[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608269#comment-14608269
]
József Márton Jung commented on SAMZA-670:
------------------------------------------
Hi guys,
I'm back from my vacation... And it seems, I found the problem. In
{{JobCoordinator}} object in {{apply}} function, the
{{coordinatorSystemConsumer}} is stopped immediately in line 71. Later
{{coordinatorSystemConsumer}} is passed to {{LocalityManager}}. As the
{{coordinatorSystemConsumer}} was stopped, it did not read the newest message
which was put in the coordinator stream (the stopping happens before putting
the newest container to host mappings to the coordinator stream).
Later I will attach a patch which addresses this and exposes the JMX address to
AM UI. I just wanted to let you know that I found the root cause of my problem.
:-)
> 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
>
> Attachments: SAMZA-670.BUG_1.patch, SAMZA-670.BUG_2.patch
>
>
> 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)
