Thank you for the explanation, Mehdi. About the "critical issues" mentioned in the commits, as i understand:
[1] seems just socket timeout issue, and admins can adjust those kernel params themselves. [2] and [3] truly a problem about the heartbeat implementation, but it says the fix is a part of py-amqp 1.4.0, and the dependency with kombu was not specified. [4] is a bug of kombu's autoretry method which is said to be fixed in kombu 3.0.0, it is not directly related to heartbeat. Am I missing something else? [1]: https://bugs.launchpad.net/oslo.messaging/+bug/1436788 [2]: https://bugs.launchpad.net/oslo.messaging/+bug/1436769 [3]: https://github.com/celery/py-amqp/issues/6 [4]: https://bugs.launchpad.net/oslo.messaging/+bug/1408830 On Tue, Oct 27, 2015 at 2:41 PM, Mehdi Abaakouk <[email protected]> wrote: > > Le 2015-10-27 04:22, me,apporc a écrit : > >> But i found in the changelog history of kombu [1], heartbeat support was >> added in version 2.5.0, so what's the point for ">= 3.0.7". Thanks. >> > > The initial heartbeat implementation have some critical issues for > oslo.messaging that was fixed since kombu 3.0.7 and py-amqp 1.4.0. > > --- > Mehdi Abaakouk > mail: [email protected] > irc: sileht > -- Regards, apporc
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
