[
https://issues.apache.org/jira/browse/SOLR-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447072#comment-13447072
]
Mark Miller commented on SOLR-3750:
-----------------------------------
Because this behavior is not currently strictly necessary, and sometimes not
ideal, I'm thinking I will default it to false and allow it to be configured to
on along with the amount of time to wait - at least initially.
Later, when we allow you to return before *every* replica has an update, this
could probably be automatically enabled? Or in the case you could choose that
behavior per update, doc'd that you should enable it.
I think it should be an option now because it also can offer some protections
against more esoteric cases - eg when starting the cluster, you start using a
really old node and start that node first and it becomes leader...you just want
to be willing to live with some of the esoteric downsides of enabling it as as
well.
> On session expiration, we should explicitly wait some time before running the
> leader sync process so that we are sure every node participates.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3750
> URL: https://issues.apache.org/jira/browse/SOLR-3750
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
>
> We should wait until all the known nodes are part of the election, or X
> amount of time if that does not happen (when a node or more does not come
> back for whatever reason).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
