[MB-4189] ns_server's concept of time is decoupled from the OS Created: 14/Aug/11 Updated: 13/May/12 Resolved: 25/Apr/12 |
|
| Status: | Resolved |
| Project: | Couchbase Server |
| Component/s: | None |
| Affects Version/s: | 1.7.1, 1.8.0, 2.0-beta |
| Fix Version/s: | 1.8.1 |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Aleksey Kondratenko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 1.8.1-release-notes | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | RHEL 5.2 64-bit | ||
| Description |
|
When testing some systems in a lab environment, I've noticed that after the VM was paused and restarted, the OS is happy with the new time of day, but the ns_server erl VM is stuck in the past. Negative effects of this are the log showing the wrong date and time and the graphs in the UI not working.
This would seem to indicate any drift fixed at the OS level isn't making it's way into erl. This is particularly bad for things that are paused/restarted, but could also affect those that just naturally drift or drift due to virtualization. Note: this hasn't actually been observed against 2.0 Alpha, but it's presumed to be there as well. Filed there so it doesn't get lost in the shift from 1.7 to 2.0. |
| Comments |
| Comment by Matt Ingenthron [ 14/Aug/11 ] |
| One workaround is to restart, but that isn't intuitive and shouldn't be necessary. |
| Comment by Matt Ingenthron [ 25/Feb/12 ] |
| Assigning to Farshid for triage. |
| Comment by Aleksey Kondratenko [ 26/Mar/12 ] |
|
use of os:timestamp is merged to 1.8.1. http://review.couchbase.org/13611
It quite possibly fixes this issue. |
| Comment by Aleksey Kondratenko [ 25/Apr/12 ] |
| This issue was indeed fixed |