<div dir="ltr">I wrote those lines.<div><br></div><div>At that time, I tried a couple a publisher and a receiver at that scale. It was the receiver side what crashed trying to subscribe, the sender was completely fine.</div><div><br></div><div>Sadly I don't keep the test examples, I should have stored them in github or something. It shouldn't be hard to replicate though if you follow the oslo_messaging docs.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 20, 2017 at 9:58 AM, Matthieu Simonin <span dir="ltr"><<a href="mailto:matthieu.simonin@inria.fr" target="_blank">matthieu.simonin@inria.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
In the Neutron docs about RPCs and Callbacks system, it is said[1] :<br>
<br>
"With the underlying oslo_messaging support for dynamic topics on the receiver<br>
we cannot implement a per “resource type + resource id” topic, rabbitmq seems<br>
to handle 10000’s of topics without suffering, but creating 100’s of<br>
oslo_messaging receivers on different topics seems to crash."<br>
<br>
I wonder if this statements still holds for the new transports supported in<br>
oslo.messaging (e.g Kafka, AMQP1.0) or if it's more a design limitation.<br>
I'm interested in any relevant docs/links/reviews on the "topic" :).<br>
<br>
Moreover, I'm curious to get an idea on how many different resources a Neutron<br>
Agent would have to manage and thus how many oslo_messaging receivers would be<br>
required (e.g how many security groups a neutron agent has to manage ?) - at<br>
least the order of magnitude.<br>
<br>
Best,<br>
<br>
Matt<br>
<br>
<br>
<br>
[1]: <a href="https://docs.openstack.org/neutron/latest/contributor/internals/rpc_callbacks.html#topic-names-for-every-resource-type-rpc-endpoint" rel="noreferrer" target="_blank">https://docs.openstack.org/<wbr>neutron/latest/contributor/<wbr>internals/rpc_callbacks.html#<wbr>topic-names-for-every-<wbr>resource-type-rpc-endpoint</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br></div>