[SERVER-16746] Leap Second impact Created: 06/Jan/15 Updated: 07/Jan/15 Resolved: 07/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sumeet Sharma | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Can you elaborate on the impact expected on a sharded cluster due to a Leap Second. We use ntpd for syncronization of time between machines. |
| Comments |
| Comment by Ramon Fernandez Marina [ 07/Jan/15 ] |
|
Thanks for your report sumeet.x.sharma.-nd@disney.com. The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, |