[SERVER-16811] Only register wiredTiger factory once Created: 12/Jan/15  Updated: 02/Oct/15  Resolved: 15/Jan/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.0.0-rc6

Type: Improvement Priority: Minor - P4
Reporter: James Wahlin Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16685 serverBuildInfo should include storag... Closed
is related to SERVER-17244 Unknown storage engine: wiredtiger Closed
Backwards Compatibility: Minor Change
Participants:

 Description   

The wiredTiger storage engine is registered twice with the global environment. This is to accommodate passing both "wiredtiger" and "wiredTiger" as engine name at the mongod command line.

Under SERVER-16266 we added "wiredTiger" to make the naming consistent and left "wiredtiger" as we had released an RC. I would argue however that we should remove "wiredtiger" now as there will be a larger impact if removed in the future.

Outside of simplifying the command line, removal of "wiredtiger" comes into play when iterating over the list of storage engine factories via the StorageFactoriesIterator. The Factory interface provides engine identification via the getCanonicalName() method. This method will return the same name, "wiredTiger", for both registered WiredTiger instances. De-duping is then required if looking for a list of registered storage engines.



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

Author:

{u'username': u'ramonfm', u'name': u'Ramon Fernandez', u'email': u'ramon.fernandez@mongodb.com'}

Message: SERVER-16811 Register wiredTiger factory once.

This change removes support for the use of the "wiredtiger" name (note
lowercase t) for the Wired Tiger storage engine. From now on only the
"wiredTiger" name is supported.
Branch: master
https://github.com/mongodb/mongo/commit/85fcc6daad585196ce69f1868f8283e0d92388be

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