Hi,
I would like to share the information because you might encounter the same
situation.
- Symptom:
Impala/fe$ mvn -fae test -Dtest=PlannerTest#testEmpty -e
...
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.impala.planner.PlannerTest
*** Check failure stack trace: ***
@ 0x7f0a5a4cc6cd google::LogMessage::Fail()
@ 0x7f0a5a4cdf72 google::LogMessage::SendToLog()
@ 0x7f0a5a4cc0a7 google::LogMessage::Flush()
@ 0x7f0a5a4cf66e google::LogMessageFatal::~LogMessageFatal()
@ 0x7f0a58eebb87 impala::Frontend::Frontend()
@ 0x7f0a58db4f16 impala::ExecEnv::ExecEnv()
@ 0x7f0a58db4ad0 impala::ExecEnv::ExecEnv()
@ 0x7f0a58a8c468
Java_org_apache_impala_service_FeSupport_NativeFeTestInit
@ 0x7f0ac5017774 (unknown)
Wrote minidump to
/home/jinchulkim/Impala/logs/fe_tests/minidumps/FeSupport/8d967a71-64da-4df9-6f354b8f-c4b334dc.dmp
Wrote minidump to
/home/jinchulkim/Impala/logs/fe_tests/minidumps/FeSupport/8d967a71-64da-4df9-6f354b8f-c4b334dc.dmp
...
You can find a root cause from logs/fe_tests/FeSupport.ERROR.
F1114 14:06:11.742421 5523 frontend.cc:94] NoSuchMethodError:
setCatalogInitialized
. Impalad exiting.
- Cause:
Symbol lookup failed due to the function name inconsistency between fe and
be. You might compile only fe.
Recently, the function name was renamed by the change
<https://gerrit.cloudera.org/#/c/8202/25/be/src/testutil/in-process-servers.cc>:
setCatalogInitialized => SetCatalogIsReady
- Solution:
Incremental build for both fe and be
Best regards,
Jinchul
