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

Getting negetive wallclock time in the sparklens UI #44

Closed
shahidki31 opened this issue Aug 23, 2019 · 3 comments
Closed

Getting negetive wallclock time in the sparklens UI #44

shahidki31 opened this issue Aug 23, 2019 · 3 comments

Comments

@shahidki31
Copy link

shahidki31 commented Aug 23, 2019

Hi,
Thank you for the amazing tool for the performance monitoring of spark jobs. I was trying out some long running spark query using sparklens. However I was getting some strange output in the sparklens UI regarding the job time, like wallclock time etc.
image
image
Could you please help me to resolve this issue?

@iamrohit
Copy link
Contributor

@shahidki31 Thanks for raising this. We will take a look at get back to you.
I know of couple of reasons why this happens. The first one is missing job end events in the event log file. When the job end time is not known, we try to estimate it. If these are bad estimates, we can run into negative job time issues. The second reason is multiple jobs running in parallel. Sparklens computes driver time by subtracting "time spent in jobs" from the total wall clock time. With parallel jobs, it becomes a bit tricky to find out "time spent in jobs". We had made some changes to deal with this problem, but perhaps running is something new here. We will check and get back to you.

@mayurdb
Copy link
Collaborator

mayurdb commented Aug 27, 2019

@shahidki31 Parallel jobs were not getting considered at one place in the code, which is why you were getting a negative driver wallclock time. I have fixed it and updated the jar. Please check now, it should work correctly. Thanks for reporting 👍

@shahidki31
Copy link
Author

Thanks @iamrohit @mayurdb for the replies. Yes, I am running jobs in parallel (TPCDS queries basically). Seems, console output is giving the correct results, only UI has the problem. Will check again. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants