Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6379

CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • 4.10, 6.0
    • SolrCloud
    • None


      spin off of SOLR-2894 where sarowe & miller were getting failures from TestCloudPivot that seemed unrelated to any of hte distrib pivot logic itself.

      in particular: adding a call to "waitForThingsToLevelOut" at the start of the test, even before indexing any docs, seemed to work around the problem – but even if all replicas aren't yet up when the test starts, we should either get a failure when adding docs (ie: no replica hosting the target shard) or queries should only be routed to the replicas that are up and fully caught up with the rest of the collection.

      (NOTE: we're specifically talking about a situation where the set of docs in the collection is static during the query request)


        1. SOLR-6379.pristine_collection.test.patch
          9 kB
          Chris M. Hostetter
        2. SOLR-6379.patch
          12 kB
          Chris M. Hostetter
        3. SOLR-6379.patch
          13 kB
          Mark Miller
        4. SOLR-6379.patch
          15 kB
          Mark Miller
        5. SOLR-6379.patch
          10 kB
          Anshum Gupta
        6. SOLR-6379.patch
          13 kB
          Anshum Gupta
        7. SOLR-6379.patch
          23 kB
          Anshum Gupta
        8. SOLR-6379.patch
          23 kB
          Anshum Gupta
        9. SOLR-6379.patch
          23 kB
          Anshum Gupta

        Issue Links


          This comment will be Viewable by All Users Viewable by All Users


            anshum Anshum Gupta
            hossman Chris M. Hostetter




                Issue deployment