[ 
https://issues.apache.org/jira/browse/IMPALA-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951905#comment-17951905
 ] 

ASF subversion and git services commented on IMPALA-13866:
----------------------------------------------------------

Commit fae38aa77d152f0dc8e16e81464ef2d6e701f106 in impala's branch 
refs/heads/master from skatiyal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=fae38aa77 ]

IMPALA-13866: Add the timestamp in /jvm-threadz page

Enhanced /jvm-threadz WebUI page to include a timestamp for every jstack 
capture,
It will help comparing multiple jstacks captured via WebUI.

Change-Id: Ic0cb95028e175328c94aa2ad9df1f841efcde948
Reviewed-on: http://gerrit.cloudera.org:8080/22877
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Add the timestamp in /jvm-threadz page
> --------------------------------------
>
>                 Key: IMPALA-13866
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13866
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Quanlong Huang
>            Assignee: Saurabh Katiyal
>            Priority: Major
>              Labels: new-bie, ramp-up
>
> In the WebUI, /jvm-threadz page shows the stacktrace of JVM threads similar 
> to jstack output. This is useful for env where jstack is missing. Comparing 
> to the jstack output, the timestamp of taking these stacktraces is missing in 
> the page. We should add it to help comparing stacktraces of different 
> snapshots.
> Here is where we handler the request:
> https://github.com/apache/impala/blob/356b7e5ddf7868968fb76ca55a8046d0291388fd/be/src/util/thread.cc#L427
> and the web template:
> https://github.com/apache/impala/blob/356b7e5ddf7868968fb76ca55a8046d0291388fd/www/jvm-threadz.tmpl#L26



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to