Bug 1342629
| Summary: | seeing rabbitmq is reporting heartbeat timeout to some nodes | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | bigswitch <rhosp-bugs-internal> |
| Component: | rabbitmq-server | Assignee: | Peter Lemenkov <plemenko> |
| Status: | CLOSED DUPLICATE | QA Contact: | Udi Shkalim <ushkalim> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 (Liberty) | CC: | apevec, jeckersb, lhh, rhosp-bugs-internal, srevivo |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-oslo-messaging-1.8.3-4.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-21 21:21:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
(In reply to bigswitch from comment #0) > Description of problem: > Seen in Dell scale setup with 299 compute nodes and three controller. notice > on rabbitmq log that it is reporting heartbeat timeout to some nodes. > The network is stable at that time and no network event is going on. want to > know if this is acceptable and if there is any impact to the overcloud > > =INFO REPORT==== 26-May-2016::00:18:28 === > -- > =ERROR REPORT==== 26-May-2016::00:18:44 === > closing AMQP connection <0.14519.1> (172.17.1.68:41262 -> 172.17.0.14:5672): > {heartbeat_timeout,running} > > =INFO REPORT==== 26-May-2016::00:18:45 === > -- > =ERROR REPORT==== 26-May-2016::00:19:09 === > closing AMQP connection <0.384.0> (172.17.0.172:58136 -> 172.17.0.14:5672): > {heartbeat_timeout,running} > > =ERROR REPORT==== 26-May-2016::00:19:09 === > closing AMQP connection <0.478.0> (172.17.0.86:52691 -> 172.17.0.14:5672): > {heartbeat_timeout,running} > > =ERROR REPORT==== 26-May-2016::00:19:09 === > closing AMQP connection <0.462.0> (172.17.0.86:52690 -> 172.17.0.14:5672): > {heartbeat_timeout,running} > > Version-Release number of selected component (if applicable): > RHOSP 8 What's the version of python-oslo-messaging ? I believe it might be the same as bug 1295896. (In reply to bigswitch from comment #0) How's it going? Do you still see these issues? Closing this as a duplicate of bug 1295896. *** This bug has been marked as a duplicate of bug 1295896 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: Seen in Dell scale setup with 299 compute nodes and three controller. notice on rabbitmq log that it is reporting heartbeat timeout to some nodes. The network is stable at that time and no network event is going on. want to know if this is acceptable and if there is any impact to the overcloud =INFO REPORT==== 26-May-2016::00:18:28 === -- =ERROR REPORT==== 26-May-2016::00:18:44 === closing AMQP connection <0.14519.1> (172.17.1.68:41262 -> 172.17.0.14:5672): {heartbeat_timeout,running} =INFO REPORT==== 26-May-2016::00:18:45 === -- =ERROR REPORT==== 26-May-2016::00:19:09 === closing AMQP connection <0.384.0> (172.17.0.172:58136 -> 172.17.0.14:5672): {heartbeat_timeout,running} =ERROR REPORT==== 26-May-2016::00:19:09 === closing AMQP connection <0.478.0> (172.17.0.86:52691 -> 172.17.0.14:5672): {heartbeat_timeout,running} =ERROR REPORT==== 26-May-2016::00:19:09 === closing AMQP connection <0.462.0> (172.17.0.86:52690 -> 172.17.0.14:5672): {heartbeat_timeout,running} Version-Release number of selected component (if applicable): RHOSP 8