[
https://issues.apache.org/jira/browse/SOLR-13386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818095#comment-16818095
]
Mark Miller commented on SOLR-13386:
------------------------------------
bq. Maybe we can just skip the "exists" call?
Yeah, good point, being optimistic here is nicer.
bq. I see similar pattern in ClusterProperties and CollectionProperties where
we catch KeeperException.NodeExistsException but that probably needs to be
NoNodeException?
I'll take a look.
> Remove race in OverseerTaskQueue#remove that can result in the Overseer
> causing a Zookeeper call spin spike.
> ------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-13386
> URL: https://issues.apache.org/jira/browse/SOLR-13386
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
> Fix For: 7.7.2, 8.1
>
>
> If the data call hits NoNodeException, it will throw and the Overseer work
> queue processor will catch it and loop and repeat, which causes major zk
> getData / NoNode call traffic or other such things.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
