Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase max execution timeout for a specific query. #24486

Merged
merged 2 commits into from Aug 27, 2018

Conversation

sureshc
Copy link
Contributor

@sureshc sureshc commented Aug 27, 2018

Changes to the nightly contact rollups job to support multi auth appear to be causing the job to fail because at a specific query is taking longer than the maximum query execution timeout (30 seconds) currently configured on the production database. Use an optimizer hint to override the global timeout for this specific query.

Copy link
Contributor

@wjordan wjordan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not very comfortable with any query to the production database taking longer than 30 seconds unless there's a specific necessary reason that it can't be avoided, since the reporting DB is our usual target for offline, long-running analytics queries like this. I'm OK with this PR but only as a temporary fix to be followed up on later.

@sureshc sureshc merged commit b082643 into staging Aug 27, 2018
@sureshc sureshc deleted the increase-contact-rollups-query-execution-time branch August 27, 2018 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants