Skip to content

Commit 11e4abe

Browse files
nicktindallywangd
andauthored
Update docs/internal/GeneralArchitectureGuide.md
Co-authored-by: Yang Wang <[email protected]>
1 parent 45b5c7a commit 11e4abe

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/internal/GeneralArchitectureGuide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ There are two main types of network communication used in Elasticsearch:
1313
> [!NOTE]
1414
> Cross-cluster [replication](https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-ccr.html) and [search](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cross-cluster-search.html) use binary/TCP messaging for inter-cluster communication but this is out of scope for this section
1515
16-
The node that a REST request arrives at is called the "coordinating" node. Its job is to coordinate the execution of the request with the other nodes in the cluster and when the requested action is completed, return the response the REST client via HTTP.
16+
The node that a REST request arrives at is called the "coordinating" node. Its job is to coordinate the execution of the request with the other nodes in the cluster and when the requested action is completed, return the possibly aggregated response the REST client via HTTP.
1717

1818
By default, all nodes will act as coordinating nodes, but by specifying `node.roles` to be empty you can create a [coordinating-only node](https://www.elastic.co/guide/en/elasticsearch/reference/current/node-roles-overview.html#coordinating-only-node-role).
1919

0 commit comments

Comments
 (0)