[
https://issues.apache.org/jira/browse/CASSANDRA-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-12074:
------------------------------------
Description:
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.
was:
Since CASSANDRA-7245, 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.
> 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)
