Fuel for OpenStack

  1. Bug #1463433
  2. Comment #12

Comment 12 for bug 1463433

Revision history for this message
Bogdan Dobrelya (bogdando) wrote : Re: [shaker] test failing due to multiple "Timed out waiting for reply to ID" events logged by Oslo.messaging after rabbitmq recovered from partitioning and kept running with some connections got blocked because virt memory got exhausted by publishers

Some questions remain unanswered:
1) Why the swapped virtual memory at node-1 increased from 13.5 to 19G by this night, if many connections was blocked? Were there more and more connections and messages incoming form anaware OpenStack services or we just can see a memory leak issue in beam process? How to debug this?
2) Why blocked connections persist instead of being closed?