Disable propagateCreateError by default #3132
Closed
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.
The attribute propagateCreateError should be set to false by default to prevent unexpected
Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
error.Explanation:
The propagateCreateError is set to true by default in Knex and throws a TimeoutError if the first create connection to the database fails, preventing tarn (the connection pool manager) from re-connecting automatically.
The solution is to set propagateCreateError to false thus enabling knex to automatically reconnect on create connection failure, instead of throwing the error, and only throwing it when the acquireTimeoutMillis has passed, as defined by tarn
Related issues:
#1381 #1382 #1655 #2445 strapi/strapi#2790 #1875 #1909 #2302 #2141 #1264