Fix quorum handling in DWAd for partitions where middle nodes were removed
Details
| Detail name | Value |
|---|---|
| Changelog Number | 22130 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.33.0 |
| Resolution Date | 2025-02-27 |
Description
Previously, removed nodes were still effectively counted as part of the partition size, so a partition like [11 … … … 15] could look like 5 nodes even though only 2 active nodes remained. That made DWAd think quorum was lost when it should still be achievable.
This error was observed in a multi-cluster database and as a result DB couldn’t be stopped or started.
Workaround
Avoid or undo “middle-node removal” topologies; keep only the surviving nodes in the partition view if possible.
Fix
- Adjusts DWAd quorum logic so removed nodes don’t count against quorum in affected partition scenarios.
- Addresses cases like [11 … … … 15] (dead nodes in between active nodes), where logical partition size was misleading versus active node count.
