Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 8 Dec 2015 17:06:11 +0000 (UTC)
From: "Joshua McKenzie (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12838588.1434575094000.303120.1449594371748@Atlassian.JIRA>
In-Reply-To: <JIRA.12838588.1434575094000@Atlassian.JIRA>
References: <JIRA.12838588.1434575094000@Atlassian.JIRA>
 <JIRA.12838588.1434575094765@arcas>
Subject: [jira] [Updated] (CASSANDRA-9615) Speed up Windows launch scripts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Joshua McKenzie updated CASSANDRA-9615:
---------------------------------------
    Component/s: Packaging

> Speed up Windows launch scripts
> -------------------------------
>
>                 Key: CASSANDRA-9615
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9615
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>            Priority: Minor
>              Labels: Windows
>             Fix For: 2.2.1
>
>
> Currently the async callback to start C* on Windows from within ccm is taking upwards of 1.5 to 2 seconds per node due to a variety of somewhat expensive process launches we're doing in there (java version check, async port open checking). Contrast this with a crisp 0-1 ms on linux...
> Some of that stuff can be cleaned up and sped up which should help both speed up our testing environment and iron out an error that pops up on the port check w/IPv6 (note: node still starts, just complains).


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