auditor status files cause replicator to report errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Charles Hsu |
Bug Description
On a totally healthy working system the replicator finishes with log lines reporting errors:
May 18 18:38:48 saio object-6010: 954 successes, 8 failures
May 18 18:38:48 saio object-6010: 748 suffixes checked - 100.00% hashed, 0.00% synced
This is because build_jobs is incrementing errors for *all* devices when it encounters an unexpected file in the objects dir (in this cause the auditor_
There's no good logging around the event.
The object-replicator should expect the auditor status files to be in the objects dir. It should not report failures when their are none. If it encounters a condition which results in incrementing failures it should include good logging around the nature of the failure.
This was reported on the ML and I confirmed it:
http://
Changed in swift: | |
assignee: | nobody → Charles Hsu (charles0126) |
gah, reconstructor needs the same smarts:
May 17 16:29:35 STACO2 object- reconstructor: Unexpected entity in data dir: u'/srv/ node/s02z2ecd02 /objects- 1/auditor_ status_ ZBF.json'