Check running queries to decide whether we should refresh a view #1837
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a running sequelize query times out, only the sequelize execution stops. The actual query in the database keeps running.
For some reason refresh of the
mv_organizations_cubetakes longer than even the extended timeout of 15 mins, we end up running multiple refreshes in the database, which creates unnecessary load on the database.We'll still need to figure out what's the reason for refreshes taking so long.
But in the meanwhile, we'll look into the database for running queries to see if there is already an ongoing one.