[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586652#comment-14586652
]
Yan Fang commented on SAMZA-670:
--------------------------------
Hi [~jjung], Thanks for the try.
{quote}
Then the second time, when it should read the new address, it reads the older
address instead, and so on.
{quote}
I also realize the messages order in the log is different from what the console
shows. This is related to SAMZA-699. I committed that patch. So it should fix
this. Can you rebase and try?
{quote}
The latest address which is in the coordinator stream is not there. And I have
no idea why.
{quote}
I think this behavior is expected. Because when the
CoordinatorStreamSystemConsumer bootstraps, the latest jmx has not been
published to the broker by that time. That means, publishing the latest jmx
always happens after the bootstrap in the log. If you want to verify this, get
the coordinatorStream bootstrap again after publishing the latest jmx (just for
testing purpose). You should be able to see the latest jmx.
> 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)
