Do you have this jar in your CLASSPATH when starting the services? hadoop-azure-datalake-2.6.0-cdh5.14.0-SNAPSHOT.jar
If not, you may have to run "mvn dependency:copy-dependencies" from the fe dir, and then source bin/set-classpath.sh On Wed, Nov 29, 2017 at 5:50 PM, Vincent Tran <[email protected]> wrote: > Today I rebased an old change <https://gerrit.cloudera.org/#/c/7009/> to > resume working on it again. Build went fine but the daemons are failing to > start with: > > > 1. > > I1129 20:26:57.751333 5739 jni-util.cc:211] java.lang.Error: > Unresolved compilation problem: > > 2. > > AdlFileSystem cannot be resolved to a type > > 3. > 4. > > at org.apache.impala.service.JniFrontend.checkFileSystem( > JniFrontend.java:724) > > 5. > > at org.apache.impala.service.JniFrontend.checkConfiguration( > JniFrontend.java:636) > > 6. > > I1129 20:26:57.801338 5739 status.cc:125] Error: Unresolved > compilation problem: > > 7. > > AdlFileSystem cannot be resolved to a type > > 8. > 9. > > @ 0x164327b impala::Status::Status() > > 10. > > @ 0x1a4d976 impala::JniUtil::GetJniExceptionMsg() > > 11. > > @ 0x18f02d2 impala::Frontend::ValidateSettings() > > 12. > > @ 0x190bae5 impala::ImpalaServer::ImpalaServer() > > 13. > > @ 0x19080cd ImpaladMain() > > 14. > > @ 0x15e5e70 main > > 15. > > @ 0x7fcca6244830 __libc_start_main > > 16. > > @ 0x15e5ce9 _start > > 17. > > E1129 20:26:57.801354 5739 impala-server.cc:284] Error: Unresolved > compilation problem: > > 18. > > AdlFileSystem cannot be resolved to a type > > 19. > 20. > > E1129 20:26:57.801373 5739 impala-server.cc:287] Aborting Impala > Server startup due to improper configuration. Impalad exiting. > > > > The change does not involve AdlFileSystem and I've had private builds with > this change in the past starting successfully. > I've rebuilt twice. Has anyone encountered this or has any lead? >
