Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Sun, 17 Jan 2010 20:28:48 -0000
Message-ID: <20100117202848.5553.35133@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSolr_Wiki=5D_Trivial_Update_of_=22SolrCloud=22_by_YonikSeele?=
 =?utf-8?q?y?=

Dear Wiki user,

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

The "SolrCloud" page has been changed by YonikSeeley.
http://wiki.apache.org/solr/SolrCloud?action=3Ddiff&rev1=3D16&rev2=3D17

--------------------------------------------------

     . URLs (the shard addresses) then servers that aren't up would just be=
 represented by a blank space:    localhost:8983,,localhost:7574
   * optionally run ZK server in Solr for simple dev cluster (zk data dir u=
nder the solr data dir?)
   * document/demo the simplest two server distributed search solution in "=
getting started"... make it easy!
-  * look into changing the name of the ugly DEFAULT_COLLECTION
+  * look into changing the name of the ugly DEFAULT_CORE (SOLR-1722)
+  * when using master/slave replication, optionally remove the periodic po=
lling that slaves do and replace with a watch on a znode that can immediate=
ly ping/pull an index when the version changes.  Seems like low priority si=
nce index version polls can be frequent with low overhead.
  =

  =3D=3D High level design goals =3D=3D
  These are long term goals for SolrCloud.  Many of these features will not=
 be developed in the first versions, but we're designing for the long haul.