Cluster 3.0.0 blocker list updated (action required)
has been updated today. I am absolutely glad to see that a lot of issues
are being addressed quickly.
with recent changes to corosync IPC interface, a new serious problem has
been discovered. This require effort from everybody to be addressed
properly. AFAICT the issue has always been there (or at least for a long
time) but the effect was never seen up to 2 days ago.
This is how to reproduce the problem:
# start cman
# start groupd
# ipcs (note the semaphores)
# stop groupd
# ipcs (semaphores are gone)
# start groupd
# start dlm_controld...
basically a full start/stop operation of all daemons will leak shared
semaphores in the system.
According to limits.h each system has only 128 semaphores available and
in order to clean them up manual intervention is required. Either by
meaning of reboot or ipcrm.
Our code probably doesn't clean up all the connections on shutdown
operations. The open connections (11) during runtime seem to correct.
We usually have 6 daemons running (2 connections each, one cman, one
ccs) and I know one of the daemons (cmannotifyd) doesn't hold a
connection with ccs unless required) so the number would match my check.
I personally fixed libccs this morning as it was leaking connections in
some error conditions, but apparently that was not enough.
Please make sure to check your code asap.
|All times are GMT. The time now is 12:00 PM.|
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.