Alarm server -connect_secs and -stable_secs settings #2600
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #2597
The config and status messages are a kafka stream.
To get the "current" configuration, we wait until there is a pause in config messages.
Similarly, the alarm server waits for a pause in state messages to assume it knows the initial alarm state.
This timeout was 4 seconds, and #2597 made it configurable.
The actual issue, however, was a slow connection which required about 10 seconds until receiving the first message.
This adds separate "
-connect_secs
and-stable_secs
command line parameters.-connect_secs
, default 10, configures the wait for the initial message, while-stable_secs
is then used to wait for a pause in messages.These parameters apply to the
-import
,-export
and also the alarm server startup.