Support Questions

Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Druid could not be started from Ambari

Explorer

Hello all,

We have Ambari 2.5.1.0 and Druid 0.10.1 in HDP 2.6.3.

When we try start from Ambari only superset starts. Rest of the services won't start. Log says,

"INFO: An exception was caught and reported. Message: java.io.IOException: No FileSystem for scheme: wasb java.lang.RuntimeException: java.io.IOException: No FileSystem for scheme: wasb"

But if we start from the command line manually it starts. Is this the problem with Ambari ? Should we upgrade Ambari ?

Any help on this would be very much appreciated.

Thanks,

Cibi

1 REPLY 1

Super Mentor

@Cibi Chakaravarthi

Usually , this error indicates that the Azure jars (like hadoop-azure*.jar , azure-storage*.jar ..etc) are not included in the "SPARK_CLASSPATH".

As you mentined that it is happenign only when you are trying to start it via Ambari UI, So can you please check if by any chance you have set any environment variable (global variable) to affect the SPARK_CLASSPATH ?

.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.