[SERVER-6209] mongos 'corrupted double-linked list' during shard rebalancing Created: 26/Jun/12  Updated: 16/Nov/21  Resolved: 11/Mar/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Reid Morrison Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Linux 5 64 bit


Attachments: Text File mongos.log    
Operating System: Linux
Participants:

 Description   

This is the second occurrence of the mongos process crashing while it is trying to rebalance the shards. It also appears that the crash is occurring after the stop time in the sharding window.

Mongo sharding window configuration:
mongos> db.settings.findOne(

{ _id : "balancer" }

)
{
"_id" : "balancer",
"activeWindow" :

{ "start" : "01:00", "stop" : "13:00" }

}

Attached is the log extract for the period leading up to the crash of mongos.

Output for: uname -a
Linux dalwork3.clarity.net 2.6.18-238.21.1.el5 #1 SMP Tue Aug 9 11:57:24 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

Output for: mongos --version
Tue Jun 26 14:24:26 mongos db version v2.0.6, pdfile version 4.5 starting (--help for usage)
Tue Jun 26 14:24:26 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
Tue Jun 26 14:24:26 build info: Linux ip-10-110-9-236 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41

Our Mongo Servers can be viewed in MMS under "Clarity Services"

Thank you for such a great product!

Regards,
Reid Morrison
Software Architect
Clarity Services



 Comments   
Comment by Reid Morrison [ 11/Mar/13 ]

Ian, good point, I completely forgot about this ticket. I can confirm that it was completely resolved in V2.2.2. Thank you for resolving it for us.

Comment by Ian Whalen (Inactive) [ 11/Mar/13 ]

Reid, because of the amount of time transpired since you filed this ticket I'm resolving it as incomplete. My apologies for us not responding sooner. Please do add a comment if you're still able to recreate (especially on a 2.2.x or 2.4 release candidate) and I'll reopen this.

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