[
https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077188#comment-17077188
]
liusheng commented on KUDU-3007:
--------------------------------
Hi [~adar],
About the Kudu aarch/ARM support, we have done some works these days, besides
the sub-tasks of this issue related with ARM support, the most modification are
in the patch: [https://gerrit.cloudera.org/#/c/14964/,] As disscussed
previously, we proposed to add an ARM CI for Kudu community. Now we have spent
some time tried to make Kudu building and running test cases sucessfully on
ARM, according to the Jenkins CI of Kudu, there are 6 testing types: LINT,
IWYU, DEBUG, RELEASE, ASAN, TSAN. we have also tried these testing types. We
have built the primary OpenLab CI job in our experimental OpenLab environment,
the latest testing results after applying the 14964 patch are here:
[http://80.158.17.129/logs/8/8/aa7f8a35bafe7b0e6bd1e6793470c8b4d8aaa14a/check/kudu-build-test-aarch64-in-docker/e6e529b/test_results/]
For the LINT and IWYU testing type, it is easy to fix the issues occurs on ARM,
but it is strange that there are several failures of IWYU doesn't look like
relate with ARM and didn't occur in Jenkin CI. details can be find in "iwyu"
directory of above testing results link.
For DEBUG and RELEASE testing types, we have made many changes in the patch and
the building process are OK now, and >99% test cases can pass now, but current
there still have random 1~3 test case failures every time, we are still
debuging but hard to find explict root cause. more details can be find in the
"debug" and "release" directories of above testing results link.
For ASAN and TSAN testing types, we have struggled a while, but it looks like
there are some problems about TSAN/ASAN support on ARM, we have asked in
[https://github.com/google/sanitizers/issues/1208] and will continue to dig
more.
Summarily, the DEBUG and RELEASE testing type now are almost fully passed, the
small issues in LINT and IWYU we have fixed. the TSAN and ASAN look like have
some problems about ARM supporting. So. do you think if we can built and in
tegrate the ARM CI running DEBUG, RELEASE, LINT and IWYU testing job to Kudu
community now ? we will also try to find the root cause about TSAN and ASAN
failures.
> ARM/aarch64 platform support
> ----------------------------
>
> Key: KUDU-3007
> URL: https://issues.apache.org/jira/browse/KUDU-3007
> Project: Kudu
> Issue Type: Improvement
> Reporter: liusheng
> Priority: Critical
>
> As an import alternative of x86 architecture, Aarch64(ARM) architecture is
> currently the dominate architecture in small devices like phone, IOT devices,
> security cameras, drones etc. And also, there are more and more hadware or
> cloud vendor start to provide ARM resources, such as AWS, Huawei, Packet,
> Ampere. etc. Usually, the ARM servers are low cost and more cheap than x86
> servers, and now more and more ARM servers have comparative performance with
> x86 servers, and even more efficient in some areas.
> We want to propose to add an Aarch64 CI for KUDU to promote the support for
> KUDU on Aarch64 platforms. We are willing to provide machines to the current
> CI system and manpower to mananging the CI and fxing problems that occours.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
