[SERVER-16660] sharding_system_namespaces.js incorrectly assumes that mongod supports wiredTiger Created: 24/Dec/14  Updated: 15/Jan/15  Resolved: 05/Jan/15

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

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16498 d_migrate.cpp should not rely on syst... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

sharding_system_namespaces.js relies on the wiredTiger storage engine being compiled into the server. This assumption does not hold on 32-bit platforms. Specifically, the test's call to the "create" command fails with the following:

{
	"ok" : 0,
	"errmsg" : "wiredTiger is not a registered storage engine for this server",
	"code" : 72
}



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

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-16660 Add comments to sharding_system_namespaces.js
Branch: master
https://github.com/mongodb/mongo/commit/5c3e3df015d8bdb8703accb4f24ee7657fa2ba50

Comment by Githook User [ 05/Jan/15 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-16660 sharding_system_namespaces.js incorrectly assumes that mongod supports wiredTiger
Branch: master
https://github.com/mongodb/mongo/commit/780c6856b83168f17c2015fb8f8547e223eadf53

Comment by Eric Milkie [ 29/Dec/14 ]

For this problem, we've simply been disabling the tests when db.serverBuildInfo().bits = 32.

Comment by Andy Schwerin [ 24/Dec/14 ]

I wonder if there's a broader problem here, with the option validation logic. I think benety.goh and milkie did work on this, with an eye toward keeping mixed-version replica sets functional.

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