[SERVER-31851] Issue a warning when Olson time zone db versions do not match Created: 07/Nov/17 Updated: 06/Dec/22 Resolved: 29/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
Each node in the cluster can separately use the timeZoneInfo configuration parameter to point to time zone information. Users could easily misconfigure their cluster to have different versions of the Olson time zone db on different nodes. This is not a fatal misconfiguration, but it could cause time calculations to be incorrect. We should attempt to proactively detect this misconfiguration and issue a warning. |
| Comments |
| Comment by David Storch [ 07/Nov/17 ] |
|
milkie, I'm aware that this clearly needs to be thought through and specified in more detail. Implementing this could be significant work. I don't think we even surface the time zone db version information right now, plus we need to do the work of figuring out when and how to detect a version mismatch. I doubt it makes sense on startup, but perhaps it makes sense on connection setup? But then how do we avoid spamming the logs with warnings whenever two nodes with different Olson versions communicate? From derick:
|
| Comment by Eric Milkie [ 07/Nov/17 ] |
|
Where would the warning go? (Into the system log of every node?) |