mirror of
https://github.com/apache/impala.git
synced 2025-12-19 18:12:08 -05:00
48b38810e8
Custom cluster tests like TestKuduHMSIntegration restart the Kudu service with custom startup flags. On Redhat8 ARM64, these tests have been failing due to Kudu being unresponsive after this restart. Debugging showed that Kudu was stuck early in startup. This only reproduced via the custom cluster tests and never via regular minicluster startup. When custom cluster tests restart Kudu, the script to restart Kudu inherits environment variables from the test runner. It turns out that the HEAPCHECK environment variable (even when empty) causes Kudu to get stuck during startup on Redhat8 ARM64 after the recent toolchain update. As a short-term fix, this unsets HEAPCHECK when restarting the Kudu service for these tests. There will need to be further investigation / cleanup beyond this. Testing: - Ran the Kudu custom cluster tests on Redhat8 ARM64 and on Ubuntu 20 x86_64 Change-Id: I51513e194d9e605df199672231b412fae40343af Reviewed-on: http://gerrit.cloudera.org:8080/23467 Reviewed-by: Riza Suminto <riza.suminto@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>