[
https://issues.apache.org/jira/browse/KUDU-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-2036:
--------------------------------
Description:
It would be nice to introduce a run-time scenario for kudu-jepsen to run tablet
servers on machines with significant clock skew (say, 30 seconds for the
beginning).
>From the high-level, it seems feasible to update local clock on every machine
>and then start the ntpd daemon which uses machine's hardware clock as a driver
>(so, no external NTP server to sync with).
While doing that, it's worth clarifying how to do the same trick if using
Docker containers instead of VMs -- it might not work under Docker.
was:
It would be nice to introduce a run-time scenario for kudu-jepsen to run tablet
servers on machines with significant clock skew.
>From the high-level, it seems feasible to update local clock on every machine
>and then start the ntpd daemon which uses machine's hardware clock as a driver
>(so, no external NTP server to sync with).
While doing that, it's worth clarifying how to do the same trick if using
Docker containers instead of VMs -- it might not work under Docker.
> kudu-jepsen: add a scenario to run against a set of machines having
> significant clock skew
> ------------------------------------------------------------------------------------------
>
> Key: KUDU-2036
> URL: https://issues.apache.org/jira/browse/KUDU-2036
> Project: Kudu
> Issue Type: Task
> Reporter: Alexey Serbin
> Labels: consistency, newbie
>
> It would be nice to introduce a run-time scenario for kudu-jepsen to run
> tablet servers on machines with significant clock skew (say, 30 seconds for
> the beginning).
> From the high-level, it seems feasible to update local clock on every machine
> and then start the ntpd daemon which uses machine's hardware clock as a
> driver (so, no external NTP server to sync with).
> While doing that, it's worth clarifying how to do the same trick if using
> Docker containers instead of VMs -- it might not work under Docker.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
