lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Trivial Update of "SolrReplication" by PeterWolanin
Date Thu, 31 May 2012 12:59:06 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "SolrReplication" page has been changed by PeterWolanin:
http://wiki.apache.org/solr/SolrReplication?action=diff&rev1=88&rev2=89

Comment:
minor cleanup

  </requestHandler>
  }}}
  
- '''NOTE''': Be sure to add 'false' default to enable.master and enable.slave, or deploying
will fail and the log will shows Solr gets a '.' instead of correct core instance dir. In
Solr Admin main page, you won't see links with core names (Clicking into the only link, you'll
get 'missing core in path' error). (added by Scott Chu @ Taiwan)
+ '''NOTE''': Be sure to add a 'false' default to enable.master and enable.slave, or deploying
will fail and the log will shows Solr gets a '.' instead of correct core instance dir. In
Solr Admin main page, you won't see links with core names (Clicking into the only link, you'll
get 'missing core in path' error).
  
- '''NOTE''': If deploying is ok but you'll still see no links with core name, it could be
permission problem. This normally happens when you set instance dir under AP server's default
webapps folder. The workaround is to create another folder with good permissions, and put
solr.xml into root of that folder. Edit context file to point solr/home to that folder. Now
undeploy previous webapp and redeploy again. (added by Scott Chu @ Taiwan)
+ '''NOTE''': If deploying is ok but you'll still see no links with core name, it could be
permission problem. This normally happens when you set instance dir under AP server's default
webapps folder. The workaround is to create another folder with good permissions, and put
solr.xml into root of that folder. Edit context file to point solr/home to that folder. Now
undeploy previous webapp and redeploy again.
  
  When the master is started, pass in -Denable.master=true and in the slave pass in -Denable.slave=true.
 Alternately, these values can be stored in a solrcore.properties file as follows:
  
@@ -147, +147 @@

  enable.slave=true
  }}}
  
- '''NOTE''': Each core has its own solrcore.properties and put it under conf subfolder of
each core's instance dir. (added by Scott Chu @ Taiwan)
+ '''NOTE''': Each core has its own solrcore.properties that is located under the conf directory
of each core's instance directory.
  
  == Replication with MultiCore ==
  Add the replication request handler to solrconfig.xml for each core (i.e. /usr/share/tomcat6/solr/CORENAME/conf/solrconfig.xml).

Mime
View raw message