yahoo-eng-team team mailing list archive

[OpenStack Infra <1847747@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/688147
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=b104f254ab43d5e2589e845eff84b1bd096cb42d
Submitter: Zuul
Branch:    master

commit b104f254ab43d5e2589e845eff84b1bd096cb42d
Author: LIU Yulong <i@xxxxxxxxxxxx>
Date:   Fri Oct 11 23:22:23 2019 +0800

    Add RPC incoming and reply log
    
    Typically a simple log will not narrow down the
    performance, but give us more information about
    the service status.
    
    Change-Id: I51c8f2743dd39cccd3d1d021d3c50dc09f70cd97
    Closes-Bug: #1847747


** Changed in: oslo.messaging
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1847747

Title:
  [RPC] digging RPC timeout for client and server

Status in neutron:
  New
Status in oslo.messaging:
  Fix Released

Bug description:
  RPC timeout can be found frequently, but we have no statistical data
  for it. A simple log can help. Since all the projects are using
  oslo.messaging as midlware between services and message queue, we can
  add a log in it, something like this, a local test:

  2019-10-11 19:23:05.703 40774 INFO oslo_messaging.rpc.server [-] Receive incoming message with id cf4ab75b89e64458bc989c709add43cf and method: sync_routers.
  2019-10-11 19:29:19.781 40774 INFO oslo_messaging.rpc.server:188 [None req-e33a11a2-64cd-4aea-b801-7689996a8ace - - - - -] Replied message with id cf4ab75b89e64458bc989c709add43cf and method: sync_routers. Time elapsed: 374.078

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1847747/+subscriptions