[DOCS-365] balancer window specified in local time Created: 25/Jul/12 Updated: 31/Aug/12 Resolved: 16/Aug/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Ed Costello |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 24 weeks, 5 days ago |
| Description |
|
http://www.mongodb.org/display/DOCS/Sharding+Administration#ShardingAdministration-Balancerwindow Make it clear that the balancer window is specified in server-local time, not GMT/UTC. |
| Comments |
| Comment by Ed Costello [ 31/Aug/12 ] |
|
Closing, edits reflecting the wiki deployed to http://docs.mongodb.org/manual/administration/sharding |
| Comment by auto [ 15/Aug/12 ] |
|
Author: {u'date': u'2012-08-15T14:33:35-07:00', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: minor: |
| Comment by auto [ 15/Aug/12 ] |
|
Author: {u'date': u'2012-08-15T14:20:25-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: |
| Comment by Ed Costello [ 15/Aug/12 ] |
|
Initial cut of changes in this pull request: https://github.com/mongodb/docs/pull/124 |
| Comment by Ed Costello [ 15/Aug/12 ] |
|
Additionally: is there a specific recommendation to run all mongos in the same timezone, regardless of geography? |
| Comment by Ed Costello [ 15/Aug/12 ] |
|
Does mongos inherit the timezone from the startup environment (eg: the TZ environment variable)? Is it configurable anywhere else? |
| Comment by Scott Hernandez (Inactive) [ 25/Jul/12 ] |
|
Updated a bit but can use some cleanup. Made Limitation section: http://www.mongodb.org/display/DOCS/Sharding+Administration#ShardingAdministration-Balancerwindow |
| Comment by Scott Hernandez (Inactive) [ 25/Jul/12 ] |
|
Also, note that each mongos evaluates this so if they have different timezones this can be problematic. Imagine mongos servers in US/ASIA running with a local timezone, not in UTC – gets bad... |