[
https://issues.apache.org/jira/browse/SOLR-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074307#comment-14074307
]
ASF GitHub Bot commented on SOLR-6279:
--------------------------------------
GitHub user cpoerschke opened a pull request:
https://github.com/apache/lucene-solr/pull/72
SOLR-6279: cores?action=UNLOAD can unregister unclosed core
https://issues.apache.org/jira/i#browse/SOLR-6279
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bloomberg/lucene-solr
trunk-UNLOAD-can-unregister-unclosed-close
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/72.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #72
----
commit 2a80ca5dfb47b7cd0416be2ae72bade0fe8f3ad0
Author: Christine Poerschke <[email protected]>
Date: 2014-07-22T12:07:58Z
solr: cores?action=UNLOAD can unregister unclosed core
Changing CoreContainer.unload to wait for core to close before
unregistering it from ZK. Adding testMidUseUnload method to TestLazyCores.
----
> cores?action=UNLOAD can unregister unclosed core
> ------------------------------------------------
>
> Key: SOLR-6279
> URL: https://issues.apache.org/jira/browse/SOLR-6279
> Project: Solr
> Issue Type: Bug
> Reporter: Christine Poerschke
>
> baseline:
> {code}
> /somewhere/instanceA/collection1_shard1/core.properties
> /somewhere/instanceA/collection1_shard1/data
> /somewhere/instanceA/collection1_shard2/core.properties
> /somewhere/instanceA/collection1_shard2/data
> /somewhere/instanceB
> {code}
> actions:
> {code}
> curl
> "http://host:port/solr/admin/cores?action=UNLOAD&core=collection1_shard2";
> # since UNLOAD completed we should now be free to move the unloaded core's
> files as we wish
> mv /somewhere/instanceA/collection1_shard2
> /somewhere/instanceB/collection1_shard2
> {code}
> expected result:
> {code}
> /somewhere/instanceA/collection1_shard1/core.properties
> /somewhere/instanceA/collection1_shard1/data
> # collection1_shard2 files have been fully relocated
> /somewhere/instanceB/collection1_shard2/core.properties.unloaded
> /somewhere/instanceB/collection1_shard2/data
> {code}
> actual result:
> {code}
> /somewhere/instanceA/collection1_shard1/core.properties
> /somewhere/instanceA/collection1_shard1/data
> /somewhere/instanceA/collection1_shard2/data
> # collection1_shard2 files have not been fully relocated and/or some files
> were left behind in instanceA because the UNLOAD action had returned prior to
> the core being closed
> /somewhere/instanceB/collection1_shard2/core.properties.unloaded
> /somewhere/instanceB/collection1_shard2/data
> {code}
> +proposed fix:+ Changing CoreContainer.unload to wait for core to close
> before unregistering it from ZK. Adding testMidUseUnload method to
> TestLazyCores.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
