Re: Unique identifier in osd debug log to track ONE process from beginning to end

[Gregory Farnum <greg@xxxxxxxxxxx>]

This is harder than it sounds, but you can get a broad picture by looking for all the instances of the client request string (I believe it's the one from the incoming message, but I'm not at a computer to check). It outputs all the key points with that tag, and you can look at what's going on in the vicinity of those points for more.

-Greg

On Wednesday, February 12, 2014, Mihály Árva-Tóth <mihaly.arva-toth@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello,

I have got strange OSD slowing issue (always on primary OSD): I turned on --debug-log 30/30 to all OSDs, and I would like to track one process (for example write an object) in the log from the beginning to end without annoying other log rows (which are related another processes). Can you put an unique ID which joins a single process to one trackable feed?

Thank you!

--

Best regards,

Mihály Árva-Tóth

System Engineer

Virtual Call Center GmbH

Address: 23-33  Csalogány Street, Budapest 1027, Hungary

Tel: +36 1 999 7400

Mobile: +36 30 473 9256

Fax: +36 1 999 7401

E-mail: mihaly.arva-toth@xxxxxxxxxxxxxxxxxxxxxx

Web: www.virtual-call-center.eu

-- 
Software Engineer #42 @ http://inktank.com | http://ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com