Is there any way to collect object-level I/O access traces in Ceph?

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? Thanks! LW -- To unsubscribe from this list: send the line unsubscribe

Re: Is there any way to collect object-level I/O access traces in Ceph?

search in the log file to locate the object operations? Thanks! LW On Fri, Jan 16, 2015 at 4:21 PM, Gregory Farnum g...@gregs42.com wrote: On Fri, Jan 16, 2015 at 11:28 AM, Lipeng Wan lipengwa...@gmail.com wrote: Dear all, Does Ceph provide a way to collect object-level I/O access traces

Question about the test() function in CrushTester class

Hi guys, I am now trying to use crushtool.cc to test crush algorithm. First, I build a new crush map using crushtool.cc and all the devices have the maximum weight (0x1). Then I assign different weights to devices using the --weight option and run the test() function. It seems that during the

question about the data structure of crush_map

Hi guys, I am reading the source code of ceph and trying to understand the data structure of crush_map. Now I am confused by the use of struct crush_bucket **buckets in function int crush_do_rule(...) in src/crush/mapper.c. It seems that the index of array map-buckets[] could be negative (see

Re: question about the data structure of crush_map

means osds. On 2 December 2013 11:20, Lipeng Wan lipengwa...@gmail.com wrote: Hi guys, I am reading the source code of ceph and trying to understand the data structure of crush_map. Now I am confused by the use of struct crush_bucket **buckets in function int crush_do_rule(...) in src/crush