[
https://issues.apache.org/jira/browse/SAMZA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935574#comment-15935574
]
Navina Ramesh commented on SAMZA-825:
-------------------------------------
[~jmakes] No. This has not been addressed (yet) by Standalone implementation
yet. But it seems to be related to defining the runtime environment. I will
keep an eye out to address it with SAMZA-1064. Just not yet :)
> SamzaContainer JMX port should be configurable
> ----------------------------------------------
>
> Key: SAMZA-825
> URL: https://issues.apache.org/jira/browse/SAMZA-825
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.9.1
> Reporter: Elias Levy
> Priority: Minor
>
> SamzaContainer allocates an ephemeral port for the JMX server, as it expects
> to execute in YARN, where there is no guarantee there won't be a port
> collision if a static port is selected. But that limitation does not apply
> to other potential SamzaJob implementations.
> Samza should allow the JMX port to be configured. The JmxSever class already
> support passing in a requested port number. SamzaContainer just needs to be
> modified to pass in the configured JXM port if one is found in the
> configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
