[SERVER-17898] Intermittent config server check failures (uncovered by 4_upgrade_cluster.js) Created: 03/Apr/15  Updated: 18/Sep/15  Resolved: 29/Apr/15

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

Type: Bug Priority: Major - P3
Reporter: Spencer Jackson Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File 4_upgrade_cluster.html    
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Sporadic failures occur in in 4_upgrade_cluster.js. Example: https://mci.10gen.com/task/mongodb_mongo_master_linux_64_194522f2427a5bf9dcc813b224b943923790cc94_15_04_02_16_38_05_multiversion_linux_64

----
Cluster upgraded.
----
 m29002| 2015-04-03T06:07:28.894+0000 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:44390 #1 (1 connection now open)
 m30999| 2015-04-03T06:07:28.897+0000 I SHARDING [conn1] couldn't find database [config] in config db
 m30999| 2015-04-03T06:07:28.934+0000 I NETWORK  [conn1] Detected bad connection created at 1428041237141682 microSec, clearing pool for ip-10-153-130-203:29002 of 0 connections
 m30999| 2015-04-03T06:07:28.934+0000 W SHARDING [conn1] error creating initial database config information :: caused by :: database metadata write failed: { ok: 0, code: 25, errmsg: "Could not verify that config servers were active and reachable before write" }
 
	
 
2015-04-03T06:07:28.940+0000 E QUERY    Error: error: {
	"$err" : "error creating initial database config information :: caused by :: database metadata write failed: { ok: 0, code: 25, errmsg: \"Could not verify that config servers were active and reachable before write\" }",
	"code" : 25
}
    at Error (<anonymous>)
    at DBQuery.next (src/mongo/shell/query.js:265:15)
    at DBCollection.findOne (src/mongo/shell/collection.js:190:22)
    at printShardingStatus (src/mongo/shell/shardingtest.js:659:55)
    at ShardingTest.printShardingStatus (src/mongo/shell/shardingtest.js:633:5)
    at /data/mci/shell/src/jstests/multiVersion/4_upgrade_cluster.js:127:4 at src/mongo/shell/query.js:265
failed to load: /data/mci/shell/src/jstests/multiVersion/4_upgrade_cluster.js

The first build I see this on is: https://mci.10gen.com/task/mongodb_mongo_master_linux_64_14ce8911246fa6a9ae238d69fac05b169a66e6d4_15_03_31_15_34_06_multiversion_linux_64
which introduced a commit which may be related to config servers.



 Comments   
Comment by Kaloian Manassiev [ 29/Apr/15 ]

https://github.com/mongodb/mongo/commit/0a93c411a6a22c0dac8a82fed0efc4e60f62f40d

and

https://github.com/mongodb/mongo/commit/b5253c0a357dab7ba202fb8368a9f75d72501f17

Comment by Githook User [ 07/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17898 Add logging of config server check failures

This does not actually fix the bug, but helps narrow down the exact
nature of these intermittent failures.
Branch: master
https://github.com/mongodb/mongo/commit/fd0af1c636bc45f1da87a3b8402111f30b636021

Comment by Spencer Jackson [ 03/Apr/15 ]

kaloian.manassiev Could you take a look at this?

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