cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12074) Faster check for open JMX port on startup
Date Thu, 23 Jun 2016 04:35:16 GMT

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

Jeff Jirsa commented on CASSANDRA-12074:
----------------------------------------

Concern here is that in real servers, there are other things that may show up in {{lsof -i}}
other than running cassandra daemon - outbound jmx/nodetool connections (operator running
commands against other servers, perhaps), or software bound to other interfaces will stop
cassandra from starting.


> Faster check for open JMX port on startup
> -----------------------------------------
>
>                 Key: CASSANDRA-12074
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12074
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Lifecycle
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             Fix For: 3.x
>
>
> Since CASSANDRA-7254, we check whether the JMX port is available before starting Cassandra
in order to provide a better error message when another Cassandra process is already running.
 The current check starts a Java process to do this, which takes ~3 seconds.  Instead, we
can use {{lsof}}, which is basically instantaneous.
> By my estimate, this will shave about 40 minutes off our dtest runs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message