On Mon, Mar 05, 2018 at 12:55:52PM -0500, Jonathan D. Proulx wrote:
:Hi All,
:
:I've recently noticed my deep scrubs are EXTREAMLY poorly
:distributed. They are stating with in the 18->06 local time start
:stop time but are not distrubuted over enough days or well distributed
:over the range of days they have.
:
:root@ceph-mon0:~# for date in `ceph pg dump | awk '/active/{print $20}'`; do date +%D -d $date; done | sort | uniq -c
:dumped all
: 1 03/01/18
: 6 03/03/18
: 8358 03/04/18
: 1875 03/05/18
:
:So very nearly all 10240 pgs scrubbed lastnight/this morning. I've
:been kicking this around for a while since I noticed poor distribution
:over a 7 day range when I was really pretty sure I'd changed that from
:the 7d default to 28d.
So for posterity I was looking at the wrong field, D'oH!
The unstructured output of `ceph pg dump` has spaces in the date
string fields "2018-03-19 01:13:45.997550" so counting off the header
line does not get the field you think it does.
In my case $20 is actually part of the "SCRUB_STAMP" not
"DEEP_SCRUB_STAMP" so it *looks* like hwat I expect "%Y-%m-%d" but
isn't the right "%Y-%m-%d"...
The rightest thing would be to use structured output like `ceph pg
dump -f json-pretty`.
ceph pg dump -f json-pretty | jq '.pg_stats[].last_deep_scrub_stamp'
now if only I can get jq's strptime to swollow the fractional seconds
in the string this spits out (unix timestame would have ben better
than formatted time atleast in json and xml outputs)
Ooops,
-Jon
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
