[SERVER-6137] When disk is full on any secondary, the whole set of secondaries freezes until the full node is stopped Created: 20/Jun/12  Updated: 15/Aug/12  Resolved: 22/Jun/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Luciano Issoe Assignee: Kristina Chodorow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04 LTS


Issue Links:
Depends
depends on SERVER-5208 Replica set periodic reevaluation of ... Closed
Operating System: Linux
Participants:

 Description   

When one of the secondaries stops can´t create a new database file, the others secondaries freezes, and are unable to catch up the primary until one stops the failed node.



 Comments   
Comment by Kristina Chodorow (Inactive) [ 22/Jun/12 ]

Great, feel free to watch/vote for SERVER-5208.

Comment by Luciano Issoe [ 22/Jun/12 ]

I´m sure that was the case! I was just not sure if it was supposed to happen, so I reported it.

Thanks!

Comment by Kristina Chodorow (Inactive) [ 22/Jun/12 ]

Sounds like the frozen secondaries were syncing from the disk-full secondary. Because the disk-full secondary could no longer replicate data, everyone fell behind. If you have rs.status() output from the various members from when they were frozen, we can verify this. Assuming this is correct, it would be fixed by SERVER-5208.

Generated at Thu Feb 08 03:10:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.