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/01 14:40:00 UTC
[jira] [Updated] (KUDU-1219) OS X Limitations & Known Issues
[ https://issues.apache.org/jira/browse/KUDU-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-1219:
------------------------------
Target Version/s: (was: 1.8.0)
> OS X Limitations & Known Issues
> -------------------------------
>
> Key: KUDU-1219
> URL: https://issues.apache.org/jira/browse/KUDU-1219
> Project: Kudu
> Issue Type: Task
> Environment: OS X
> Reporter: Dan Burkert
> Assignee: Dan Burkert
> Priority: Major
>
> This is a tracking ticket for known issues of running Kudu on OS X.
> # -The hybrid logical clock has error permanently set to 0us. This is a result of the {{ntp_gettime}} (or similar) API not existing on Darwin. The result is that using the hybrid logical clock on a cluster of OS X hosts is unsupported (a single-host Kudu installation is fine).-
> UPDATE: with macOS High Sierra (10.13), the hybrid clock is now supported for Kudu 1.12 and newer
> # The Kudu client library does not properly hide non-public symbols. This is a result of the {{--version-script}} option being unavailable on the OS X system linker.
> # The log block manager is not supported on OS X. This is a result of OS X not supporting sparse files and hole punching.
> # Some of the monitoring and debugging tools built in to Kudu do not work properly. In particular, stack traces (both user and kernel) may not work, and the {{/pprof}} endpoint on server pages may not work correctly.
> # ASAN tests will run and flag issues correctly, but LSAN is disabled (it is Linux only), and there are many false positives.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)