Description
During a backup when getting errors from the storage layer e.g. a failed write (caused by the mutation/deletion callback in dcp.go) they will be logged, however, we simply ignore them and continue trucking. This is the wrong behavior; we should at the very least evaluate the errors and exit if they are serious.
Attachments
Issue Links
- duplicates
-
MB-24734 cbbackupmgr : no error when archive location is out of disk space
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to CBSE-7863 [ CBSE-7863 ] |
Affects Version/s | 6.0.3 [ 16164 ] | |
Affects Version/s | 6.0.4 [ 16502 ] |
Fix Version/s | 6.5.1 [ 16622 ] |
Labels | 6.0.5-candidate |
Link | This issue blocks MB-37192 [ MB-37192 ] |
Fix Version/s | 6.5.1 [ 16622 ] |
Labels | 6.0.5-candidate |
Fix Version/s | Mad-Hatter [ 15037 ] | |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Link | This issue blocks MB-37192 [ MB-37192 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |