[SERVER-5156] better monitoring of config data refreshing Created: 01/Mar/12  Updated: 10/Dec/14  Resolved: 06/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4672 add monitoring of version reload stat... Closed
Operating System: ALL
Participants:

 Description   

It's difficult to see the impact of particular mongos/mongod algorithms for refreshing config data because there's very few (if any) statistics gathered on how often we need to do this. We should at least record the number of times config data is accessed, could also record buckets like :

  • local query/update/insert stale version (doesn't actually hit config server, usually)
  • remote query stale version
  • remote update/query stale writeback
  • migrate / split
  • repeated stale version resulting in force

Could also be a good test case for labeled log levels of whatever implementation - logging every interaction with the config server would be extremely useful, but only when debugging particular issues and would otherwise be very verbose.


Generated at Thu Feb 08 03:08:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.