[SERVER-31731] Test that mongos accepts a --timeZoneInfo parameter, and can correctly execute expressions using time zones Created: 26/Oct/17 Updated: 30/Oct/23 Resolved: 16/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||
| Sprint: | Query 2017-12-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Recently we re-enabled execution of parts of the aggregation pipeline on mongos. With that change, it's possible that there will be expressions executed on mongos that need to know time zone information. It turns out that we already accept the --timeZoneInfo parameter on mongos, so this should all just work, but that was lucky. We need to add a test for this. |
| Comments |
| Comment by Githook User [ 05/Dec/17 ] |
|
Author: {'username': 'gormanb', 'email': 'bernard.gorman@gmail.com', 'name': 'Bernard Gorman'}Message: (cherry picked from commit 340bf8c5f1bef80037e336c699f7c69753a25567) |
| Comment by Githook User [ 16/Nov/17 ] |
|
Author: {'name': 'Bernard Gorman', 'username': 'gormanb', 'email': 'bernard.gorman@gmail.com'}Message: |
| Comment by David Storch [ 07/Nov/17 ] |
|
pasette, I don't think there's an easy way to make sure that all nodes have the same time zone data. I suppose we could make a mongos or mongod log a warning whenever it opens a connection to another mongod whose timezone db version mismatches the version of its own tz db. Alternatively, we could build a tool into the shell which goes around contacting all the nodes in a cluster, verifying that all nodes have the same time zone db. I filed |
| Comment by Daniel Pasette (Inactive) [ 07/Nov/17 ] |
|
charlie.swanson is there a way to detect this misconfiguration at startup (mismatched timezoneInfo)? |