[
https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531744#comment-14531744
]
Yan Fang commented on SAMZA-670:
--------------------------------
Agreed on this. It's a little struggling now. I think those links can be put in
the [AM
UI|http://samza.apache.org/learn/documentation/0.9/yarn/application-master.html]
which we already have.
In addition, (just the thoughts in my mind)
1) I was thinking of putting the checkpoint offset (since it's already in the
coordinator stream) to the dashboard as well. (Maybe the latest offset too).
This is useful because it gives you the very first impression of how the
processing works (fast enough or not) before you even connect to any other
metric/monitoring tools. If you think it's worthing doing, we can create a
ticket for this.
2) the UI's doc is hidden somehow, we want to take it out to a separating
category, such as monitoring.
> 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
> 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)
