Info

There are places where DBConfig::_lock mutex is held while reading/modifying these members and there are methods that just reference them without holding the mutex.

Top User Comments

xgen-internal-githook commented on Fri, 19 Aug 2016 06:06:53 +0000: Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'} Message: SERVER-22175 DBConfig needs to lock mutex whenever accessing _primaryId or _shardingEnabled Branch: master https://github.com/mongodb/mongo/commit/0b165e8a2b756c5c5fa8746df049f7b3253ec294 renctan commented on Wed, 13 Jan 2016 21:09:17 +0000: Yes. There are some setter methods for it, and also whenever _load is called. spencer commented on Wed, 13 Jan 2016 20:58:02 +0000: renctan - can those values change once a DBConfig is constructed? If so then we probably need to be locking everywhere.

Steps to Reproduce