-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-10-22
The log lines will be added at log level 0 while sharded transactions are being tested and stabilized, but the lines can either be removed or their log level reduced afterwards.
–
Update: The log lines were added at log level 3, but the default level for the kTransaction log component when running a test through resmoke.py was set to 4 for both local testing and evergreen.
- is duplicated by
-
SERVER-36687 Reduce verbosity of two phase commit log lines once cross-shard transactions are stable
- Closed