[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524811#comment-14524811
]
Hadoop QA commented on HADOOP-10136:
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 1s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12627604/HADOOP-10136.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6334/console |
This message was automatically generated.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinayakumar B
Assignee: Vinayakumar B
Attachments: HADOOP-10136.patch, HADOOP-10136.patch,
HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524758#comment-14524758
]
Hadoop QA commented on HADOOP-10136:
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12627604/HADOOP-10136.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6324/console |
This message was automatically generated.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinayakumar B
Assignee: Vinayakumar B
Attachments: HADOOP-10136.patch, HADOOP-10136.patch,
HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892837#comment-13892837
]
Steve Loughran commented on HADOOP-10136:
-
# how would this get wired up in an application?
# what would be very nice would be for the JMXServer to extend
{{AbstractService}}, and so share the same lifecycle. Any YARN composite
service could simply add it as a child hook it into its lifecycle
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
Attachments: HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890885#comment-13890885
]
Vinay commented on HADOOP-10136:
bq. In this case we can change the default port right ?
We could change default ports to some other range. But these ports are there
from very long time. I feel changing needs to be mentioned as incompatible.
{quote}In case of JMX even if we need to configure it is not possible.
So i think better to keep this JMX server as an option.{quote}
Yes.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
Attachments: HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13881732#comment-13881732
]
nijel commented on HADOOP-10136:
bq.Unfortunately, some Hadoop daemons are using ports in the ephemeral range as
if they were fixed ports.
In this case we can change the default port right ?
In case of JMX even if we need to configure it is not possible.
So i think better to keep this JMX server as an option.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
Attachments: HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836646#comment-13836646
]
Colin Patrick McCabe commented on HADOOP-10136:
---
bq. [~stev...@iseran.com]] Is the port the JMX server coming up on in use?
Unfortunately, some Hadoop daemons are using ports in the ephemeral range as if
they were fixed ports. For example, the DataNode uses port 50070 by default,
which is in the Linux ephemeral range of 32768 to 61000. In the long run, we'd
like to migrate people away from using those ports. But in the short run,
reducing the ephemeral port usage would be a good thing.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
Attachments: HADOOP-10136.patch
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835294#comment-13835294
]
Steve Loughran commented on HADOOP-10136:
-
Is the port the JMX server coming up on in use? Surely it should be asking to
listen on port 0 and let the OS find a port 1024 where there is space.
If you are going to do a custom JMX server, I would like the option of letting
it take a port 0 for an automatic port selection -but have a way to query the
server for the port in use -which is something the standard one doesn't let you
do. Maybe also take a range of allowed ports and scan through them until a free
port can be used -which will allow ops teams to restrict the open ports on a
firewall to the same range
This is important for starting JMX in YARN containers, as you can't hard code
any port bindings without risking port collision.
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835444#comment-13835444
]
Vinay commented on HADOOP-10136:
Thanks Steve for the input.
bq. Is the port the JMX server coming up on in use?
This is possible. But my concern was not this. Default JMX will use one more
extra random port along with the port configured via
*-Dcom.sun.management.jmxremote.port*.
I will try to implement suggestions you given.
bq. have a way to query the server for the port in use
Do you mean, querying this via RPC..?
Custom JMX server to avoid random port usage by default JMX Server
--
Key: HADOOP-10136
URL: https://issues.apache.org/jira/browse/HADOOP-10136
Project: Hadoop Common
Issue Type: Improvement
Reporter: Vinay
Assignee: Vinay
If any of the java process want to enable the JMX MBean server then
following VM arguments needs to be passed.
{code}
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=14005
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false{code}
But the issue here is this will use one more random port other than 14005
while starting JMX.
This can be a problem if that random port is used for some other service.
So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
