[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590263#comment-14590263
]
Yan Fang commented on SAMZA-670:
--------------------------------
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.
Here are my thoughts:
1. the jmx address is sent in the Container level, not AM level. That means,
the jmx address is sent after the AM is fully started. So do you call the
state.jobCoordinator.jobModel.getLocalityManager after all containers start?
2. 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.
Let me know if it works. Thank you.
> 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)
