Closed
Bug 1290803
Opened 9 years ago
Closed 9 years ago
Investigate sporadic redshift batch insert errors
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: robotblake, Assigned: robotblake)
References
Details
(Whiteboard: [SvcOps])
When this happens with dsmo_load, all processing stops until the process is restarted, in some cases the processing will continue to fail at the exact same spot.
|
Assignee | |
Comment 1•9 years ago
|
||
May need to reach out to Amazon to figure out what's going on.
|
|
Assignee | |
Updated•9 years ago
|
Assignee: bimsland → nobody
Priority: P2 → P3
|
|
Assignee | |
Updated•9 years ago
|
Priority: P3 → P2
|
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → bimsland
|
|
Assignee | |
Comment 2•9 years ago
|
||
I've upgraded the version of hindsight we're using and that seems to have resolved this issue, will reopen if we see it happen again.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•