[9.x] Always use the write PDO connection to read the just stored pending batch #43737
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.
Setting the
sticky
option tofalse
for a database connection with separate read/write database nodes, results in problems with finding a batchable job right after creation.This can happen because the read query is executed on a replicated read-only node directly after writing to the write node. If the select query is executed faster than the database replication takes place, then no batch is found. In that case an exception is thrown because jobs are added to a
null
batch.This PR fixes this problem by always using the write PDO connection for finding the just created batchable job in the
store()
method inDatabaseBatchRepository.php
.