[
https://issues.apache.org/jira/browse/SOLR-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975362#comment-13975362
]
Mark Miller commented on SOLR-5495:
-----------------------------------
bq. which I can't really see how it would happen
Consider that we might have other states in the future as well - and / or,
there can be backed up requests. Or what about races with the replica doing
it's own recovery and having a down tossed in there by the leader. It's tricky
to promise anything.
bq. This would make the replica a candidate for receiving requests again, which
would just lead to another error
Is that guaranteed though? What if a connection recovers and it doesn't lead to
another error?
If it all bears out in testing though, perhaps that's all fine.
bq. I found a handy class named SocketProxy
+1 - it's great to be able to do this as part of the standard tests in Java.
> Recovery strategy for leader partitioned from replica case.
> -----------------------------------------------------------
>
> Key: SOLR-5495
> URL: https://issues.apache.org/jira/browse/SOLR-5495
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Timothy Potter
> Attachments: SOLR-5495.patch
>
>
> We need to work out a strategy for the case of:
> Leader and replicas can still talk to ZooKeeper, Leader cannot talk to
> replica.
> We punted on this in initial design, but I'd like to get something in.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
