Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.1.0
-
None
-
Untriaged
-
Windows 64-bit
-
Unknown
Description
After writing to the mutation log, we assert on to check if the number of bytes written is greater than equal to 0. This isn't always the case as in the case of failures, we return -1. There needs to be better error handling in case of write failures to the mutation log.
Attachments
| For Gerrit Dashboard: MB-18476 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 61116,11 | MB-18476: Handle write failures more gracefully in the mutation log | sherlock | ep-engine | Status: MERGED | +2 | +1 |
| 61468,5 | MB-18476: Handle write failures more gracefully in the mutation log | watson | ep-engine | Status: MERGED | +2 | +1 |
| 61494,1 | MB-18476: Handle write failures more gracefully in the mutation log | master | ep-engine | Status: ABANDONED | 0 | 0 |
| 61527,2 | Merge remote-tracking branch 'couchbase/watson' into 'couchbase/master' | master | ep-engine | Status: MERGED | +2 | +1 |
| 64036,1 | Merge remote-tracking branch 'couchbase/sherlock' into watson | watson | ep-engine | Status: MERGED | +2 | +1 |
| 64117,1 | Merge remote-tracking branch 'couchbase/watson' into master | master | ep-engine | Status: MERGED | +2 | +1 |