Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.8, 6.0
    • SolrCloud
    • None

    Description

      In SolrCloud, it is possible for a core to come up in any node , and register itself with an arbitrary slice/coreNodeName. This is a legacy requirement and we would like to make it only possible for Overseer to initiate creation of slice/replicas

      We plan to introduce cluster level properties at the top level

      /cluster-props.json

      {
      "noSliceOrReplicaByCores":true"
      }
      

      If this property is set to true, cores won't be able to send STATE commands with unknown slice/coreNodeName . Those commands will fail at Overseer. This is useful for SOLR-5310 / SOLR-5311 where a core/replica is deleted by a command and it comes up later and tries to create a replica/slice

      Attachments

        1. SOLR-5609_5130.patch
          26 kB
          Noble Paul
        2. SOLR-5609_5130.patch
          41 kB
          Noble Paul
        3. SOLR-5609_5130.patch
          42 kB
          Noble Paul
        4. SOLR-5609_5130.patch
          44 kB
          Noble Paul
        5. SOLR-5609.patch
          12 kB
          Noble Paul
        6. SOLR-5609.patch
          12 kB
          Noble Paul

        Issue Links

        Activity

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

          People

            noble.paul Noble Paul
            noble.paul Noble Paul
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment