[SERVER-8781] sharding_migrateBigObject.js failing on RHEL Created: 28/Feb/13  Updated: 14/Jul/17  Resolved: 28/Feb/13

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

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Greg Studer
Resolution: Won't Fix Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

http://buildlogs.mongodb.org/Nightly%20Linux%20RHEL%2064-bit/builds/424/test/slow%20nightly/sharding_migrateBigObject.js

Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:7)
    at doassert (src/mongo/shell/assert.js:6:1)
    at Function.assert.soon (src/mongo/shell/assert.js:110:48)
    at /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/jstests/slowNightly/sharding_migrateBigObject.js:43:8
Thu Feb 28 08:32:30.614 JavaScript execution failed: assert.soon failed: function (){ 
        res = mongos.getDB( "config" ).chunks.group( { cond : { ns : "test.stuff" } , 
                                                       key : { shard : 1 }  , 
                                                       reduce : function( doc , out ){ out.nChunks++; } , 
                                                       initial : { nChunks : 0 } } );
        
        printjson( res );
        return res.length > 1 && Math.abs( res[0].nChunks - res[1].nChunks ) <= 3;
    }, msg:never migrated at src/mongo/shell/assert.js:L7
failed to load: /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/jstests/slowNightly/sharding_migrateBigObject.js



 Comments   
Comment by auto [ 28/Feb/13 ]

Author:

{u'date': u'2013-02-28T18:53:57Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-8781 buildbot sharding_migrateBigObject better error message when balancing fails due to I/O problems
Branch: master
https://github.com/mongodb/mongo/commit/7471ba53b04f21157c4d6066e6e2769d856a3d3c

Comment by Greg Studer [ 28/Feb/13 ]

Issue here is A) that the config server and shard are running on the same (local)host, and B) that the disk on that host was so slow that it took 13s to flush the migrated data and 7s to flush the config data. This test is somewhat performance-related and requires a minimum level of I/O performance to work.

Since the I/O interruption is very unpredictable and there isn't a good way to separate the config server and shard in the current test framework, creating a better error message for this failure.

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