Workers can consume more than one message at a time due to eventlet/greenthreads. The conf option rpc_thread_pool_size determines how many messages can theoretically be handled at once. Greenthread switching can happen any time a monkeypatched call is made.
Vish On Jul 21, 2014, at 3:36 AM, fdsafdsafd <[email protected]> wrote: > Hello, > recently, i use rally to test boot-and-delete. I thought that one > nova-scheduler will handle message sent to it one by one, but the log print > show differences. So Can some one how nova-scheduler handle messages? I read > the code in nova.service, and found that one service will create fanout > consumer, and that all fanout message consumed in one thread. So I wonder > that, How the nova-scheduler handle message, if there are many messages > casted to call scheduler's run_instance? > Thanks a lot. > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
