ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colm O hEigeartaigh <cohei...@apache.org>
Subject Re: Review Request 62376: The JAVA_HOME property is invalid in install.properties for Solr for Ranger Audits. The solr started fail after installed and configured Solr for Ranger Audits.
Date Tue, 19 Sep 2017 14:13:36 GMT


> On Sept. 19, 2017, 11:43 a.m., Colm O hEigeartaigh wrote:
> > I wonder if we need to support JAVA_HOME at all here in the solr audit install.properties?
Why not just take it from the environment like all of the other plugins?
> 
> pengjianhua wrote:
>     The case will be very passive when we run hbase using jdk1.7 and run solr using jdk1.8
in the same node. Once we support the issue, this case is very easy to solve. So I think we
should make this configuration effective, which can give us flexibility without any side effects.
> 
> pengjianhua wrote:
>     In my environment, solr must be jdk1.8 or more, and my other components must use
jdk1.7. I have to modify other programs or Solr for Ranger Audits scripts to run the programs
I need. Other users will face the same problem, they will have no way to solve the case unless
they modify the code.
> 
> Colm O hEigeartaigh wrote:
>     Sorry, I don't understand your response. Why not just set JAVA_HOME in the environment
instead of in install.properties?
> 
> pengjianhua wrote:
>     Ok. Please check install.properties. You can find the following code in the install.properties.
>     #JAVA_HOME to be used by Solr. Solr only support JDK 1.7 and above. If JAVA_HOME
is not set
>     #in the env, then please set it here
>     #JAVA_HOME=
>     
>     I modified above code. Set JAVA_HOME property equal to /diskb/home/pengjianhua/tools/jdk1.8.0_111.
The JAVA_HOME property I set is invalid when installed Solr for Ranger Audits.
>     #JAVA_HOME to be used by Solr. Solr only support JDK 1.7 and above. If JAVA_HOME
is not set
>     #in the env, then please set it here
>     JAVA_HOME=/diskb/home/pengjianhua/tools/jdk1.8.0_111
> 
> pengjianhua wrote:
>     #JAVA_HOME to be used by Solr. Solr only support JDK 1.7 and above. If JAVA_HOME
is not set
>     #in the env, then please set it here
>     #JAVA_HOME=

Yes I understand that, but I'm asking if we should not just remove this configuration option
from install.properties? You can't set JAVA_HOME in install.properties for any of the other
plugins.


- Colm


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62376/#review185673
-----------------------------------------------------------


On Sept. 19, 2017, 12:45 p.m., pengjianhua wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62376/
> -----------------------------------------------------------
> 
> (Updated Sept. 19, 2017, 12:45 p.m.)
> 
> 
> Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh,
Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and
Qiang Zhang.
> 
> 
> Bugs: RANGER-1791
>     https://issues.apache.org/jira/browse/RANGER-1791
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> The JAVA_HOME property is invalid in install.properties for Solr for Ranger Audits. The
solr started fail after installed and configured Solr for Ranger Audits. The error information
is as following:
> Your current version of Java is too old to run this version of Solr
> We found version 1.7.0_80, using command '/diskb/home/pengjianhua/tools/jdk1.7.0_80/bin/java
-version', with response:
> java version "1.7.0_80"
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
> 
> Please install latest version of Java 1.8 or set JAVA_HOME properly.
> 
> Debug information:
> JAVA_HOME: /diskb/home/pengjianhua/tools/jdk1.8.0_111
> Active Path:
> /diskb/home/pengjianhua/tools/jdk1.7.0_80/bin:/diskb/home/pengjianhua/tools/jdk1.7.0_80/jre/bin:/diskb/home/pengjianhua/tools/jdk1.7.0_80/bin:/diskb/home/pengjianhua/tools/jdk1.7.0_80/jre/bin:/diskc/component/run/hbase-1.2.6/bin:/diskc/component/run/hbase-1.2.6/conf:/diskc/component/run/hadoop-2.7.4/bin:/diskc/component/run/hadoop-2.7.4/sbin:/diskc/component/run/zookeeper-3.4.10/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/pengjianhua/anaconda3/bin:/snap/bin:/home/pengjianhua/bin:/diskb/home/pengjianhua/tools/apache-maven-3.3.9/bin:/home/pengjianhua/anaconda3/bin:/home/pengjianhua/bin:/diskb/home/pengjianhua/tools/apache-maven-3.3.9/bin:/home/pengjianhua/anaconda3/bin
> That is, this configuration is invalid.
> 
> 
> Diffs
> -----
> 
>   security-admin/contrib/solr_for_audit_setup/setup.sh 22d4c620 
> 
> 
> Diff: https://reviews.apache.org/r/62376/diff/1/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> pengjianhua
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message