[SERVER-18785] Store mongos timezone in config.mongos pings Created: 02/Jun/15  Updated: 06/Dec/22  Resolved: 15/Nov/21

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-4963 Time zone ambiguity in balancer activ... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

In the absence of a fix for SERVER-4963, it would help with diagnosing balancer-out-of-window events if the pings stored in config.mongos included the mongos's local timezone next to the ping time. eg.

{ "_id" : "mongos1:27017", "ping" : ISODate("2015-06-01T07:09:12.708Z"), tz: "-0700", "up" : 986411, "waiting" : true, "mongoVersion" : "3.0.3" }



 Comments   
Comment by Kaloian Manassiev [ 12/Feb/19 ]

kevin.pulo, we are putting this on the back-burner for now. Let us know if you think it is important to do from support perspective.

Comment by Andy Schwerin [ 20/Jul/15 ]

An implementation should include a multi-version test that confirms that it is backwards compatible with versions that don't store the timezone.

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