SolrJ already has access to zookeeper cluster state. Network I/O bottleneck can be avoided by parallel requests. You are only as slow as your slowest responding server, which could be your single leader with the current set up.
Wouldn't this lessen the burden of the leader, as he does not have to maintain transaction logs or distribute to replicas? -----Original Message----- From: Shalin Shekhar Mangar <shalinman...@gmail.com> To: solr-user <solr-user@lucene.apache.org> Sent: Tue, Jun 18, 2013 2:05 am Subject: Re: SOLR Cloud - Disable Transaction Logs Yes, but at what cost? You are thinking of replacing disk IO with even more slower network IO. The transaction log is a append-only log -- it is not pretty cheap especially so if you compare it with the indexing process. Plus your write request/sec will drop a lot once you start doing synchronous replication. On Tue, Jun 18, 2013 at 2:18 AM, Rishi Easwaran <rishi.easwa...@aol.com>wrote: > Shalin, > > Just some thoughts. > > Near Real time replication- don't we use solrCmdDistributor, which send > requests immediately to replicas with a clonedRequest, as an option can't > we achieve something similar form CloudSolrserver in Solrj instead of > leader doing it. As long as 2 nodes receive writes and acknowledge. > durability should be high. > Peer-Sync and Recovery - Can we achieve that merging indexes from leader > as needed, instead of replaying the transaction logs? > > Rishi. > > > > > > > > -----Original Message----- > From: Shalin Shekhar Mangar <shalinman...@gmail.com> > To: solr-user <solr-user@lucene.apache.org> > Sent: Mon, Jun 17, 2013 3:43 pm > Subject: Re: SOLR Cloud - Disable Transaction Logs > > > It is also necessary for near real-time replication, peer sync and > recovery. > > > On Tue, Jun 18, 2013 at 1:04 AM, Rishi Easwaran <rishi.easwa...@aol.com > >wrote: > > > Hi, > > > > Is there a way to disable transaction logs in SOLR cloud. As far as I can > > tell no. > > Just curious why do we need transaction logs, seems like an I/O intensive > > operation. > > As long as I have replicatonFactor >1, if a node (leader) goes down, the > > replica can take over and maintain a durable state of my index. > > > > I understand from the previous discussions, that it was intended for > > update durability and realtime get. > > But, unless I am missing something an ability to disable it in SOLR cloud > > if not needed would be good. > > > > Thanks, > > > > Rishi. > > > > > > > -- > Regards, > Shalin Shekhar Mangar. > > > -- Regards, Shalin Shekhar Mangar.
