Bug 1326734

Summary: Need an admin-friendly log file to check multisite sync status
Product: Red Hat Ceph Storage Reporter: shilpa <smanjara>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED NOTABUG QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.0CC: cbodley, ceph-eng-bugs, kbader, kdreyer, mbenjamin, owasserm, smanjara, sweil, yehuda
Target Milestone: rcKeywords: FutureFeature
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-02 14:29:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description shilpa 2016-04-13 11:53:27 UTC 
Description of problem:
As an admin I would like to be able to see the sync status of objects in logs in a multisite configuration. Currently I can get the number of shards that are to be synced by checking radosgw-admin command "sync status". But it would be easier to check what objects need to be synced and corresponding errors upon failure in rgw log file in /var/log.
Comment 2 shilpa 2016-04-13 12:13:11 UTC 
Upstream tracker: http://tracker.ceph.com/issues/15483
Comment 3 Matt Benjamin (redhat) 2016-04-13 12:50:58 UTC 
Are you thinking of this as a production setup?  Seems like this may generate a potentially very large increase in log traffic at a realistic scale.
Comment 4 shilpa 2016-04-13 13:16:36 UTC 
(In reply to Matt Benjamin (redhat) from comment #3)
> Are you thinking of this as a production setup?  Seems like this may
> generate a potentially very large increase in log traffic at a realistic
> scale.

May be the shard numbers could be logged. That way I can atleast see what shard has failed. We could use that shard index to look up the rgw pools to see what files the shard contains. Or logging the objects that have failed to sync would be helpful. Not sure if it is feasible.
Comment 5 Yehuda Sadeh 2016-04-22 17:56:31 UTC 
There is a log that logs failed sync operations. You can see that via:

$ radosgw-admin sync error list
Comment 6 Ken Dreyer (Red Hat) 2016-04-26 21:04:27 UTC 
Is the command in comment #5 enough to close this bug?
Comment 7 shilpa 2016-05-02 14:28:54 UTC 
> There is a log that logs failed sync operations. You can see that via:
> 
> $ radosgw-admin sync error list

Thanks that works.