Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8, 6.0
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      addReplica API will add a node to a given collection/shard.

      Parameters:

      1. node
      2. collection
      3. shard (optional)
      4. route (optional) (see SOLR-4221)

      If shard or route is not specified then physical shards will be created on the node for the given collection using the persisted values of maxShardsPerNode and replicationFactor.

      1. SOLR-5130.patch
        8 kB
        Shalin Shekhar Mangar

        Issue Links

          Activity

          Hide
          thetaphi Uwe Schindler added a comment -

          Close issue after release of 4.8.0

          Show
          thetaphi Uwe Schindler added a comment - Close issue after release of 4.8.0
          Hide
          mjhugo Mike Hugo added a comment -

          doesn't look like this made it into the 4.7 release, please update the fix version to reflect that

          Show
          mjhugo Mike Hugo added a comment - doesn't look like this made it into the 4.7 release, please update the fix version to reflect that
          Hide
          noble.paul Noble Paul added a comment -

          resolved

          Show
          noble.paul Noble Paul added a comment - resolved
          Hide
          kamaci Furkan KAMACI added a comment -

          Shalin Shekhar Mangar Noble Paul is this issue resolved?

          Show
          kamaci Furkan KAMACI added a comment - Shalin Shekhar Mangar Noble Paul is this issue resolved?
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1571279 from Noble Paul in branch 'dev/branches/branch_4x'
          [ https://svn.apache.org/r1571279 ]

          SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1571279 from Noble Paul in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1571279 ] SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1571276 from Noble Paul in branch 'dev/trunk'
          [ https://svn.apache.org/r1571276 ]

          SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1571276 from Noble Paul in branch 'dev/trunk' [ https://svn.apache.org/r1571276 ] SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1571272 from Noble Paul in branch 'dev/branches/branch_4x'
          [ https://svn.apache.org/r1571272 ]

          SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1571272 from Noble Paul in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1571272 ] SOLR-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1571264 from Noble Paul in branch 'dev/trunk'
          [ https://svn.apache.org/r1571264 ]

          SORL-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1571264 from Noble Paul in branch 'dev/trunk' [ https://svn.apache.org/r1571264 ] SORL-5609 Don't let cores create slices/named replicas , SOLR-5130 addReplica Collections API
          Hide
          noble.paul Noble Paul added a comment -

          It should be possible to add a replica without the node param. In that case the overseer should identify a suitable node and create a replica there

          Show
          noble.paul Noble Paul added a comment - It should be possible to add a replica without the node param. In that case the overseer should identify a suitable node and create a replica there
          Hide
          shalinmangar Shalin Shekhar Mangar added a comment - - edited

          Supported Parameters:

          1. collection
          2. shard (optional)
          3. node
          4. route (optional)
          5. name - the core name (optional)
          6. instanceDir (optional)
          7. dataDir (optional)

          The collection.configName is looked up and passed along to the core admin create. If name is not specified then it is assigned. I intend to auto-assign shard as well if neither shard nor route is specified but that is not implemented yet.

          I'm working on the tests.

          Show
          shalinmangar Shalin Shekhar Mangar added a comment - - edited Supported Parameters: collection shard (optional) node route (optional) name - the core name (optional) instanceDir (optional) dataDir (optional) The collection.configName is looked up and passed along to the core admin create. If name is not specified then it is assigned. I intend to auto-assign shard as well if neither shard nor route is specified but that is not implemented yet. I'm working on the tests.
          Hide
          noble.paul Noble Paul added a comment - - edited

          currently a user can control several core properties through coreadmin CREATE

          name :The name of the new core. Same as "name" on the <core> element.
          instanceDir : The directory where files for this SolrCore should be stored. Same as instanceDir on the <core> element.
          datadir : (Optional) Name of the data directory relative to instanceDir

          This new API should support this as well, otherwise we would be taking away the some features users need

          Show
          noble.paul Noble Paul added a comment - - edited currently a user can control several core properties through coreadmin CREATE name :The name of the new core. Same as "name" on the <core> element. instanceDir : The directory where files for this SolrCore should be stored. Same as instanceDir on the <core> element. datadir : (Optional) Name of the data directory relative to instanceDir This new API should support this as well, otherwise we would be taking away the some features users need

            People

            • Assignee:
              noble.paul Noble Paul
              Reporter:
              shalinmangar Shalin Shekhar Mangar
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development