Skip to content

[DOC-14256]: Feedback on Identifying the Orchestrator Node | Couchbase Docs#4113

Open
RayOffiah wants to merge 2 commits intorelease/7.6from
DOC-14256--Feedback-on-Identifying-the-Orchestrator-Node--Couchbase-Docs
Open

[DOC-14256]: Feedback on Identifying the Orchestrator Node | Couchbase Docs#4113
RayOffiah wants to merge 2 commits intorelease/7.6from
DOC-14256--Feedback-on-Identifying-the-Orchestrator-Node--Couchbase-Docs

Conversation

@RayOffiah
Copy link
Copy Markdown
Contributor

Fixed the version number in the JSON example.
Small corrections to grammar and punctuation.

…e Docs

Minor correction to version number. Small grammar and punctuation fixes.

Signed-off-by: Ray Offiah <ray.offiah@couchbase.com>
@RayOffiah RayOffiah requested a review from a team April 29, 2026 13:58
@RayOffiah RayOffiah self-assigned this Apr 29, 2026
@RayOffiah RayOffiah added the bug Something isn't working label Apr 29, 2026
Copy link
Copy Markdown

@Rebecca-Martinez007 Rebecca-Martinez007 left a comment

Choose a reason for hiding this comment

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

I left a small note about admonitions, but otherwise it LGTM. Let me know what you think and I'll aprove!

Comment thread modules/rest-api/pages/rest-identify-orchestrator.adoc Outdated
…e Docs

Minor corrections following review.

Signed-off-by: Ray Offiah <ray.offiah@couchbase.com>
Copy link
Copy Markdown

@Rebecca-Martinez007 Rebecca-Martinez007 left a comment

Choose a reason for hiding this comment

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

Left a small (not SOS) suggestion, but approving in case you need to get this out!

Note also that in cases where the cluster has undergone an unexpected network partition, different specified nodes may return different values.
[NOTE]
====
The location of the orchestrator may change at any time, including at a point after execution of the call but before the return of a value, meaning that the returned value is already incorrect.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
The location of the orchestrator may change at any time, including at a point after execution of the call but before the return of a value, meaning that the returned value is already incorrect.
* The location of the orchestrator may change at any time, including at a point after execution of the call but before the return of a value, meaning that the returned value is already incorrect.

====
The location of the orchestrator may change at any time, including at a point after execution of the call but before the return of a value, meaning that the returned value is already incorrect.

Also note that in cases where the cluster has undergone an unexpected network partition, different specified nodes may return different values.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
Also note that in cases where the cluster has undergone an unexpected network partition, different specified nodes may return different values.
* In cases where the cluster has undergone an unexpected network partition, different specified nodes may return different values.

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants