You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Naveen Somasundaram (JIRA)" <ji...@apache.org> on 2015/05/07 00:54:02 UTC
[jira] [Commented] (SAMZA-670) Allow easier access to JMX port
[ https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531615#comment-14531615 ]
Naveen Somasundaram commented on SAMZA-670:
-------------------------------------------
We might be able to store this meta-information as a part of SAMZA-617 in coordinator stream, or at least worth exploring as a part of it.
> Allow easier access to JMX port
> -------------------------------
>
> Key: SAMZA-670
> URL: https://issues.apache.org/jira/browse/SAMZA-670
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.9.0
> Reporter: Naveen Somasundaram
> Fix For: 0.10.0
>
>
> The current way we expose JMX is throw logs. The process for figuring this out is (To debug a particular partition):
> 1. Figure out the Partition to container mapping throw the YARM AM or logs.
> 2. Once we know the container, access the container logs and figure out the JMX port.
> 3. Connect to the machine using the JMX port.
> We should ideally expose it through some REST service or make it available through the coordinator stream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)