Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-40787

Add a setting for num_replica on UI

    XMLWordPrintable

Details

    • 1

    Description

      Please add the "num_replica" setting to UI under "Advanced Index Settings".

      The default value of this setting should be "0". The change to this setting should invoke a REST call to indexer settings endpoint, updating the "indexer.settings.num_replica" value

      .

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Dave Finlay

            We'd like to continue this rather than invent a new way to send different kinds of settings to indexer. Can numReplicas be set this way or do you have some work to do on your side?

            Yes, metakv is the preferred way to do this. Sorry about the confusion. It should already work, there is nothing additional to be done from indexer side.

            if numReplicas is missing from the indexing config are you comfortable forever defaulting it to zero?

            Yes, the setting has a default value of 0. If the setting is missing in metakv, indexer would use the default.

            Another question : Some customers are already using this setting(as seen in the linked customer cases). In that case, Indexer would have already written the key "indexer.settings.num_replica" to metakv with some value. Will ns-server default to the value already existing in metakv or overwrite the metakv setting with 0 on upgrade?

            deepkaran.salooja Deepkaran Salooja added a comment - Dave Finlay We'd like to continue this rather than invent a new way to send different kinds of settings to indexer. Can numReplicas be set this way or do you have some work to do on your side? Yes, metakv is the preferred way to do this. Sorry about the confusion. It should already work, there is nothing additional to be done from indexer side. if numReplicas is missing from the indexing config are you comfortable forever defaulting it to zero? Yes, the setting has a default value of 0. If the setting is missing in metakv, indexer would use the default. Another question : Some customers are already using this setting(as seen in the linked customer cases). In that case, Indexer would have already written the key "indexer.settings.num_replica" to metakv with some value. Will ns-server default to the value already existing in metakv or overwrite the metakv setting with 0 on upgrade?

            Varun Velamuri, I was wondering how this max (16) was chosen? Could you please clarify?

            pavel Pavel Blagodov added a comment - Varun Velamuri , I was wondering how this max (16) was chosen? Could you please clarify?

            Build couchbase-server-7.0.0-4318 contains ns_server commit 95ff282 with commit message:
            MB-40787: add a setting for num_replica in UI

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-4318 contains ns_server commit 95ff282 with commit message: MB-40787 : add a setting for num_replica in UI

            Build couchbase-server-7.0.0-4318 contains ns_server commit 8ced889 with commit message:
            MB-40787: add a setting for num_replica

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-4318 contains ns_server commit 8ced889 with commit message: MB-40787 : add a setting for num_replica

            Validated on build 7.0.0-4502. 

             

            After changing the setting from UI in Advance Index settings, indexes are created with set num replica values.

            hemant.rajput Hemant Rajput added a comment - Validated on build 7.0.0-4502.    After changing the setting from UI in Advance Index settings, indexes are created with set num replica values.

            People

              pavel Pavel Blagodov
              varun.velamuri Varun Velamuri
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty