As seen in HELP-73786 it is possible for the opWriteConcernCounters to embed a NUL byte value into the ServerStatus response (specifically into a string field which can cause a node to go down. We need to find the root cause of this issue and prevent it from happening.
max.hirschhorn@mongodb.com identified that wTagCounts is a likely source of this error since it could relate to custom write concern tags provided by users
This issue has been seen back to 7.0
- related to
-
SERVER-106312 Add null byte validation to WriteConcernW
-
- Closed
-