[SERVER-20760] sharding_rs1.js failed due to too stale condition Created: 05/Oct/15  Updated: 07/Oct/15  Resolved: 05/Oct/15

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

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:
Linked BF Score: 0

 Description   

This test failed due to a node falling behind and getting stale. The test should ensure this can't happen.

test failure

failures

[js_test:sharding_rs1] 2015-10-03T14:53:47.524+0000 d20011| 2015-10-03T14:53:47.523+0000 I REPL     [ReplicationExecutor] syncing from: ip-10-232-149-173:20012
[js_test:sharding_rs1] 2015-10-03T14:53:47.524+0000 d20012| 2015-10-03T14:53:47.524+0000 I NETWORK  [initandlisten] connection accepted from 10.232.149.173:54394 #11 (8 connections now open)
[js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20012| 2015-10-03T14:53:47.524+0000 I NETWORK  [conn11] end connection 10.232.149.173:54394 (7 connections now open)
[js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20011| 2015-10-03T14:53:47.524+0000 W REPL     [rsBackgroundSync] we are too stale to use ip-10-232-149-173:20012 as a sync source
[js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20011| 2015-10-03T14:53:47.525+0000 I REPL     [ReplicationExecutor] syncing from: ip-10-232-149-173:20010



 Comments   
Comment by Githook User [ 05/Oct/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-20760 slow inserts in noPassthroughWithMongod/sharding_rs1.js to prevent nodes from falling off the back of the oplog
Branch: master
https://github.com/mongodb/mongo/commit/16441614656c0ea6b06422427e28634bb8e21823

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