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

Add systemd watchdog and adjust reload behaviour #5996

Merged
merged 1 commit into from
Jan 21, 2018

Conversation

Crunsher
Copy link
Contributor

@Crunsher Crunsher commented Jan 17, 2018

TODO:

  • docs
  • windows

@dgoetz
Copy link
Contributor

dgoetz commented Jan 17, 2018

@Crunsher: Nice work, have you also thought about send a status to systemd like mod_systemd for httpd does? Having some of the internal performance data or states like config dump to database done in a status line could be a nice feature.

@Crunsher
Copy link
Contributor Author

Not for this one, please create a new issue for additional status messages. The big change with this PR is the change to how we handle our reload (so the watchdog does not starve)

@gunnarbeutner gunnarbeutner added the enhancement New feature or request label Jan 18, 2018
@Crunsher Crunsher force-pushed the feature/watchdog-2287 branch from 152b688 to 7f0a66a Compare January 19, 2018 13:44
@Crunsher Crunsher force-pushed the feature/watchdog-2287 branch from 7f0a66a to c418a96 Compare January 19, 2018 15:52
@Crunsher Crunsher requested a review from dnsmichi January 19, 2018 15:53
@gunnarbeutner
Copy link
Contributor

LGTM. 👍

@gunnarbeutner gunnarbeutner merged commit 5d464a9 into master Jan 21, 2018
@gunnarbeutner gunnarbeutner deleted the feature/watchdog-2287 branch January 21, 2018 04:18
@gunnarbeutner gunnarbeutner added this to the 2.9.0 milestone Jan 21, 2018
dnsmichi pushed a commit that referenced this pull request May 3, 2019
This follows the same principle as with the shutdown handler,
and was introduced with the changed reload handling with 2.9.
Previously IsShuttingDown() was sufficient which got set at one
location.

SigUsr2 as handler introduced a new location where m_ShuttingDown
is not necessarily set yet. Since this handler gets called when
l_Restarting is enabled, we'll use this flag to avoid config update
events resulting in object deactivation (object->IsActive() always
returns false).

refs #5996
refs #6691
refs #6970

fixes #7125
dnsmichi pushed a commit that referenced this pull request May 16, 2019
This follows the same principle as with the shutdown handler,
and was introduced with the changed reload handling with 2.9.
Previously IsShuttingDown() was sufficient which got set at one
location.

SigUsr2 as handler introduced a new location where m_ShuttingDown
is not necessarily set yet. Since this handler gets called when
l_Restarting is enabled, we'll use this flag to avoid config update
events resulting in object deactivation (object->IsActive() always
returns false).

refs #5996
refs #6691
refs #6970

fixes #7125

(cherry picked from commit 78e24c5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants