You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Cassandra Targett (Jira)" <ji...@apache.org> on 2021/08/13 21:44:00 UTC
[jira] [Updated] (SOLR-11932) ZkCmdExecutor: Retry ZkOperation on
SessionExpired
[ https://issues.apache.org/jira/browse/SOLR-11932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassandra Targett updated SOLR-11932:
-------------------------------------
Component/s: SolrCloud
> ZkCmdExecutor: Retry ZkOperation on SessionExpired
> ---------------------------------------------------
>
> Key: SOLR-11932
> URL: https://issues.apache.org/jira/browse/SOLR-11932
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 7.2
> Reporter: John Gallagher
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SessionExpiredLog.txt, org.apache.solr.schema.ManagedSchemaRoundRobinCloudTest.error.txt, zk_retry.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We are seeing situations where an operation, such as changing a replica's state to active after a recovery, fails because the zk session has expired.
> However, these operations seem like they are retryable, because the ZookeeperConnect receives an event that the session expired and tries to reconnect.
> That makes the SessionExpired handling scenario seem very similar to the ConnectionLoss handling scenario, so the ZkCmdExecutor seems like it could handle them in the same way.
>
> Here's an example stack trace with some slight redactions: [^SessionExpiredLog.txt] In this case, a zk operation (a read) failed with a SessionExpired event, which seems retriable. The exception kicked off a reconnection, but seems like the subsequent operation, (publishing as active) failed (perhaps it was using a stale connection handle at that point?)
>
> Regardless, the watch mechanism that reestablishes connection on SessionExpired seems sufficient to allow the ZkCmdExecutor to retry that operation at a later time and have hope of succeeding.
>
> I have included a simple patch we are trying that catches both exceptions instead of just ConnectionLossException: [^zk_retry.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org