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

jobs from python client not showing up in Scheduler UI #625

Closed
hokiegeek2 opened this issue Jan 23, 2023 · 3 comments
Closed

jobs from python client not showing up in Scheduler UI #625

hokiegeek2 opened this issue Jan 23, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@hokiegeek2
Copy link

Describe the bug
I am not totally sure this is a bug. The key thing is that I'm concerned that the ballista requests being submitted from my Python shell are not being distributed across my four-node cluster. I see the executors in the ui:

image

the ui is running here:

image

But I don't see any jobs:

![image](https://user-images.gu

but it appears jobs are running:

image

I also don't see anything in the logs, so not sure if I am missing a config somewhere?

@hokiegeek2 hokiegeek2 added the bug Something isn't working label Jan 23, 2023
@andygrove
Copy link
Member

You need to use BallistaContext rather than SessionContext. See #595 for more details. Basically you are running thee query in DataFusion in the Python process and not in the Ballista cluster.

@hokiegeek2
Copy link
Author

@andygrove thanks for the follow-up! On a hunch I did just that yesterday and got things working in terms of the sql API part:

image

so basically with BallistaContext the means to get a BallistaDataFrame is to execute a query against the sql API, works for me.

@hokiegeek2
Copy link
Author

hokiegeek2 commented Jan 24, 2023

@andygrove closing this issue, thanks for the clarification (and reminder about #595)

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

2 participants