[jira] [Created] (SOLR-12291) OverseerCollectionMessageHandler sliceCmd assumes only one replica exists on each node

["Varun Thacker (JIRA)" <ji...@apache.org>]

Varun Thacker created SOLR-12291:
------------------------------------

             Summary: OverseerCollectionMessageHandler sliceCmd assumes only one replica exists on each node
                 Key: SOLR-12291
                 URL: https://issues.apache.org/jira/browse/SOLR-12291
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Varun Thacker


The OverseerCollectionMessageHandler sliceCmd assumes only one replica exists on one node

When multiple replicas of a slice are on the same node we only track one replica's async request. This happens because the async requestMap's key is "node_name"

I discovered this when [~alabax] shared some logs of a restore issue, where the second replica got added before the first replica had completed it's restorecore action.

While looking at the logs I noticed that the overseer never called REQUESTSTATUS for the restorecore action , almost as if it had missed tracking that particular async request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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