If you're looking at what objects the MDS touches, it's probably easiest to set "debug ms = 1" in the mds config file. Then you can grep out the outgoing message lines and sed out the actual objects they're hitting. Something like the upcoming tracepoints would be easier to program against, but the MDS hits the Objecter directly so I'm not sure if they'd work. -Greg On Fri, Jan 16, 2015 at 4:06 PM, Lipeng Wan <lipengwan86@xxxxxxxxx> wrote: > Hi Greg, > > Thanks for your reply. > I found that in /var/log/ceph directory on each node, there are > several log files in it, > such as ceph-client.admin.log, ceph-mds.ceph-node1.log, etc., which > log file should I look at? Maybe the "ceph-mds.ceph-node1.log"? > Specifically, is there any keyword I can search in the log file to > locate the object operations? > Thanks! > LW > > On Fri, Jan 16, 2015 at 4:21 PM, Gregory Farnum <greg@xxxxxxxxxxx> wrote: >> On Fri, Jan 16, 2015 at 11:28 AM, Lipeng Wan <lipengwan86@xxxxxxxxx> wrote: >>> Dear all, >>> >>> Does Ceph provide a way to collect object-level I/O access traces? >>> Specifically, can we collect the traces to record how many times each >>> object has been accessed (read, write, etc.) during a fixed period of >>> time? >> >> I don't think we have any programmatic access, but depending on what >> you need it for you could enable messenger logging (or filestore >> logging, depending on what exactly you want) and count the references >> there. >> -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
