Runner drops log lines when the hub is briefly busy issue #8
closed: completed andymccall opened this · 0 comments
andymccall
During the oxygenhub runs at 00:40 and 01:01 the hub answered log appends and claims with HTTP 500 "database is locked", after its 5 s busy timeout. The runner dropped those log lines.
Transactions already begin IMMEDIATE (oxygenhub#21), so a writer held SQLite's lock for over 5 s. The likely cause is commits and checkpoints stalled while the host's disk is saturated by a release build.
The runner should retry server errors, and the hub should wait longer.
During the oxygenhub runs at 00:40 and 01:01 the hub answered log appends and claims with HTTP 500 "database is locked", after its 5 s busy timeout. The runner dropped those log lines.
Transactions already begin IMMEDIATE (oxygenhub#21), so a writer held SQLite's lock for over 5 s. The likely cause is commits and checkpoints stalled while the host's disk is saturated by a release build.
The runner should retry server errors, and the hub should wait longer.