[
https://issues.apache.org/jira/browse/SOLR-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133964#comment-18133964
]
David Smiley commented on SOLR-17704:
-------------------------------------
[~houston] last touched this (I never have) so he'd be the right reviewer here.
{quote} isAcquired() ... OK to drop it and rewrite the lock tests ...
{quote}
Yes.
{quote}I'd document a full restart for Overseer-disabled clusters moving to 11,
{quote}
+1. We can also support a rolling upgrade when there are no cluster
manipulations (state changes don't count). We might even enhance Solr to
throw/fail instead of creating locks when the cluster has diverse major
versions.
> Change ZkDistributedLock to use Curator Recipes
> -----------------------------------------------
>
> Key: SOLR-17704
> URL: https://issues.apache.org/jira/browse/SOLR-17704
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Now that Solr is using Curator Recipes for connection management, we can
> finally use it to replace Solr code. ZkDistributedLock looks like very
> low-hanging fruit, used by the non-Overseer distributed mode. That mode is
> still experimental so we can change it in backwards-incompatible ways in Solr
> 10.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
