Replication‑factor misconfiguration blocks writes after node failure

Goal

The cluster should continue to accept writes even when a node goes down, maintaining the configured replication‑factor.

Constraints & Uncertainty

Replication‑factor is set to 3 but the cluster only has 2 active nodes. The write operation blocks and errors appear in the logs. It is unclear whether the failure is due to the replication‑factor exceeding the node count, heartbeat‑interval delays, or another namespace setting.

Questions

• Is the replication‑factor value greater than the current number of live nodes?
• Could the heartbeat‑interval or heartbeat‑mode be delaying failure detection and causing write blocks?
• What cluster‑wide configuration changes would allow writes to succeed while preserving the desired level of redundancy?