[SERVER-31733] Explicit mongos default value for --timeZoneInfo parameter Created: 26/Oct/17  Updated: 06/Dec/22  Resolved: 07/Sep/18

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

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-3748 Add init scripts for mongos and confi... Closed
Related
related to SERVER-31731 Test that mongos accepts a --timeZone... Closed
related to SERVER-3748 Add init scripts for mongos and confi... Closed
is related to SERVER-29822 update linux packages to add /usr/sha... Closed
is related to SERVER-34752 Figure out a more centralised alterna... Closed
Assigned Teams:
Query
Participants:

 Description   

See SERVER-31731, we recently realized that mongos processes need to have their time zone database configurable and use the system time zone info by default.

The simplest way to achieve the needs/goals here is to make /usr/share/zoneinfo the hard coded default value for the --timeZoneInfo variable in the mongos binary on POSIX (non-Windows) systems since /usr/share/zoneinfo is the FHS/POSIX standard.

 



 Comments   
Comment by David Storch [ 07/Sep/18 ]

We do not plan to change the behavior in which mongos uses its embedded copy of the Olson timezone database in the absence of the --timeZoneInfo flag. However, once SERVER-3748 is implemented we should add a default value of /usr/share/zoneinfo for packages on platforms which have it.

Comment by Mira Carey [ 04/Sep/18 ]

Passing to query to do the work, we're happy with the approach above (adding a default path in the build system, along with the new flag).

Comment by Mira Carey [ 04/Sep/18 ]

To add a little bit of extra work, we should also add a scons flag for specifying the default path

Comment by Kaloian Manassiev [ 30/Apr/18 ]

OK, filed SERVER-34752 for the second point above and moving this ticked as it stands to the build team.

Comment by Charlie Swanson [ 30/Apr/18 ]

Yep, that's the gist of it kaloian.manassiev.

Comment by Kaloian Manassiev [ 27/Apr/18 ]

The way I read this ticket is that MongoS already supports the --timeZoneInfo configuration and configuring it as part of the installer (SERVER-3748) will solve the immediate problem.

However using the --timeZoneInfo for this purpose is generally error prone since it is still possible that different processes can be accidentally misconfigured to have different configurations. Is this correct charlie.swanson?

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