Christine Poerschke created SOLR-6279:
-----------------------------------------

             Summary: 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]

Reply via email to