[SERVER-34752] Figure out a more centralised alternative to `--timeZoneInfo` in a sharded cluster Created: 30/Apr/18  Updated: 06/Dec/22  Resolved: 02/May/18

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-31733 Explicit mongos default value for --t... Closed
Assigned Teams:
Sharding
Participants:

 Description   

In a sharded cluster, the --timeZoneInfo parameter needs to be appended to each MongoDB process individually, which makes it error-prone. This ticket is to figure out a better alternative, such as a config.settings entry.



 Comments   
Comment by Andy Schwerin [ 02/May/18 ]

That approach was discarded for the added complexity inside MongoDB and also because it requires administrators to update the timezone info for the cluster instead of relying on underlying os package managers to update timezone info.

Comment by Kaloian Manassiev [ 01/May/18 ]

I filed this ticket to consider the approach of storing the time zone info inside the config database, yes. If this approach was considered and discarded for any reason, I'd be happy to close this ticket as Won't Fix.

Comment by Andy Schwerin [ 01/May/18 ]

As long as the data is stored in a file outside the control of MongoDB, I think a per-node setting will be necessary. During design of the project that introduced this parameter, we considered storing the data in the database itself, but opted not to in order to keep the project scope down.

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