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 "SolrCloud" by ErickErickson
Date Thu, 09 Feb 2012 13:33:34 GMT
Dear Wiki user,

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

The "SolrCloud" page has been changed by ErickErickson:
http://wiki.apache.org/solr/SolrCloud?action=diff&rev1=27&rev2=28

Comment:
cd example2, added link and notes for new admin UI.

   * {{{-Dcollection.configName=myconf}}} sets the config to use for the new collection. Omitting
this param will cause the config name to default to "configuration1".
   * {{{-DnumShards=2}}} the number of logical partitions we plan on splitting the index into.
  
- Browse to http://localhost:8983/solr/collection1/admin/zookeeper.jsp to see the state of
the cluster (the zookeeper distributed filesystem).
+ Browse to http://localhost:8983/solr/collection1/admin/zookeeper.jsp to see the state of
the cluster (the zookeeper distributed filesystem). NOTE: There is a new admin UI that is
a work-in-progress that is also available: http://localhost:8983/solr/#/cloud (make sure to
expand the rather lonely-looking root node in the initial display!). The information on this
page may not be complete, feel free to try it and provide feedback/enhancements.
  
  You can see from the zookeeper browser that the Solr configuration files were uploaded under
"myconf", and that a new document collection called "collection1" was created.  Under collection1
is a list of shards, the pieces that make up the complete collection.
  
@@ -49, +49 @@

  Then start the second server, pointing it at the cluster:
  
  {{{
+ cd example2
  java -Djetty.port=7574 -DzkHost=localhost:9983 -DnumShards=2 -jar start.jar
  }}}
   * {{{-Djetty.port=7574}}}  is just one way to tell the Jetty servlet container to use a
different port.
@@ -93, +94 @@

  cd example2B
  java -Djetty.port=7500 -DzkHost=localhost:9983 -DnumShards=2 -jar start.jar
  }}}
- Refresh the zookeeper browser page http://localhost:8983/solr/admin/zookeeper.jsp and verify
that 4 solr nodes are up, and that each shard is present at 2 nodes.
+ Refresh the zookeeper browser page [[http://localhost:8983/solr/admin/zookeeper.jsp|Solr
Zookeeper Admin UI]] or [[http://localhost:8983/solr/#/cloud|new Solr Zookeeper Admin UI]]
and verify that 4 solr nodes are up, and that each shard is present at 2 nodes.
  
  Because we have been telling Solr that we want two logical shards, starting instances 3
and 4 are assigned to be replicas of instances one and two automatically.
  
@@ -141, +142 @@

  cd example2B
  java -Djetty.port=7500 -DzkHost=localhost:9983,localhost:8574,localhost:9900 -DnumShards=2
-jar start.jar
  }}}
- Now since we are running three embedded zookeeper servers as an ensemble, everything can
keep working even if a server is lost. To demonstrate this, kill the exampleB server by pressing
CTRL+C in it's window and then browse to http://localhost:8983/solr/admin/zookeeper.jsp to
verify that the zookeeper service still works.
+ Now since we are running three embedded zookeeper servers as an ensemble, everything can
keep working even if a server is lost. To demonstrate this, kill the exampleB server by pressing
CTRL+C in it's window and then browse to [[http://localhost:8983/solr/admin/zookeeper.jsp|Solr
Zookeeper Admin UI]] or [[http://localhost:8983/solr/#/cloud|new Solr Zookeeper Admin UI]]
to verify that the zookeeper service still works.
  
  == ZooKeeper ==
  Multiple Zookeeper servers running together for fault tolerance and high availability is
called an ensemble.  For production, it's recommended that you run an external zookeeper ensemble
rather than having Solr run embedded servers.  See the [[http://zookeeper.apache.org/|Apache
ZooKeeper]] site for more information on downloading and running a zookeeper ensemble. More
specifically, try [[http://zookeeper.apache.org/doc/r3.3.4/zookeeperStarted.html|Getting Started]]
and [[http://zookeeper.apache.org/doc/r3.3.4/zookeeperAdmin.html|ZooKeeper Admin]]. It's actually
pretty simple to get going. You can stick to having Solr run ZooKeeper, but keep in mind that
a ZooKeeper cluster is not easily changed dynamically. Until further support is added to ZooKeeper,
changes are best done with rolling restarts. Handling this in a separate process from Solr
will usually be preferable. 

Mime
View raw message