Martin Tzvetanov Grigorov created DRILL-7911:
------------------------------------------------

             Summary: Build faillure on Linux ARM64
                 Key: DRILL-7911
                 URL: https://issues.apache.org/jira/browse/DRILL-7911
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Martin Tzvetanov Grigorov


There are few problems when trying to build Drill on Linux ARM64 machine:

 

1) org.apache.drill.exec.record.vector.TestValueVector fails with 
OutOfMemoryError while trying to allocate native memory.

I've tried to debug it by adding io.netty.leakDetection.level=paranoid to 
maven-surefire-plugin's argLine but instead of reporting the leaks this 
actually worked around the issue

 

2) Contrib Storage Mongo module tests fail because flapdoodle.mongo dependency 
does not support Linux ARM64

I've created the following PRs to fix it:

[https://github.com/flapdoodle-oss/de.flapdoodle.embed.process/pull/119]{color:#000000}
 - Add support for AARCH64{color}

[https://github.com/flapdoodle-oss/de.flapdoodle.embed.process/pull/12|https://github.com/flapdoodle-oss/de.flapdoodle.embed.process/pull/120]+0+{color:#000000}
 - Add support for comparing versions{color}

[https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/pull/34|https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/pull/343]+3+{color:#000000}
 - Add support for Linux AARCH64 and newer Mongodb versions{color}

{color:#000000}3) Contrib Storage JDBC tests fail because 
{color}com.wix:wix-embedded-mysql does not support Linux ARM64

I've started adding support for ARM64 to Wix but then I realized that the 
project might be dead. Last commit to 
[https://github.com/wix/wix-embedded-mysql] is at Nov 3rd 2019. So I am not 
sure whether the improvement will be ever accepted and released.

My new approach here is to use TestContainers-MySQL instead of 
com.wix:wix-embedded-mysql. Apache Drill already uses TestContainers for 
Storage Cassandra and TestContainers Vault for java-exec module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to