Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alarm server -connect_secs and -stable_secs settings #2600

Merged
merged 4 commits into from
Mar 17, 2023

Conversation

kasemir
Copy link
Collaborator

@kasemir kasemir commented Mar 17, 2023

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.

@kasemir kasemir merged commit b20ccda into master Mar 17, 2023
@kasemir kasemir deleted the alarm_config_stblztn branch March 17, 2023 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant