[ 
https://issues.apache.org/jira/browse/CASSANDRA-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443796#comment-13443796
 ] 

Dean Hiller edited comment on CASSANDRA-4580 at 8/29/12 3:40 PM:
-----------------------------------------------------------------

I am not sure what you mean by "gives me the options"???  The ticket was closed 
and it only seems "very related" anyways which is why I opened the new one.  
Are you saying I should try to re-open that ticket?

OR are you saying that ticket gives me the options to solve the problem myself 
in which case, I am not sure how they applied to nodetool at all....I have 
nodetool and I have cassandra.  The links to documents are too code...am I 
supposed to modify nodetool then myself?

thanks,
Dean
                
      was (Author: deanhiller):
    I am not sure what you mean by "gives me the options"???  The ticket was 
closed and it only seems "very related" anyways which is why I opened the new 
one.  Are you saying I should try to re-open that ticket?

thanks,
Dean
                  
> 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

Reply via email to