lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brendan Grainger <>
Subject Re: state.json base_url has internal IP of ec2 instance set instead of 'public DNS' entry in some cases
Date Fri, 15 Jan 2016 23:27:22 GMT
Hi Hoss,

Thanks for the reply. I installed the service using the install script. I double checked it
and it looks like it install in /etc/defaults/ It actually looks like
if it is in /var the install script moves it into /etc/defaults (unless I’m reading this
wrong): <>

I checked the process and even on restarts it looks like this:

ps aux | grep solr
  my_solr_user      9522  0.2  1.5 3010216 272656 ?      Sl   20:06   0:26 /usr/lib/jvm/java-8-oracle/bin/java
-server -Xms512m -Xmx512m -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8
-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark
-XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50
-XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled
-verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps
-XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log
-DzkClientTimeout=15000 -DzkHost=ec2_host:2181/solr -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks
-Dhost=ec2_host -Duser.timezone=UTC -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data
-Dsolr.install.dir=/opt/solr -Dlog4j.configuration=file:/var/solr/ -Xss256k
-jar start.jar -XX:OnOutOfMemoryError=/opt/solr/bin/ 8983 /var/solr/logs --module=http

Note I replaced the user I’m running it as with my_solr_user and the actual ec2 public DNS
with e2_host in the output above.

I am new to SolrCloud so it’s more than likely I’ve screwed up some configuration setting

Thank you for your help,

> On Jan 15, 2016, at 6:07 PM, Chris Hostetter <> wrote:
> : What I’m finding is that now and then base_url for the replica in 
> : state.json is set to the internal IP of the AWS node. i.e.:
> : 
> : "base_url":"http://10.29.XXX.XX:8983/solr”,
> : 
> : On other attempts it’s set to the public DNS name of the node:
> : 
> : "base_url":"http://ec2_host:8983/solr”,
> : 
> : In my /etc/defaults/ I have:
> : 
> : SOLR_HOST=“ec2_host”
> : 
> : which I thought is what I needed to get the public DNS name set in base_url. 
> i believe you are correct.  the "now and then" part of your question is 
> weird -- it seems to indicate that sometimes the "correct" thing is 
> happening, and other times it is not.  
> /etc/defaults/ isn't the canonical path for 
> according to the docs/install script for running a production solr 
> instance...
> *exactly* are you running Solr on all of your nodes?
> because my guess is that you've got some kind of inconsistent setup where 
> sometimes when you startup (or restart) a new node it does refer to your 
> file, and other times it does not -- so sometimes solr never 
> sees your SOLR_HOST option.  In those cases, when it regesters itself with 
> ZooKeeper it uses the current IP as a fallback, and then that info gets 
> backed into the metadata for the replicas that get created on that node 
> at that point in time.
> FWIW, you should be able to spot check that the SOLR_HOST is being applied 
> correctly by looking at the java process command line args (using PS, or 
> loading the SOlr UI in your browser) and checking for the "-Dhost=..." 
> option -- if it's not there, then your probably wasn't read in 
> correctly
> -Hoss

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