[SERVER-18827] repl1.js repl6.js failure Created: 29/May/15  Updated: 19/Sep/15  Resolved: 04/Jun/15

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: UT
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File repl1.log     File repl6.log    
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_duroff_replication_auth_1f4188fbdc733aa1cb08403d75f13a04d2279817_15_05_29_11_37_19

Seems to start happening after we switched WT as default storage engine. Tests timed out waiting for slave to replicate. Logs suggests that slaves are not even trying:

 m31000| 2015-05-29T08:01:19.585-0400 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:44323 #1 (1 connection now open)
 m31000| 2015-05-29T08:01:19.601-0400 I ACCESS   [conn1] Successfully authenticated as principal __system on local
 m31001| 2015-05-29T08:01:20.388-0400 I REPL     [replslave] syncing from host:127.0.0.1:31000
 m31000| 2015-05-29T08:01:20.388-0400 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:44324 #2 (2 connections now open)
 m31000| 2015-05-29T08:01:20.413-0400 I ACCESS   [conn2] Successfully authenticated as principal __system on local
 m31001| 2015-05-29T08:01:20.414-0400 I REPL     [replslave] nextOpTime May 29 08:01:19 5568550f:1 > syncedTo May 29 08:01:08 55685504:a
 m31001| time diff: 11sec
 m31001| tailing: 0
 m31001| data too stale, halting replication
 m31001| 2015-05-29T08:01:20.414-0400 I REPL     [replslave] caught SyncException
 m31001| 2015-05-29T08:01:20.414-0400 I REPL     [replslave] sleep 10 sec before next pass
:30 +0000	
 m31001| 2015-05-29T08:01:30.415-0400 I REPL     [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds
 m31000| 2015-05-29T08:01:30.415-0400 I NETWORK  [conn2] end connection 127.0.0.1:44324 (1 connection now open)
:35 +0000	
 m31001| 2015-05-29T08:01:35.415-0400 I REPL     [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds
:40 +0000	
 m31001| 2015-05-29T08:01:40.415-0400 I REPL     [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds
:45 +0000	
 m31001| 2015-05-29T08:01:45.416-0400 I REPL     [replslave] all sources dead: data too stale halted replication, sleeping for 5 seconds
:49 +0000	
assert.soon failed, msg:expected count: 1020 from : connection to 127.0.0.1:31001
Error: assert.soon failed, msg:expected count: 1020 from : connection to 127.0.0.1:31001
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.soon (src/mongo/shell/assert.js:189:13)
    at soonCount (jstests/repl/repl6.js:6:12)
    at doTest (jstests/repl/repl6.js:63:5)
    at jstests/repl/repl6.js:77:1
2015-05-29T08:01:49.760-0400 E QUERY    [thread1] Error: assert.soon failed, msg:expected count: 1020 from : connection to 127.0.0.1:31001
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.soon (src/mongo/shell/assert.js:189:13)
    at soonCount (jstests/repl/repl6.js:6:12)
    at doTest (jstests/repl/repl6.js:63:5)
    at jstests/repl/repl6.js:77:1 at src/mongo/shell/assert.js:13
failed to load: jstests/repl/repl6.js



 Comments   
Comment by Githook User [ 04/Jun/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-18827 do not force-kill master-slave master; this confuses slave when running with no journal
Branch: master
https://github.com/mongodb/mongo/commit/189f91d382337a25aac57803b49f297eb238162d

Comment by Ian Whalen (Inactive) [ 03/Jun/15 ]

ping milkie this has been failing for several days

https://evergreen.mongodb.com/task_history/mongodb-mongo-master/replication_auth?revision=db06d0a4ecdbac5b5e15981dd49c8a40ce74e255#repl6.js=fail

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