You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/02 18:38:01 UTC
[jira] [Updated] (KUDU-2036) kudu-jepsen: add a scenario to run
against a set of machines having significant clock skew
[ https://issues.apache.org/jira/browse/KUDU-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-2036:
------------------------------
Labels: consistency newbie test (was: consistency newbie)
> 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
> Priority: Major
> Labels: consistency, newbie, test
>
> 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
(v8.3.4#803005)