All of lore.kernel.org
 help / color / mirror / Atom feed
From: di.wang <di.wang@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre RPC visualization
Date: Mon, 03 May 2010 14:58:15 -0400	[thread overview]
Message-ID: <4BDF1CC7.5020502@oracle.com> (raw)
In-Reply-To: <4BDF1199.2030007@tu-dresden.de>

Michael Kluge wrote:
> Hi Andreas,
>
> Am 03.05.2010 15:20, schrieb Andreas Dilger:
>> On 2010-05-03, at 04:41, Michael Kluge wrote:
>>> I have a small problem understanding the logical order of the events.
>>> Here is one example from the logs where the client reports an RPC as
>>> completed before the server says that it has finished the RPC handling.
>>> The difference is about 1.5 ms.
>>>
>>> Is that due to the fact that the server waits until the client has
>>> ack'ed the result of the RPC? Or are the clocks between the servers not
>>> well synchronized? Or are the timestamps in the logfile sometimes not
>>> correct (log message could not be flushed or whatever)?
>>
>> The timestamps on the log messages are only as accurate as the clocks on
> > the nodes.  Lustre can run without synchronized clocks, using the 
> client
> > clock as the basis for the timestamps, but Lustre makes no effort to
> > synchronize the client clocks.  For that you need to use NTP (easiest)
>>  or adjust the timestamps in the logs based on messages like this.
>
> OK, so logically the "Completed RPC" on the client side is supposed to 
> show up after the server has written his "Handled RPC" to its log (if 
> clocks are snyc'ed perfectly).
Yes.
>
> One more question: RPC 1334380768266400 (in the log WangDi sent me) 
> has on the client side only a "Sending RPC" message, thus missing the 
> "Completed RPC". The server has all three (received,start work, done 
> work). Has this RPC vanished on the way back to the client? There is 
> no further indication what happend. The last timestamp in the client 
> log is:
> 1272565368.228628
> and the server says it finished the processing of the request at:
> 1272565281.379471
> So the client log has been recorded long enough to contain the 
> "Completed RPC" message for this RPC if it arrived ever ...
Logically, yes. But in some cases, some debug logs might be abandoned 
for some reasons(actually, it happens not rarely), and probably you need 
maintain an average time from server "Handled RPC" to client "Completed 
RPC", then you just guess the client "Completed RPC" time in this case.

Thanks
WangDi

>
>
> Regards, Michael
>

  parent reply	other threads:[~2010-05-03 18:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000c01cae6ee$1d4693d0$57d3bb70$@barton@oracle.com>
2010-04-29  1:25 ` [Lustre-devel] (no subject) di.wang
2010-04-29  1:49   ` Andreas Dilger
2010-04-29  2:04     ` di.wang
2010-04-29  4:48   ` [Lustre-devel] Lustre RPC visualization Michael Kluge
     [not found]     ` <4BD9CF75.8030204@oracle.com>
2010-05-03  8:41       ` Michael Kluge
2010-05-03 13:20         ` Andreas Dilger
2010-05-03 18:10           ` Michael Kluge
2010-05-03 18:57             ` Robert Read
2010-05-03 18:58             ` di.wang [this message]
2010-05-03 19:32               ` Michael Kluge
2010-05-03 19:52                 ` di.wang
2010-05-03 20:04                   ` Michael Kluge
2010-05-16  9:29                   ` Michael Kluge
2010-05-16 13:12                     ` Eric Barton
2010-05-17  4:52                       ` Michael Kluge
2010-05-17  3:24                     ` Andrew Uselton
2010-05-17  5:53                       ` Michael Kluge
     [not found]                     ` <009101caf4f9$67e1dd50$37a597f0$%barton@oracle.com>
2010-05-17  3:39                       ` Shipman, Galen M.
2010-05-17  5:59                         ` Michael Kluge
2010-05-25 12:03                     ` Michael Kluge
     [not found]                       ` <4BFC7177.9000808@oracle.com>
2010-05-28 14:54                         ` Michael Kluge
     [not found]                           ` <4BFFA456.7030502@oracle.com>
     [not found]                             ` <C671351E-110C-4D2C-B216-4E8BE23A943A@oracle.com>
     [not found]                               ` <1FF3D25F-3369-462E-9651-62D56319612A@tu-dresden.de>
     [not found]                                 ` <D29ED098-3DEB-4AF4-AA68-B52B4E2BF5EA@oracle.com>
     [not found]                                   ` <4C04F3F0.9040708@oracle.com>
     [not found]                                     ` <001601cb01a3$546c93d0$fd45bb70$%barton@oracle.com>
2010-06-01 12:12                                       ` di.wang
2010-06-01 17:03                                         ` Andreas Dilger
2010-06-01 19:39                                           ` Michael Kluge
2010-06-16  8:46                                             ` Michael Kluge
2010-06-16 14:50                                               ` Andreas Dilger
2010-06-17 14:02                                                 ` Michael Kluge
     [not found]                                                   ` <4169315E-9A94-4430-8970-92068222EF15@oracle.com>
2010-06-20 20:44                                                     ` Michael Kluge
2010-06-22 15:12                                                       ` Michael Kluge
2010-06-23 10:29                                                         ` Alexey Lyashkov
2010-06-23 11:50                                                           ` Michael Kluge
2010-06-23 12:09                                                             ` Alexey Lyashkov
2010-06-23 12:38                                                               ` Michael Kluge
2010-06-23 15:55                                                             ` Andreas Dilger
2010-06-24  8:01                                                               ` Michael Kluge
2010-06-01 15:58                                     ` Eric Barton
2010-09-22 13:46                               ` Michael Kluge
2010-09-22 18:28                                 ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BDF1CC7.5020502@oracle.com \
    --to=di.wang@oracle.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.