You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/08/28 20:42:09 UTC

[jira] [Resolved] (CASSANDRA-4580) nodetool can't work from remote node if firewalls are up and only port 7199 is open :(

     [ https://issues.apache.org/jira/browse/CASSANDRA-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-4580.
---------------------------------------

    Resolution: Duplicate

The penultimate comment on the ticket you link gives you the options: https://issues.apache.org/jira/browse/CASSANDRA-2967?focusedCommentId=13278943&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13278943
                
> nodetool can't work from remote node if firewalls are up and only port 7199 is open :(
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4580
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4580
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 1.1.4
>         Environment: Environment with medium security in which firewalls open specific ports(ie. mostly all production environments from small companies to large).
>            Reporter: Dean Hiller
>            Priority: Minor
>
> nodetool uses port 7199 to start with but then JMX opens dynamic ports which can't get through the firewalls.  People on the web keep pointing to this ticket which is closed
> https://issues.apache.org/jira/browse/CASSANDRA-2967
> There are definitely a large amount of users wanting this but the ticket appears close and I don't see the replacement ticket(but just close this if you know what it is).  This feature is especially needed by operations teams to run the nodetool from their control node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira