What is the role of a coordinator node in Cassandra?

Any node in a Cassandra cluster can act as a coordinator for a given client request — there is no dedicated coordinator node or single point of entry, unlike a master node in other systems.

• It receives the client's query and identifies, using the token ring and the partitioner, which nodes actually own the requested partition.
• For writes, it forwards the mutation to all owning replicas and waits for the number of acknowledgements required by the consistency level.
• For reads, it queries enough replicas to satisfy the consistency level, merges the responses, and may trigger a read repair.
• It also applies the retry policy, timeout handling, and (in multi-datacenter setups) routes requests across datacenters as needed.

Because every node can be a coordinator, clients typically connect to any node in the cluster, and drivers use a token-aware load balancing policy so the node contacted is often already a replica for the data, avoiding an unnecessary network hop.

The coordinator itself does not need to own the data being requested — its job is purely request routing and response aggregation for that one query.