Cluster configuration is now synchronized before Cored starts
Details
| Detail name | Value |
|---|---|
| Changelog Number | 22788 |
| Type | Bug |
| Status | Open |
| Affected Versions | Exasol 6.2.2 |
Description
A node could start Cored without installing the cluster's configuration. When the node's local CoredPort differed from the cluster's, the node started an isolated Cored instance and remained at wait_for_nodes without joining cluster membership. This affected adding a node and rebooting an existing node. A node booting while the cluster was electing a master was affected through the same path, because the ConfD /master response was not validated.
Workaround
Align the node's local EXAConf with the cluster configuration and reboot the node.
Fix
A node now installs the EXAConf obtained from the active master before Cored starts, whether or not registration is required. Synchronization is mandatory once a node answers on the ConfD port, and startup fails after a fixed deadline instead of continuing from the local EXAConf. Startup from the local EXAConf remains available while no node answers on the ConfD port.
