Skip to content

[docs] coordinator service#76

Merged
cendhu merged 2 commits into
hyperledger:mainfrom
cendhu:coord-doc
Jul 14, 2025
Merged

[docs] coordinator service#76
cendhu merged 2 commits into
hyperledger:mainfrom
cendhu:coord-doc

Conversation

@cendhu

@cendhu cendhu commented Jul 9, 2025

Copy link
Copy Markdown
Contributor

Type of change

  • Documentation update

Description

This document explains the internals of coordinator.

Related issues

This document explains the internals of coordinator.

Signed-off-by: Senthil Nathan N <cendhu@gmail.com>
@cendhu cendhu requested a review from Copilot July 9, 2025 15:05
@cendhu cendhu self-assigned this Jul 9, 2025
@cendhu cendhu added the documentation Improvements or additions to documentation label Jul 9, 2025

Copilot AI left a comment

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.

Pull Request Overview

This PR adds a new documentation page detailing the internal design and workflow of the Coordinator service.

  • Introduces coordinator service responsibilities and architecture
  • Outlines configuration, workflow steps, dependency graph details, gRPC API, and failure recovery
  • Provides code snippets and links to relevant manager components
Comments suppressed due to low confidence (3)

docs/coordinator.md:128

  • [nitpick] Inconsistent naming: the component is referred to as both "Validator Committer Manager" and "Validator-Committer Manager". Please choose one style and apply it uniformly.
in conjunction with a [`Policy Manager`](https://github.com/hyperledger/fabric-x-committer/blob/main/service/coordinator/policy_manager.go), ensures that all `Signature Verifier` services are updated with the new endorsement policy for that namespace. 

docs/coordinator.md:141

  • [nitpick] LaTeX/math mode syntax may not render properly in GitHub-flavored Markdown. Consider switching to inline code or plain-text arrows (e.g., T_j -> T_i (rw(k))).
1.  **Read-Write Dependency ($T_{i}\xleftarrow{rw\mbox{(}k\mbox{)}}T_{j}$):** $T_i$ writes to key `k`, and a later transaction $T_j$ reads the *previous* version of `k`.

docs/coordinator.md:13

  • [nitpick] The ampersand in the section title generates anchors with double hyphens. Verify these links work as expected or simplify the heading to avoid special characters in the anchor ID.
    * [Step 2. Dependency Analysis & Parallel Validation](#step-2-dependency-analysis--parallel-validation)

@cendhu cendhu requested a review from liran-funaro July 9, 2025 15:06

@liran-funaro liran-funaro left a comment

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.

LGTM

Comment thread docs/coordinator.md
Comment on lines +141 to +146
1. **Read-Write Dependency ($T_{i}\xleftarrow{rw\mbox{(}k\mbox{)}}T_{j}$):** $T_i$ writes to key `k`, and a later transaction $T_j$ reads the *previous* version of `k`.
If $T_i$ is valid, $T_j$ must be invalid because it read a stale value.
2. **Write-Read Dependency ($T_{i}\xleftarrow{wr\mbox{(}k\mbox{)}}T_{j}$):** $T_i$ reads key `k`, and a later transaction $T_j$ writes to `k`. This dependency is used
to enforce commit order. $T_j$ cannot be committed before $T_i$ is finalized, otherwise $T_i$'s read would become stale, violating the original block order.
3. **Write-Write Dependency ($T_{i}\xleftarrow{ww\mbox{(}k\mbox{)}}T_{j}$):** Both $T_i$ and $T_j$ write to the same key `k`. This dependency ensures $T_j$ is not
committed before $T_i$, preventing $T_j$'s write from being overwritten and lost.

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.

Read-read dependency should also be mentioned

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Read-read is not a dependency. No conflicts between transactions when two transactions are reading the same key without writes.

Co-pilot reviews.

Signed-off-by: senthil <cendhu@gmail.com>
@cendhu cendhu merged commit 44f2a1a into hyperledger:main Jul 14, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants