| Issue Number | 4819 |
|---|---|
| Summary | Increase DB Timeout for GovDelivery Report |
| Created | 2020-04-29 11:40:03 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-04-29 15:19:27 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.261140 |
One of our weekly reports (GovDelivery) is failing because it is taking too long to create a connection to the DB in the middle of the night (DB needs its beauty sleep!)
We decided to increase the timeout setting for this report, bumping it up from the default of 120 seconds to five minutes in order to allow for more time to complete the connection and/or query.
Are you proposing that we raise the default to five minutes in
db.py rather than bumping it up for this report? (As we
discussed yesterday, there's a serious downside in making the user wait
a very long time only to find out that a report which would have
completed quickly when the systems are behaving properly is going to
fail.
Oops! Sorry, I looked at my notes that I had written before we talked. I adjusted the title.
Did you want this to go as a hotfix or as part of Leibniz?
I think Leibniz is fine.
Ready for a test spin on DEV. Default timeout for this job is now 300 seconds. You can override this with the named timeout parameter. The scheduler on DEV has been bounced to pick up the new version of the code.
We haven't had any DB connectivity issues in a while. Assuming the issue is fixed and the ticket can be closed.
Elapsed: 0:00:00.001723