Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with running Delight on a standalone Spark cluster #36

Open
lior-wnwd opened this issue Jul 4, 2023 · 0 comments
Open

Problem with running Delight on a standalone Spark cluster #36

lior-wnwd opened this issue Jul 4, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@lior-wnwd
Copy link

lior-wnwd commented Jul 4, 2023

Hi,

I found Datamechanics Delight tool online, and started using it locally on my Mac. It seems amazing!
However, while trying to run it from our cluster, it failed and wrote that it "Could not process the Spark Events log. Metrics are unavailable."

We're running Spark 2.4.7 on AWS in standalone mode. The history server is enabled, as well as spark.eventLog.enabled property.
The job does manage to send heartbeats to Delight, and there are no errors in the log (all logs are INFO).
At the end of the log, once the job is finished successfully, I have a message:

[spark-listener-group-shared] INFO  co.datamechanics.delight.DelightStreamingConnector- Application will be available in a few minutes on Delight at this url: https://delight.datamechanics.co/apps/some-id

When opening the link, from the overview screen, I am able to see the Spark UI of the history server, but the overview of Delight is empty (see image below).

image

This is the spark-submit command I'm using (there are some additional configs on the machine itself):

/root/spark/bin/spark-submit /
--master spark://my-master.com --name app-name /
--class com.example.MyApp --total-executor-cores 24 /
--conf spark.eventLog.dir=file:/tmp 
--conf spark.history.fs.logDirectory=file:/tmp /
--repositories https://oss.sonatype.org/content/repositories/snapshots /
--packages co.datamechanics:delight_2.11:latest-SNAPSHOT /
--conf spark.delight.accessToken.secret=my-token  /
--conf spark.extraListeners=co.datamechanics.delight.DelightListener /
 my-app.jar

How can I solve this issue, in order to use Delight from our cluster?

Thanks,
Lior

@lior-wnwd lior-wnwd added the bug Something isn't working label Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant