[
https://issues.apache.org/jira/browse/WHIRR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094519#comment-13094519
]
Karel Vervaeke commented on WHIRR-358:
--------------------------------------
Had a look with wireshark. The value of java.rmi.server.hostname is sent to the
client. I guess it's the client which decides to abort the connection when it
doesn't match the hostname it used.
The value of java.rmi.server.hostname can be anything really. As long as your
client connects using that value for the hostname.
The default value is java.rmi.server.hostname the ip address of the server (I
guess that means whatever 'hostname -i' returns). For BYON, you get whatever is
set in /etc/hosts for your hostname. For ec2, you get the internal ip address.
Let's evaluate the possible values for java.rmi.server.hostname (with ec2 in
mind):
- internal hostname: Connecting from outside the cluster only works if you add
an entry for it in /etc/hosts: {external ip address}.
- internal ip address (==default): Connecting from outside the cluster won't
work (unless do funky things with iptables locally)
- external ip address: Connect using the external ip address
- external hostname: Connect using the external hostname.
What an annoying situation: you can't even use a http tunnel (because then the
client would compare the received hostname with 'localhost')
> Enable remote JMX access for HBase
> ----------------------------------
>
> Key: WHIRR-358
> URL: https://issues.apache.org/jira/browse/WHIRR-358
> Project: Whirr
> Issue Type: Improvement
> Components: service/hbase
> Reporter: Karel Vervaeke
> Attachments: WHIRR-358.patch
>
>
> Enabling remote jmx access should make certain management tasks easier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
