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

CloudSolrClient's cluster state cache can break direct updates to leaders

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.4
    • Component/s: None
    • Labels:
      None

      Description

      This is the root cause of SOLR-9305 and (at least some of) SOLR-9390. The process goes something like this:

      Documents are added to the cluster via a CloudSolrClient, with directUpdatesToLeadersOnly set to true. CSC caches its view of the DocCollection. The leader then goes down, and is reassigned. Next time documents are added, CSC checks its cache again, and gets the old view of the DocCollection. It then tries to send the update directly to the old, now down, leader, and we get ConnectionRefused.

        Attachments

        1. SOLR-9512.patch
          46 kB
          Noble Paul
        2. SOLR-9512.patch
          7 kB
          Noble Paul
        3. SOLR-9512.patch
          15 kB
          Alan Woodward

        Issue Links

          Activity

            People

            • Assignee:
              noble.paul Noble Paul
              Reporter:
              romseygeek Alan Woodward

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment