[jira] [Updated] (SAMZA-670) Allow easier access to JMX port

["József Márton Jung (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

József Márton Jung updated SAMZA-670:
-------------------------------------
    Attachment: SAMZA-670.BUG_2.patch
                SAMZA-670.BUG_1.patch

I attached 2 patches which can reproduce my problem. They are independent, and can be applied to samza master.

The container to host mapping is already passed to {{JobModel}} in {{JobCoordinator}} at the end of {{refreshJobModel}} function.

In the first patch, [^SAMZA-670.BUG_1.patch], I just added the value to AM UI to Containers tab.

In the second patch, [^SAMZA-670.BUG_2.patch], I changed to {{JobModel}} to accept {{LocalityManager}} instead of container to host mapping. Changed the method in {{JobModel}} to read the container locality form {{localityManager}}. On AM UI, in {{index.scaml}} the {{localityManager.readContainerLocality()}} gets invoked when the AM UI is loaded, so it is invoked after all containers are up and running.

In both cases the behavior is the same. When you start your samza app for the first time, assuming there is no coordinator stream yet, the coordinator stream gets created, the locality is written as expected, but on AM UI the written values is not read.
When you stop and start your app again, the first run's value is read, although the address was written to it successfully for the second time.

Hope my description is clear. :) JMX address is exposed the same way as the IP of the container, so this can be reproduced with the IP only.

> 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
>
>         Attachments: SAMZA-670.BUG_1.patch, SAMZA-670.BUG_2.patch
>
>
> 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)