[IMPALA-9577] Use `system_unsync` time for Kudu test clusters

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.4.0
• Epic Color: ghx-label-12
• Assignee: Grant Henke
• Reporter: Grant Henke
• Created: 30/Mar/20 21:27
• Updated: 06/Aug/20 23:21
• Resolved: 01/Apr/20 20:06

Description

Recently Kudu made enhancements to time source configuration and adjusted the time source for local clusters/tests to `system_unsync`. Impala should mirror that behavior in Impala test clusters given there is no need to require NTP-synchronized clock for a test where all the participating Kudu masters and tablet servers are run at the same node using the same local wallclock.

 

See the Kudu commit here for details: https://github.com/apache/kudu/commit/eb2b70d4b96be2fc2fdd6b3625acc284ac5774be

Issue Links

• is duplicated by: IMPALA-8764 Kudu data load failures due to "Clock considered unsynchronized"