[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267202#comment-15267202
]
ASF GitHub Bot commented on APEXCORE-330:
-----------------------------------------
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61780111
--- Diff:
engine/src/main/java/com/datatorrent/stram/engine/StreamingContainer.java ---
@@ -690,8 +693,19 @@ public void heartbeatLoop() throws Exception
// heartbeat call and follow-up processing
//logger.debug("Sending heartbeat for {} operators.",
msg.getContainerStats().size());
msg.sentTms = System.currentTimeMillis();
+
+ msg.stackTrace = stackTrace;
+
rsp = umbilical.processHeartbeat(msg);
+
+ if ( rsp.stackTraceRequired ) {
--- End diff --
no space after ( and before )
> 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)
