[KUDU-3007] ARM/aarch64 platform support

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Assignee: RuiChen
• Reporter: liusheng
• Created: 22/Nov/19 03:14
• Updated: 12/May/21 05:03
• Resolved: 03/Sep/20 19:16

Description

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.

Issue Links

• incorporates: KUDU-3101 ASAN/TSAN with dynamic linking are incompatible on aarch64
• relates to: KUDU-3264 Release kudu-binary for linux-aarch64

Sub-Tasks

• client_symbol-test failed on aarch64 server: Resolved
• MemTracker CHECK failed on aarch64 when run cache-bench test: Resolved
• minidump-test failed on aarch64 server: Resolved
• Python tests failed on arm64: Resolved
• DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64: Resolved
• debug-util-test failed sometimes on aarch64: Segmentation fault: Resolved
• All tests failed with TSAN enabled on aarch64: Resolved
• ASAN/TSAN with dynamic linking are incompatible on aarch64: Open
• TestRpc.TestCancellationMultiThreads fail on ARM sometimes due to service queue is full: Resolved
• master_authz-itest failed on ARM server: Resolved
• Compile kudu in Release mode failed on aarch64 server: Resolved
• KUDU_LINK should be set before function APPEND_LINKER_FLAGS is called: Resolved