hubcio opened a new pull request, #3768: URL: https://github.com/apache/iggy/pull/3768
A node that had ever served a client could no longer boot. WAL replay rebuilds the VSR client table and bootstrap reinstalls it, but the `set_clients_table_max` call added alongside the config knob ran afterwards and hard-asserts an empty table, so shard 0 panicked at startup and the process exited. Fresh boots were unaffected, which is why only restarts broke. Apply the configured capacity before the recovered table is installed rather than relaxing the assert. The setter rebuilds the table from scratch, so keeping it after the install would have traded the panic for silently dropping every resumed session. Recovery built its table from the compile-time default, which the install then propagated, leaving `[metadata] clients_table_max` inert across restarts. It now takes the configured value the same way it already takes `journal_slots`. -- 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]
