[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580803#comment-14580803
]
Yi Pan (Data Infrastructure) commented on SAMZA-670:
----------------------------------------------------
Hi, [~jjung], your understanding of the starting sequence is correct.
[~naveenatceg] has mentioned in the first comment in this JIRA that we should
probably expose this via the coordinator stream (SAMZA-611). I.e. when each
container starts, it should log a message containing the current JMX port
numbers to the coordinator stream. The JobCoordinator, which is instantiated in
the Application Master, will listen to the coordinator stream and get these
information.
> 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
> Assignee: József Márton Jung
> 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 through 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)
