-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Run HealthCheck without saving the ExecSession
to the database
#25003
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Honny1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ac4e5b3
to
31172f4
Compare
ExecSession
to the database
31172f4
to
79dddb6
Compare
Ephemeral COPR build failed. @containers/packit-build please check. |
1 similar comment
Ephemeral COPR build failed. @containers/packit-build please check. |
a2e6f31
to
8434c76
Compare
…database Fixes: https://issues.redhat.com/browse/RHEL-69970 Signed-off-by: Jan Rodák <[email protected]>
8434c76
to
30e4aac
Compare
/packit retest-failed |
This PR should not merge until after
|
This PR creates a method to run the HealthCheck command without creating and deleting an
ExecSession
in the database.When HealthCheck is run using the original
exec
method, anExecSession
is created and deleted. This approach causes unexpectedly higher IO usage when synchronizing the container and creating and deletingExecSession
in the database.The new
healthCheckExec
function locks the container and creates theExecSession
locally without writing to the database. Executes a localExecSession
. As a result, the number of writes in the database has been reduced to zero.Verify reduction
/bin/true
as a health check that runs every 10 seconds.timeout 120 stap check.stp 0x23 > stap.out
check.stp
:sed -E 's/([0-9]+)//' stap.out | sort | uniq -c | sort -bn | tail -n 3
Fixes: https://issues.redhat.com/browse/RHEL-69970
Does this PR introduce a user-facing change?