-
Type: Bug
-
Resolution: Incomplete
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.2.0
-
Component/s: Sharding
-
Environment:linux 64 bit
-
Linux
We are running mongodb v2.2.0 Linux 64 Bit, 3 shards each having 3 nodes.
One node seemed to be dead, so we restarted it. In the logs we found thousands of "waiting till out of critical section", filling up our logs very fastly and making mongodb inaccessible.
What does this error mean?
Here are the logs from the restart, if it matters:
http://pastebin.com/raw.php?i=cZeRJ7NV
This happened to other nodes as well already to another time.
Could it be related to v2.2.0 or to authentification? We're using both since a few time and we encounter this error only since then. Should we downgrade or disable authentification?
- is related to
-
SERVER-7034 timeouts for all connections in migrate critical section
- Closed
-
SERVER-7472 Replication lag can cause cluster to hang in migration critical section
- Closed
-
SERVER-7493 Possible for read starvation to cause migration to get stuck in critical section
- Closed