Duplicate marker regex fails to match (HTTP 503)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
Critical
|
Flavio Percoco |
Bug Description
When a duplicate key is detected prior to insertion, the storage driver is supposed to know how to extract the marker for that key from the error string.
Since recent updates, the regex has started failing as follows:
'''
2013-08-12 10:52:13.361 24036 ERROR marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
2013-08-12 10:52:13.361 24036 TRACE marconi.
'''
Changed in marconi: | |
status: | New → Confirmed |
Changed in marconi: | |
assignee: | nobody → Flavio Percoco (flaper87) |
Changed in marconi: | |
status: | Fix Committed → Fix Released |
milestone: | none → havana-3 |
Duplicate key errors are expected when the service attempts to process multiple inserts in parallel, and two messages end up with the same marker. Normally this situation is handled with retry logic, but it looks like the regex in the logic is borked.