-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The review on master branches are ready:
oslo.messaging with heartbeat off:
https://review.openstack.org/#/c/174929/
requirement changes: https://review.openstack.org/#/c/174930/
Once they are merged, I will backport them to stable/kilo and sync the
requirements to release oslo.messaging 1.8.2 with this new
requirements.:
- ---
Mehdi Abaakouk
mail: sil...@sileht.net
irc: sileht
Le 2015-04-17 15:54, Sean Dague a écrit :
It turns out a number of people are hitting -
https://bugs.launchpad.net/oslo.messaging/+bug/1436769 (I tripped over
it this morning as well).
Under a currently unknown set of conditions you can get into a
heartbeat
loop with oslo.messaging 1.8.1 which basically shuts down the RPC bus
as
every service is heartbeat looping 100% of the time.
I had py-amqp < 1.4.0, and 1.4.0 seems to have a bug fix for one of the
issues here.
However, after chatting with silent in IRC this morning it sounded like
the safer option might be to disable the rabbit heartbeat by default,
because this sort of heartbeat storm can kill the entire OpenStack
environment, and is not really clear how you recover from it.
All of which is recorded in the bug.
Proposed actions are to do both of:
- oslo.messaging release with heartbeats off by default (simulates
1.8.0
behavior before the heartbeat code landed)
- oslo.messaging requiring py-amqp >= 1.4.0, so that if you enable the
heartbeating, at least you are protected from the known bug
This would still let operators use the feature, we'd consider it
experimental, until we're sure there aren't any other dragons hidden in
there. I think the goal would be to make it default on again for
Marmoset.
-Sean
-----BEGIN PGP SIGNATURE-----
Version: OpenPGP.js v.1.20131017
Comment: http://openpgpjs.org
wsFcBAEBCAAQBQJVOQV9CRAYkrQvzqrryAAAUVkP/jV4VGtzM2PMk15FxYxM
WS1b46mu2G/J0U8hOuOcrV5G36KL3nzk3em4VEnSpPfihRLrk1Ufhi9P3Obc
DQyjNuImXUE/z4nx81pCarjk0nGeuoejHexvQP3lLn5lvd/r9nbjHkaUST9Y
yYG7GHq+j24FnQzjP84GS0tRp6DnSMqKs8OwPTg7oyGFUK9tbnkp+LqDRHnx
GqQTnb+yCs5b55VQJLOFf9IN/oPmsfSVYimtgq9MEmCXCLvWIF7AYQJMmy9Q
QG2fj1o/TPEUgOijT/15jDgEePek5EDC6RaNX0YCthUsE70DE/PFF8j1IIez
gojOO7rtkrvEi8f4P1qBbXDE2vOe9f9mYlZHxfAl8tDrT0VIoVTWKAXU/L2H
3MRMhTrnTRRZuyyLtKbIP76U+uCbHWaJaQPW/BJMYRUDAH6eNb2mSvHw3H7k
3BdVtkGRwmDCdoCxbm+T3rud2BiNpwcwmlFlLVqEphLhg/A+KMP+Kufw2DbG
SItejHMdfgAEgb/7xlJ6iKXU6Zy3fqX9ik2beQavlEqhiLtZWDXko4cHgQtd
sCLfg6a3Z394ZIUvGDXjMVX1l+CkoRg1+IBtqTCieqapuTILnsH0YHlmAfOi
dy5t1Cay4Ltgl38u8A9L4GBaVnoDmWaMiCFyHbL5Qit2pTxZkgcxa1SPdlKm
A2qk
=impF
-----END PGP SIGNATURE-----
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
