[
https://issues.apache.org/jira/browse/SAMZA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935566#comment-15935566
]
Jake Maes commented on SAMZA-825:
---------------------------------
[~navina], [~boryas], will this be resolved as part of standalone?
It was last requested in August:
http://mail-archives.apache.org/mod_mbox/samza-dev/201608.mbox/%3CCAHUevGH1s1get5EEfCAm_tYW3ddc5iCd3YNEbynvBz%2Bp-qdqWw%40mail.gmail.com%3E
> 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)
