[ 
https://issues.apache.org/jira/browse/SOLR-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515607#comment-15515607
 ] 

Cao Manh Dat commented on SOLR-4109:
------------------------------------

I tried a scenario like this in the lastest Solr version
- Start a solrcloud cluster with 3 nodes. Node A ( port 8983 ), Node B ( port 
7574 ), Node C ( port 8984 )
- Create a collection with 4 shards, 2 replicas
- Stop 2 nodes ( B and C )
- Call Delete API on node. We will get success result on node A.
{code}
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <lst name="responseHeader">
    <int name="status">0</int>
    <int name="QTime">4899</int>
  </lst>
  <lst name="success">
    <lst name="192.168.1.7:8983_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">44</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:8983_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">4041</int>
      </lst>
    </lst>
  </lst>
</response>
{code}
- Start node B and C
- The collection still alive in node B and C
- Call Delete collection on node B. We will get this result
{code}
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <lst name="responseHeader">
    <int name="status">0</int>
    <int name="QTime">3450</int>
  </lst>
  <lst name="success">
    <lst name="192.168.1.7:7574_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">48</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:7574_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">69</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:7574_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">89</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:8984_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">67</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:8984_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">2508</int>
      </lst>
    </lst>
    <lst name="192.168.1.7:8984_solr">
      <lst name="responseHeader">
        <int name="status">0</int>
        <int name="QTime">2507</int>
      </lst>
    </lst>
  </lst>
</response>

{code}

Is it a normal behaviour for this scenario?

> can't delete inactive core in  collection
> -----------------------------------------
>
>                 Key: SOLR-4109
>                 URL: https://issues.apache.org/jira/browse/SOLR-4109
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: 4.0-BETA, 4.0
>            Reporter: Po Rui
>             Fix For: 4.0-BETA, 4.0
>
>         Attachments: SOLR-4109.patch
>
>
> It failed to delete a collection when any inactive core appear in the 
> collection. the inactive core due to a lot of reasons. usually caused by 
> recovering failed and the inactive core hard to active again only if it have 
> chance to be a leader. but for user, he/she doesn't care the core is active 
> or not if he/she already decide to delete the collection. so we should delete 
> the inactive core too rather than stop user doing this operation. this 
> behavior lead a collection contained inactive core almost impossible to be 
> deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to