Grab watchdog lock before checking connection status #636
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.
Before we first check whether the connection is alive, then kick the
watchdog and only then grab the lock to make the SQL query. There's a
race condition in this as sketched below, where the watchdog acquires
the lock and closes the connection after we check that it's still alive,
but before we acquire the lock.
The solution is to protect also the checking of the connection with the
same lock, so that closing of the connection happens only before or
after we checked the connection and executed our query.
@prince-mathews Please check whether your issue from the meeting persist with this branch.