Agree! Let someone know and keep going unless someone wants to interrupt it or do something. (Does there exist a mechanism already to do this?)
-----Original Message----- From: Russell Bryant [mailto:[email protected]] Sent: Tuesday, June 25, 2013 12:21 PM To: [email protected] Subject: Re: [openstack-dev] Should RPC consume_in_thread() be more fault tolerant? On 06/25/2013 03:15 PM, Ray Pekowski wrote: > > On Jun 25, 2013 1:09 PM, "Qing He" <[email protected] > <mailto:[email protected]>> wrote: >> >> Basically, when 'unexpected' happens, someone (e.g., operator) needs > to know about it and look into it to see if it is something benign or > fatal. If it is masked, the system may degrade overtime unnoticed into > unusable. > > The approach implemented in the patch is to log the exception and > retry at a rate of one per second. An alternative would be a log and > a > sys.exit() to kill the entire process. Be aware that the code > affected by this patch is rpc created dispatcher like threads. Let's > have a vote on which option is preferrable. I like it how it's implemented, *not* killing the process ... -- Russell Bryant _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
