You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "József Márton Jung (JIRA)" <ji...@apache.org> on 2015/07/01 16:10:05 UTC

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

     [ 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.0.patch

> 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.0.patch, 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)