[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266160#comment-15266160
]
ASF GitHub Bot commented on APEXCORE-330:
-----------------------------------------
GitHub user sandeshh opened a pull request:
https://github.com/apache/incubator-apex-core/pull/321
APEXCORE-330 : Stacktrace of the StreamingContainer exposed through REST
Getting stack trace from the containers, exposed through REST api
The return value will in JSON.
StackTrace can be accessed through the following call.
"/ws/v2/stram/physicalPlan/containers/containersID/stackTrace"
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sandeshh/incubator-apex-core APEXCORE-330
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/321.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #321
----
commit 3ff661e4bf89b8fa5733bf8a95d556138d482899
Author: sandeshh <[email protected]>
Date: 2016-04-24T14:45:12Z
APEXCORE-330 : Getting stack trace from the containers, exposed through
REST api
return value will in JSON.
StackTrace can be accessed through following call.
"/ws/v2/stram/physicalPlan/containers/<containersID>/stackTrace"
----
> Ability to obtain a thread dump from a container
> ------------------------------------------------
>
> Key: APEXCORE-330
> URL: https://issues.apache.org/jira/browse/APEXCORE-330
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Thomas Weise
> Assignee: Sandesh
>
> To analyze issues such as "stuck operator", it is useful to obtain stats from
> the running JVM. Often needed are GC stats and thread dump. In production
> environments users often don't have direct access to the machines, making it
> available through the REST API will help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
