[SERVER-4956] mongos sharding assertion in shard3.js unit test from RHEL build Created: 13/Feb/12  Updated: 15/Aug/12  Resolved: 15/Feb/12

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Greg Studer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL


Issue Links:
Duplicate
duplicates SERVER-4711 Don't use masserts when getChunkManag... Closed
Operating System: ALL
Participants:

 Description   

 m30998| Sun Feb 12 11:57:18 [conn1] Assertion: 10181:not sharded:test.foo
 m30998| 0x7a8ca6 0x7a926c 0x5cdaeb 0x5cea14 0x568da3 0x4e7e05 0x4d6e0b 0x52d5fc 0x544ec4 0x61f312 0x3088a0673d 0x30882d44bd 
 m30998| Received signal 11

From line 99 of shard3.js

http://buildbot.mongodb.org:8081/builders/Nightly%20Linux%20RHEL%2064-bit/builds/3/steps/test_5/logs/stdio
After the assertion, the unit test did not exit but just hung forever waiting for a mongos that was no longer there



 Comments   
Comment by Greg Studer [ 15/Feb/12 ]

non-sharding related, it seems like we can't print backtraces safely. Will be fixed for sharding by SERVER-4711, but still the (rare) potential segfaults during traces in other places.

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