[
https://issues.apache.org/jira/browse/SOLR-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938127#comment-17938127
]
ASF subversion and git services commented on SOLR-17716:
--------------------------------------------------------
Commit 7e1f5790b7f447eae36a2d38e7c1516699f680b2 in solr's branch
refs/heads/main from Bruno Roustant
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=7e1f5790b7f ]
SOLR-17716: Handle interrupted exception in SolrCores.waitAddPendingCoreOps.
(#3283)
> Handle interrupted exception in SolrCores.waitAddPendingCoreOps
> ---------------------------------------------------------------
>
> Key: SOLR-17716
> URL: https://issues.apache.org/jira/browse/SOLR-17716
> Project: Solr
> Issue Type: Improvement
> Reporter: Bruno Roustant
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> SolrCores.waitAddPendingCoreOps is the main locking mechanism for operations
> on cores like creation/loading/removal.
> In the current code, if an InterruptedException is caught while waiting for
> the lock, the method returns null. However returning null means basically
> that the waiting is complete and the caller got the lock. So the caller code
> proceeds normally with its critical operation on the core.
> We should handle differently an InterruptedException to prevent the caller
> from taking the lock while another pending op is on the core. The proposal is
> to throw a SolrException.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
