[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591739#comment-14591739
]
József Márton Jung commented on SAMZA-670:
------------------------------------------
{quote}
Ok. Cool. From what you describe, it's not about "flush" or anything else. The
jmx address is definitely sent to the Kafka. I think the only thing you need to
verify is that, you want to see the latest jmx somewhere in the log.
{quote}
Yes, it is visible, and it is written to Kafka stream as expected. The problem
is with the reading of the written JMX address (and container to host mapping
generally).
{qoute}
So do you call the state.jobCoordinator.jobModel.getLocalityManager after all
containers start?
{quote}
Yes. {{state.jobCoordinator.jobModel.getLocalityManager}} got called when you
load the AM UI. If you reload the page it is called on reload, too. At that
time the container is up and running.
{quote}
I believe you add the jmx address in the SamzaContainer.scala, right? Try to
call localityManager.readContainerLocality() after sending (keep the flush in
the writeContainerToHostMapping). Log or system.out the result. You should be
able to see the latest jmx in container's log.
{quote}
Yes, I'm adding the JMX address in {{SamzaContainer.scala}} in
{{startLocalityManager}} function at the exact same place where the container's
IP address is added. At this place {{localityManager.readContainerLocality()}}
reads the expected values. I can see the most recent address.
> 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)
