Run HealthCheck without saving the ExecSession
to the database
#25003
+97
−26
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.
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
TBD
Does this PR introduce a user-facing change?