Couchbase Server

Allow XDCR configuration at bucket replication level, not just the cluster level

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 2.0, 2.0.1
  • Fix Version/s: 2.1
  • Component/s: ns_server
  • Security Level: Public
  • Labels:
    None

Description

There are scenarios where you may want to tune the XDCR parameters differently on a per replicator basis. Specifically, if you're using normal XDCR and integration with ElasticSearch you may want to adjust the checkpoint intervals separately.

Currently the XDCR parameters are cluster wide. Allow users to set these on a per XDCR basis.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Junyi Xie added a comment -
Modify the title to "bucket replication level".

Today the replicator is one per vbucket, there is no need to set up parameter to each single vbucket replicator. Instead, we may need a "localized parameters" for different replications.
Show
Junyi Xie added a comment - Modify the title to "bucket replication level". Today the replicator is one per vbucket, there is no need to set up parameter to each single vbucket replicator. Instead, we may need a "localized parameters" for different replications.
Hide
Permalink
Junyi Xie added a comment - - edited
Today AFAIK we do not have any bucket-level ns_server parameter but it is going to be more and more useful. It would be nice that ns_server can provide such infrastructure so in future xdcr and other component will be able to benefit from it.

I would position this requirement as a general bucket-level parameter infrastructure implemented in ns_server, not just something very specific to XDCR.
Show
Junyi Xie added a comment - - edited Today AFAIK we do not have any bucket-level ns_server parameter but it is going to be more and more useful. It would be nice that ns_server can provide such infrastructure so in future xdcr and other component will be able to benefit from it. I would position this requirement as a general bucket-level parameter infrastructure implemented in ns_server, not just something very specific to XDCR.
Hide
Permalink
Junyi Xie added a comment -
Not sure how hard to implement that and if ns_server team has cycles on this issue. Tentatively make the fix version 2.1
Show
Junyi Xie added a comment - Not sure how hard to implement that and if ns_server team has cycles on this issue. Tentatively make the fix version 2.1
Hide
Permalink
Dipti Borkar added a comment -
We need this much before 2.1. We are seeing the need for this not only for Elasticsearch plugin but also for customers as they tune XDCR for their use cases.

Aliaksey, can you comment on how much work this is on the ns_server side?
Show
Dipti Borkar added a comment - We need this much before 2.1. We are seeing the need for this not only for Elasticsearch plugin but also for customers as they tune XDCR for their use cases. Aliaksey, can you comment on how much work this is on the ns_server side?
Hide
Permalink
Dipti Borkar added a comment -
Sorry Siri, Can you comment on how much work this is ?
Show
Dipti Borkar added a comment - Sorry Siri, Can you comment on how much work this is ?
Hide
Permalink
Sriram Melkote added a comment -
Currently, we store it as "Internal Settings" - we would want to remove it from there and add it at the XDCR configuration screen. Perhaps as an "Advanced" accordion that is collapsed by default. It is a few days of work from server side, and same amount of work on UI side. As Junyi assigned this back to ns_server, I'm assuming the XDCR replicator can already handle different settings per replicator, and so no effort there.
Show
Sriram Melkote added a comment - Currently, we store it as "Internal Settings" - we would want to remove it from there and add it at the XDCR configuration screen. Perhaps as an "Advanced" accordion that is collapsed by default. It is a few days of work from server side, and same amount of work on UI side. As Junyi assigned this back to ns_server, I'm assuming the XDCR replicator can already handle different settings per replicator, and so no effort there.
Hide
Permalink
Maria McDuff added a comment -
bug scrub: if there's time to fix this in 2.0.2, we should seriously consider.
Show
Maria McDuff added a comment - bug scrub: if there's time to fix this in 2.0.2, we should seriously consider.
Hide
Permalink
Anil Kumar added a comment - - edited
assigning this ALK for ns_server related work
Show
Anil Kumar added a comment - - edited assigning this ALK for ns_server related work

People

  • Assignee:
    Anil Kumar
    Reporter:
    Marty Schoch
Vote (0)
Watch (6)

Dates

  • Created:
    Updated: