Hi
We're using good old master-slave replication (not SolrCloud yet)
Since we've upgraded to solr 4.3, replication causes the slave JVM to
hiccup (probably heap & GC issues) *during the download phase*, which
seemed strange to me because download was only supposed to copy files from
the master to
due to
transaction-logs, and possible affect on indexer stability, and am
considering increasing the JVM heap - do you think this worry is realistic?
Thanks,
Michael
On Wed, Jun 12, 2013 at 12:58 AM, Shawn Heisey wrote:
> On 6/11/2013 3:45 PM, Michael Tsadikov wrote:
>
>> We're u
We're upgrading our Solr 3.1 distributed masters/slaves setup to 4.3.
In 3.1 we used autoCommit every hour on masters, each commit is replicated
to slaves, and all searches are done on slaves. 1hr visibility is ok - we
don't need NRT.
In 4.3 we enable transaction logs, for durability in case of c
ombinator.com/item?id=4182642>
> >>
> >> Mike McCandless
> >>
> >> http://blog.mikemccandless.com
> >>
> >> On Sun, Jul 1, 2012 at 8:08 AM, Óscar Marín Miró
> >> wrote:
> >> > Hello Michael, thanks for the no
Our solr servers went into GC hell, and became non-responsive on date
change today.
Restarting tomcats did not help.
Rebooting the machine did.
http://www.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/
