hubcio opened a new pull request, #3738: URL: https://github.com/apache/iggy/pull/3738
The backup-side primary-liveness window was hardcoded at 5s (NORMAL_HEARTBEAT_TICKS). On oversubscribed hosts scheduling stalls exceed it, so backups elect a new primary although the old one is healthy, and client sessions die with the view change - loaded parallel integration runs failed 23 message_retrieval tests this way. Surface the window as [cluster] heartbeat_timeout on the server-ng config. ClusterConfig is forked into server_ng_config (like the tcp/quic/websocket forks) because the legacy struct sources its defaults from the legacy config.toml, which is frozen for ng-only knobs. The runtime converts the duration to consensus ticks and installs it before init, a validator enforces a 2s floor (the zero sentinels are rejected too), and a unit test pins the TOML default to the consensus built-in. The retrieval scenarios now run with a 60s window so box load cannot fake primary death. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
