internal-client transaction IDs pollute other daemon messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
New
|
Undecided
|
Unassigned |
Bug Description
Running the expirer when there's nothing to in the queue gives me logs like
object-expirer: Starting 731149
swift: - - 30/Apr/
object-expirer: Pass completed in 0s; 0 objects expired (txn: txb27d52a49c4f4
object-expirer: Exited 731149 (txn: txb27d52a49c4f4
Having a transaction ID logged for the internal-client request is good and proper, but strange for the "Pass completed" and "Exited" messages -- the notion of a "transaction" should have ended as soon as we handed the response back to the caller.
Note that we've previously worked around this in the sharder, but it'd be better-addressed in internal_client itself -- see https:/