-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
ALL
Assuming this is real since I've seen it on two different builders:
http://mci.10gen.com/ui/task/mongodb_mongo_master_windows_64_debug_f6a77ea2f6ae26f8408055f395ccc000db6008a8_13_07_29_20_40_06_replication_windows_64
http://mci.10gen.com/ui/task/mongodb_mongo_master_windows_64_f6a77ea2f6ae26f8408055f395ccc000db6008a8_13_07_29_20_40_06_replication_windows_64
m31001| repl: tailing: 0 m31001| repl: data too stale, halting replication m31001| Tue Jul 30 01:18:04.895 [replslave] caught SyncException m31001| Tue Jul 30 01:18:04.895 [replslave] repl: sleep 10 sec before next pass m31001| Tue Jul 30 01:18:14.895 [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds m31000| Tue Jul 30 01:18:14.895 [conn2] end connection 127.0.0.1:59362 (1 connection now open) m31000| Tue Jul 30 01:18:14.896 [conn2] thread conn2 stack usage was 26824 bytes, which is the most so far m31001| Tue Jul 30 01:18:19.895 [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds m31001| Tue Jul 30 01:18:24.895 [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds m31001| Tue Jul 30 01:18:29.895 [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds assert.soon failed: function () { var normalDocs = slave.getDB( normalDB ).data.find().count(); var specialDocs = slave.getDB( specialDB ).data.find().count(); return normalDocs == 0 && specialDocs == 1; }, msg:Failed to only sync to [a-z]+ Error: Printing Stack Trace at printStackTrace (src/mongo/shell/utils.js:37:15) at doassert (src/mongo/shell/assert.js:6:5) at Function.assert.soon (src/mongo/shell/assert.js:174:60) at D:\data\mci\single_test\git@github.commongodb\mongo.git\master\replication\jstests\repl\repl_sync_only_db_with_special_chars.js:12:8 at D:\data\mci\single_test\git@github.commongodb\mongo.git\master\replication\jstests\repl\repl_sync_only_db_with_special_chars.js:19:3 Tue Jul 30 01:18:33.256 assert.soon failed: function () { var normalDocs = slave.getDB( normalDB ).data.find().count(); var specialDocs = slave.getDB( specialDB ).data.find().count(); return normalDocs == 0 && specialDocs == 1; }, msg:Failed to only sync to [a-z]+ at src/mongo/shell/assert.js:7 failed to load: D:\data\mci\single_test\git@github.commongodb\mongo.git\master\replication\jstests\repl\repl_sync_only_db_with_special_chars.js
The first failing commit was, however, a comment-only change, so this could be a flaky test or machine issue.
- is related to
-
SERVER-10344 Race condition when starting up new master/slave cluster. Was: repl4.js failing on Linux 64-bit Weekly Slow Tests
- Closed