Rabbitmq crashed with no more index entries in atom_tab
Bug #1534519 reported by
Fabrizio Soppelsa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Alexey Lebedeff | ||
6.1.x |
Won't Fix
|
Medium
|
MOS Maintenance | ||
7.0.x |
Won't Fix
|
Medium
|
MOS Maintenance | ||
8.0.x |
Won't Fix
|
Medium
|
MOS Maintenance | ||
Mitaka |
Fix Released
|
Medium
|
Alexey Lebedeff |
Bug Description
On one of the controller nodes, RabbitMQ crashed with the following error:
no more index entries in atom_tab (max=1048576).
Environment details:
MOS 6.1 with MU4
RabbitMQ 3.3.5 not under pacemaker, but run standalone
=erl_crash_dump:0.3
Fri Dec 25 23:22:20 2015
Slogan: no more index entries in atom_tab (max=1048576)
System version: Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:30] [kernel-poll:true]
Compiled: Tue Aug 19 16:45:11 2014
Further details (as sysctl values) to be added when available.
Workaround was to restart RabbitMQ.
Changed in fuel: | |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
milestone: | none → 6.1-updates |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-mos |
no longer affects: | fuel/future |
tags: | added: wontfix-low |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This condition could be hit in following conditions:
1) Increased limit for kernel.pid_max - some value greater than ~1 million
2) Big amount of nodes in cluster - but it will require at least 32 nodes with default linux pid_max value
Proper fix will be included in rabbitmq 3.6.1 ( https:/ /github. com/rabbitmq/ rabbitmq- server/ pull/552 ). It could be backported to any version of rabbitmq starting from 3.5.0.
For earlier versions (as for 3.3.5 in the initial report) we'll need to add some shell magic instead - if it is deemed to be important enough.