|
Also I wanted to add that in the presence of the testing done under SERVER-45098, enabling this logging is a little bit less pressing, because at least we have a confirmation that the commands are apply the defaults correctly. This logging was intended to ensure that any new commands we might add won't forget to add the defaults handling.
|
|
Yes, the idea is to re-enable the logging, and then fix up any excessively verbose logging that results. The expected sources are:
- User operations that are inadvertently not sending RWC to the shards. Some of these are in the process of being fixed on
SERVER-45098. You should also be aware of SERVER-45549.
- Internal operations on mongos/shards which don't specify RWC (like the config.cache.chunks.XXX initialisation you found). These should have an appropriate RWC explicitly added to them (most likely {w:1} and {level:"local"}).
- jstests that do operations directly on shards. This might include ShardingTest setup/initialisation/shutdown. These should have an appropriate RWC explicitly added to them (almost certainly {w:1} and {level:"local"}).
|
|
kevin.pulo, kaloian.manassiev, I ran an evergreen patch with the logging enabled, and it looks like we still have a good number of internal operations that don't specify a read/write concern and trigger the logging (e.g. creating an index on a config.cache.chunks.XXX collection).
Just to confirm before I spend more time on this - was this ticket meant to include finding and fixing up these operations? Thanks!
|
|
Now that both the dependent tickets have been closed, assigning this to you Kev to evaluate whether we should re-enable that logging.
|
Generated at Thu Feb 08 05:06:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.