As I understand it (and I'm just getting into SolrCloud myself), you can essentially forget about master/slave stuff. If you're using NRT, the soft commit will make the docs visible, you don't ned to do a hard commit (unlike the master/slave days). Essentially, the update is sent to each shard leader and then fanned out into the replicas for that leader. All automatically. Leaders are elected automatically. ZooKeeper is used to keep the cluster information.
Additionally, SolrCloud keeps a transaction log of the updates, and replays them if the indexing is interrupted, so you don't risk data loss the way you used to. There aren't really masters/slaves in the old sense any more, so you have to get out of that thought-mode (it's hard, I know). The code is under pretty active development, so any feedback is valuable.... Best Erick On Mon, Feb 27, 2012 at 3:26 AM, roz dev <rozde...@gmail.com> wrote: > Hi All, > > I am trying to understand features of Solr Cloud, regarding commits and > scaling. > > > - If I am using Solr Cloud then do I need to explicitly call commit > (hard-commit)? Or, a soft commit is okay and Solr Cloud will do the job of > writing to disk? > > > - Do We still need to use Master/Slave setup to scale searching? If we > have to use Master/Slave setup then do i need to issue hard-commit to make > my changes visible to slaves? > - If I were to use NRT with Master/Slave setup with soft commit then > will the slave be able to see changes made on master with soft commit? > > Any inputs are welcome. > > Thanks > > -Saroj
