Hello,
I am experiencing a failure mode where a replica is unable to recover and it
will try to do so forever. In writing this email I want to make sure that I
haven't missed anything obvious or missed a configurable option that could
help. If something about this looks funny, I would really
Whoops, in the description of my setup that should say 2 replicas per shard.
Every server has a replica.
> On Oct 27, 2015, at 20:16, Brian Scholl wrote:
>
> Hello,
>
> I am experiencing a failure mode where a replica is unable to recover and it
> will try to do so fo
n
> delay node restart.
>
> See
> https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConf
> ig#UpdateHandlersinSolrConfig-TransactionLog for more info.
>
>
> Hope some of that helps, I don’t know a way to say
> delete-first-on-recovery.
>
>
>
&g
ut be aware that a large transaction log size can
> delay node restart.
>
> See
> https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConf
> ig#UpdateHandlersinSolrConfig-TransactionLog for more info.
>
>
> Hope some of that helps, I don’t know a way to say
> d
situation _worse_ by making running out of disk space
> during a merge even more likely.
>
> So unless there's a compelling reason you can't use bigger
> disks, IMO you'll waste lots and lots of valuable
> engineering time before... buying bigger disks.
>
> Best,
&
. network being unplugged, whatever) I'd put some energy into
> understanding that as well. Perhaps there are operational type things
> that should be addressed (e.g. stop indexing, wait for commit, _then_
> bounce Solr instances).
>
>
> Best,
> Erick
>
>
