[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580192#comment-14580192
]
József Márton Jung commented on SAMZA-670:
------------------------------------------
Hi guys,
I'm having difficulties to expose the JMX address of the containers.
As far as I understood, Samza Application Master starts the container by
executing the {{bin/run-container.sh}} command. This command then executes the
{{bin/run-class.sh}} with the passed class and java options.
It means that container will run in a new JVM not in the JVM where Samza
Application Master is running. Therefore sharing the JMX address with AM Web
servlet through objects is not possible.
Am I getting it right?
What is your suggestion for resolving this?
> 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)
