-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
[SPARK-9516][UI] Improvement of Thread Dump Page #7910
Conversation
Test build #39606 has finished for PR 7910 at commit
|
Test build #39641 has finished for PR 7910 at commit
|
Hi @CodingCat just a quick question from looking at the screenshot -- can you still click on one thread to expand the stack trace for just that? nothing looks like a hyperlink anymore. Again I'm not a UI expert by any means, so I'll defer to others opinions, but I wouldn't think they were clickable from the look of it. |
Test build #39721 has finished for PR 7910 at commit
|
Test build #39719 has finished for PR 7910 at commit
|
Hi, @squito , sorry for the late reply, here is the screenshot the rows are still clickable...I will add |
Test build #39799 has finished for PR 7910 at commit
|
Test build #39874 timed out for PR 7910 at commit |
Test build #39914 has finished for PR 7910 at commit
|
Test build #39944 has finished for PR 7910 at commit
|
Jenkins, retest this please |
if (!grepExp.isDefined) { | ||
true | ||
} else { | ||
thread.stackTrace.filter(_ >= ' ').matches(grepExp.get) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The filter seems strange to me. Won't stripping out newlines etc. lead to some weird matches?
Also, I think String.matches
may not be what we want -- that matches against the entire string, not against any contained substring. It would most likely mean that everyone would have to make their pattern ".*<pattern>.*"
. I think we'd rather use pattern.find()
, since that is more like "grep". Should probably also be in multiline mode, so:
val grepExp = Option(request.getParamter("grepexp")).map(Pattern.compile(_, Pattern.MULTILINE))
...
grepExp.map { grep => grep.matcher(thread.stackTrace).find()}.getOrElse(true)
Test build #40043 has finished for PR 7910 at commit
|
Thanks, @squito , I addressed your comments and uploaded the latest version of code |
Test build #255 has finished for PR 7910 at commit
|
Test build #40065 has finished for PR 7910 at commit
|
-_-||| |
Test build #40073 has finished for PR 7910 at commit
|
it seems that Jenkins is very very unstable in these days |
Test build #40112 has finished for PR 7910 at commit
|
Yeah, we've been combatting a really bad test flakiness issue over the past 48 hours :( |
I just tested this out and noticed a few problems:
Given all of this, I don't think that this PR is ready to merge in its current form. @CodingCat, if you don't anticipate having time to make these changes, would you mind closing this in the meantime to help de-clutter the PR review queue? Thanks! |
I might work on this during the week and next week, so, I prefer to keeping this open |
Test build #44152 has finished for PR 7910 at commit
|
I adjusted the patch according to Josh's suggestions, now the search is covering all columns (I thought it only cares about stacktrace column) the stacktrace is shown as a new row For the StackTrace row, the current implementation is to add a new row following the row showing Thread ID, Name and State, instead of toggling on "hidden" class the reason is that the hidden stacktrace row is a big trouble when you sort and then expand, or grep some lines..... so....Welcome to review it..... |
Test build #44175 has finished for PR 7910 at commit
|
@squito @JoshRosen just ping... |
} | ||
|
||
function onSearchStringChange() { | ||
var searchString = $('#search').val() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add a toLowerCase
here -- I tried searching for "RUNNABLE" first and it didn't find anything.
Hi @CodingCat, thanks for the reminder. This is looking great! I really like it. Just found a few minor things, and one design question about highlighting the task threads. |
@squito Thanks for the comments, just addressed the issues |
Test build #44780 has finished for PR 7910 at commit
|
function onSearchStringChange() { | ||
var searchString = $('#search').val().toLowerCase(); | ||
//remove the stacktrace | ||
collapseAllThreadStackTrace(false, false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this only takes 1 arg now (crazy that this works in js ...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, my bad
thanks for the update @CodingCat , just one tiny nit, otherwise lgtm. @JoshRosen would you like to take another look? |
Test build #44861 has finished for PR 7910 at commit
|
Hi, @JoshRosen , since 1.6 has been cut, will we push this feature in the coming version? |
retest this please |
Looks great! I'm going to merge this in master if no one objects. |
Test build #47699 has finished for PR 7910 at commit
|
Merged into master. Thanks @CodingCat and everyone who reviewed this! |
thanks @JoshRosen and @squito for reviewing it thanks for @andrewor14 for merging |
https://issues.apache.org/jira/browse/SPARK-9516
@squito @JoshRosen It's ready for the review now