Details

      Description

      This link: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-intercluster-replication.html

      • I think it's quite confusing to refer to "replica partitions" instead of vbuckets as they are known throughout the rest of the docs
      • I also think it's quite confusing to use the term "replica node" when a) we explicitly do NOT have replica nodes and b) customers are frequently confused because other technologies DO have master/slave
      • Typo: "Notice that a replica node may also be simultaneously by handling"
      • Typo: "...in a disk write queue to eventually stored on disk at the replica node"
      • Typo and very confusing: "If one of the nodes in the system, the replica vBuckets are enabled in place of the vBuckets that are unavailable at the failed node."
      • The last paragraph should be "introduced" better to note that it is referring to handling failovers. It's also slightly incorrect in that it doesn't mention the fact that the cluster will push-out an updated map upon failover (the client doesn't have to request a new one)
      • I think the failover should be pointed to in a different section where it can be handled more completely.
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        kzeller kzeller added a comment -

        https://github.com/couchbase/docs/commit/107c519de603fb9f8fc9484f15ca4439a2e4afcb

        Fix MB 7611, refer to replica and active data vs replica nodes, typos fixed, cross ref… …
        …reference failover from discussion of replica data after failover. Redo image to refer to first node and second node with replica data.

        Show
        kzeller kzeller added a comment - https://github.com/couchbase/docs/commit/107c519de603fb9f8fc9484f15ca4439a2e4afcb Fix MB 7611, refer to replica and active data vs replica nodes, typos fixed, cross ref… … …reference failover from discussion of replica data after failover. Redo image to refer to first node and second node with replica data.
        Hide
        kzeller kzeller added a comment -

        https://github.com/couchbase/docs/commit/107c519de603fb9f8fc9484f15ca4439a2e4afcb

        Fix MB 7611, refer to replica and active data vs replica nodes, typos fixed, cross ref… …
        …reference failover from discussion of replica data after failover. Redo image to refer to first node and second node with replica data.

        Show
        kzeller kzeller added a comment - https://github.com/couchbase/docs/commit/107c519de603fb9f8fc9484f15ca4439a2e4afcb Fix MB 7611, refer to replica and active data vs replica nodes, typos fixed, cross ref… … …reference failover from discussion of replica data after failover. Redo image to refer to first node and second node with replica data.
        Hide
        kzeller kzeller added a comment -

        This link: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-intercluster-replication.html

        • I think it's quite confusing to refer to "replica partitions" instead of vbuckets as they are known throughout the rest of the docs [Fixed with references to "replica data at other node"]
        • I also think it's quite confusing to use the term "replica node" when a) we explicitly do NOT have replica nodes and b) customers are frequently confused because other technologies DO have master/slave

        [Fixed with references to 'replica data at a second node" or "at another node"
        ]

        • Typo: "Notice that a replica node may also be simultaneously by handling"
        • Typo: "...in a disk write queue to eventually stored on disk at the replica node"
        • Typo and very confusing: "If one of the nodes in the system, the replica vBuckets are enabled in place of the vBuckets that are unavailable at the failed node."
        • The last paragraph should be "introduced" better to note that it is referring to handling failovers. It's also slightly incorrect in that it doesn't mention the fact that the cluster will push-out an updated map upon failover (the client doesn't have to request a new one)
        • I think the failover should be pointed to in a different section where it can be handled more completely. [Fixed, moved]
        Show
        kzeller kzeller added a comment - This link: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-intercluster-replication.html I think it's quite confusing to refer to "replica partitions" instead of vbuckets as they are known throughout the rest of the docs [Fixed with references to "replica data at other node"] I also think it's quite confusing to use the term "replica node" when a) we explicitly do NOT have replica nodes and b) customers are frequently confused because other technologies DO have master/slave [Fixed with references to 'replica data at a second node" or "at another node" ] Typo: "Notice that a replica node may also be simultaneously by handling" Typo: "...in a disk write queue to eventually stored on disk at the replica node" Typo and very confusing: "If one of the nodes in the system, the replica vBuckets are enabled in place of the vBuckets that are unavailable at the failed node." The last paragraph should be "introduced" better to note that it is referring to handling failovers. It's also slightly incorrect in that it doesn't mention the fact that the cluster will push-out an updated map upon failover (the client doesn't have to request a new one) I think the failover should be pointed to in a different section where it can be handled more completely. [Fixed, moved]

          People

          • Assignee:
            kzeller kzeller
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes