-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
To make it easy for us to quickly get a picture of what is happening in a sharded cluster when diagnosing a BF or HELP ticket, we should log every time a DDL or data movement command (such as reshardCollection) is received and completed. These logs should include the original command request object, as well as where the command originated from.
We should also log any exceptions that are thrown during the execution of those commands, as a lot of times our code silently catches exceptions making it hard to determine the root cause of an issue. Example in resharding where we catch an exception but don't log.
NOTE: these are just suggestions, feel free to not implement any logs you think are not necessary!