Skip to content

[DOC-14290]: Document Enforcing CE limitations#4118

Open
RayOffiah wants to merge 1 commit into
release/8.1from
DOC-14290--8.1--Document-Enforcing-CE-limitations
Open

[DOC-14290]: Document Enforcing CE limitations#4118
RayOffiah wants to merge 1 commit into
release/8.1from
DOC-14290--8.1--Document-Enforcing-CE-limitations

Conversation

@RayOffiah
Copy link
Copy Markdown
Contributor

Updated documentation to reflect the enforcement of Community Edition (CE) limitations. Changes were made to the following files:

  • editions.adoc
  • xdcr-management-overview.adoc

Preview URLs:

Preview URL:
https://preview.docs-test.couchbase.com/docs-server-DOC-14290--8.1--Document-Enforcing-CE-limitations/server/current/introduction/editions.html

https://preview.docs-test.couchbase.com/docs-server-DOC-14290--8.1--Document-Enforcing-CE-limitations/server/current/manage/manage-xdcr/xdcr-management-overview.html

You will need the Docs Team credentials on Confluence.

Noted changes in editions.adoc.
Noted changes in xdcr-management-overview.adoc
@RayOffiah RayOffiah self-assigned this May 11, 2026
@RayOffiah RayOffiah added the enhancement New feature or request label May 11, 2026
@RayOffiah RayOffiah requested review from ggray-cb and hyunjuV May 11, 2026 14:48
Copy link
Copy Markdown
Contributor

@ggray-cb ggray-cb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A minor typo and one inaccurate statement. Otherwise, looks great!


For more information, see https://blog.couchbase.com/couchbase-modifies-license-free-community-edition-package/[Couchbase Modifies License of Free Community Edition Package^],

For more information about how the new restrictions affect the experience of Community-Edition administrators., see xref:manage:manage-xdcr/xdcr-management-overview.adoc#xdcr-and-community-edition[XDCR and Community Edition] below.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Community-Edition administrators.,

remove period before comma here.

Data from the source is pushed to the target bucket by an XDCR agent, running on the source cluster, using the Database Change Protocol.

Note that XDCR can only be established between clusters whose numbers of vBuckets are equal: all supported platforms have _1024_ vBuckets except _MacOS_, which has _64_.
NOTE: XDCR can only be established between clusters whose numbers of vBuckets are equal: all supported platforms have 1024 vBuckets except macOS, which has 64.
Copy link
Copy Markdown
Contributor

@ggray-cb ggray-cb May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all supported platforms have 1024 vBuckets

That's not accurate any more. Magma buckets can have 128 or 1024 vBuckets on Windows and Linux. See https://docs.couchbase.com/server/current/learn/buckets-memory-and-storage/vbuckets.html

Maybe just remove the statement "all supported platforms have 1024 vBuckets except macOS, which has 64" and just link to the vBucket topic.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This entire note no longer applies the way it is written.

It should be something like:
Prior to Server 8.0, XDCR could only be established between buckets whose numbers of vBuckets were the same. Now, if all of the cluster versions in the replication topology are 8.0 and later, XDCR can be established between buckets with different numbers of vBuckets. While an 8.0 and later cluster can create an XDCR to a 7.x cluster bucket with a different number of vBuckets, a 7.x cluster can only create an XDCR to a bucket with the same number of vBuckets regardless of the target cluster version.

cc @nelio2k

* _Pausing_ and _Resuming_ replications: Once started, a replication is continuous; mutations on the source being constantly transmitted to the target.
Occasionally, for purposes of system maintenance, it may be desirable manually to pause a replication, and then resume it.
Information is provided in xref:manage:manage-xdcr/pause-xdcr-replication.adoc[Pause a Replication]; and xref:manage:manage-xdcr/resume-xdcr-replication.adoc[Resume a Replication].
* Pausing and Resuming replications: Once started, a replication is continuous mutations on the source being constantly transmitted to the target.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a ";" omitted, clouding the meaning.

Should be:
Once started, a replication is continuous; mutations on the source being constantly transmitted to the target.

Instead of:
Once started, a replication is continuous mutations on the source being constantly transmitted to the target.

Information is provided in xref:manage:manage-xdcr/pause-xdcr-replication.adoc[Pause a Replication] and xref:manage:manage-xdcr/resume-xdcr-replication.adoc[Resume a Replication].

* _Recovering Data_: In the event of data-loss, the *cbrecovery* tool can be used to restore data.
* Recovering Data: In the event of data-loss, the *cbrecovery* tool can be used to restore data.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@owend74
Is the cbrecovery tool documentation still good?

In the current documentation, it's documented here -- https://docs.couchbase.com/server/current/manage/manage-xdcr/recover-data-with-xdcr.html

cc @nelio2k

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its looks like it has not been modified in a while https://github.com/couchbase/couchbase-cli/blame/59bace859648b03ca0cf9fe89c1cf57dfd992157/cbrecovery

But should still be OK - although I suspect it is not regularly tested.

Copy link
Copy Markdown
Contributor

@hyunjuV hyunjuV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the XDCR Management Overview, there are changes needed:

  1. typo (left out a ";")
  2. The Note about XDCR and number of vBuckets needs to be updated for 8.0 and 8.1.
  3. Need to find out from engineering whether the cbrecovery info needs any updating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants