*** This bug is a duplicate of bug 1665215 *** https://bugs.launchpad.net/bugs/1665215
** This bug has been marked a duplicate of bug 1665215 performance degradation in agent<->server port wiring process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1735427 Title: Timeout in RPC method get_devices_details_list_and_failed_devices cannot be fixed by increasing the timeout to infinity Status in neutron: Incomplete Bug description: We are running a big production public cloud with Openstrack Newton. However looking at the code what I show here should affect also master. In neutron.conf we have: rpc_response_timeout=240 we often hit Timeout in RPC method get_devices_details_list_and_failed_devices no matter how big we set the RPC timeout. The problem is that when calling this function: https://github.com/openstack/neutron/blob/5fc8e47786c91f76d253010b194bd5637de895b8/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1514 the 'devices' argument can be very big without any limit, generating huge RPC calls and huge database queries. As an operator I would propose to paginate the list to break the thing into smaller RPC calls. Please note that `update_device_list` is also unpaginated. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1735427/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp