martin-g edited a comment on pull request #1558: URL: https://github.com/apache/kylin/pull/1558#issuecomment-865898669
@hit-lacus I was able to run the Docker image on Linux ARM64 with these changes: https://github.com/apache/kylin/compare/master...martin-g:KYLIN-4864-add-support-for-aarch64-to-Dockerfiles?expand=1 To build and run it I use: ``` #!/usr/bin/env bash if test "$1" = "rebuild"; then echo -e "\n\n-- Building the Hadoop image ... \n\n" docker build --build-arg BASE_IMAGE=arm64v8/centos:7.9.2009 --build-arg ARCH=aarch64 --build-arg JDK_ARCH=aarch64 -t kylin-hadoop:2.7 -f Dockerfile_hadoop . echo -e "\n\n-- Building the Kylin image ... \n\n" docker build --build-arg BASE_IMAGE=kylin-hadoop:2.7 -t kylin:2.7 -f Dockerfile . fi echo -e "\n\n-- Starting Kylin ... \n\n" docker run --rm -it --name kylin \ --memory=8G \ -p 7070:7070 \ -p 8088:8088 \ -p 50070:50070 \ -p 8032:8032 \ -p 8042:8042 \ -p 16010:16010 \ --user root \ kylin:2.7 ``` I had to upgrade MySQL to 8.x because there was no aarch64 binaries at http://repo.mysql.com/yum/mysql-5.7-community/el/7/ I've also updated Kylin, Livy, JDK and Maven to their latest versions. I've tested it with the steps described at http://kylin.apache.org/docs/tutorial/kylin_sample.html but it got stuck at 90.91% . The logs just repeat the following again and again: ``` ==> logs/kylin.log <== 2021-06-22 11:12:42,935 INFO [BadQueryDetector] service.BadQueryDetector:148 : Detect bad query. 2021-06-22 11:12:45,832 INFO [FetcherRunner 1102308739-43] threadpool.DefaultFetcherRunner:117 : Job Fetcher: 1 should running, 1 actual running, 0 stopped, 0 ready, 0 already succeed, 0 error, 0 discarded, 0 others ==> logs/streaming_coordinator.log <== 2021-06-22 11:12:45,832 INFO [FetcherRunner 1102308739-43] threadpool.DefaultFetcherRunner:117 : Job Fetcher: 1 should running, 1 actual running, 0 stopped, 0 ready, 0 already succeed, 0 error, 0 discarded, 0 others ==> logs/kylin.log <== 2021-06-22 11:13:15,832 INFO [FetcherRunner 1102308739-43] threadpool.DefaultFetcherRunner:117 : Job Fetcher: 1 should running, 1 actual running, 0 stopped, 0 ready, 0 already succeed, 0 error, 0 discarded, 0 others ==> logs/streaming_coordinator.log <== 2021-06-22 11:13:15,832 INFO [FetcherRunner 1102308739-43] threadpool.DefaultFetcherRunner:117 : Job Fetcher: 1 should running, 1 actual running, 0 stopped, 0 ready, 0 already succeed, 0 error, 0 discarded, 0 others ==> logs/kylin.log <== ``` I did not face any problems related to RocksDB ! Only the unit tests fail with 5.9.2 and pass with 5.18.4! Now I am trying to test with 3.1.3-SNAPSHOT but the build fails at `kylin-it` module due to : ``` java.lang.IllegalArgumentException: java.net.UnknownHostException: sandbox.hortonworks.com at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:378) at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310) at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:678) at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:619) at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2653) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:368) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:170) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:355) at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295) at org.apache.kylin.common.KylinConfigBase.getHdfsWorkingDirectory(KylinConfigBase.java:284) at org.apache.kylin.dict.ITGlobalDictionaryBuilderTest$SharedBuilderThread.run(ITGlobalDictionaryBuilderTest.java:133) ``` I cannot find what build step is supposed to build the `**-bin.tar.gz` for https://github.com/apache/kylin/blob/efedf07043c704cbdfa04ac3af3d73cec866cb76/docker/Dockerfile_dev#L25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
