Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1252545862.1240872330354.JavaMail.jira@brutus>
Date: Mon, 27 Apr 2009 15:45:30 -0700 (PDT)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-97) race condition prevents startup
 under Xen vm
In-Reply-To: <141527131.1240508910563.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Evans commented on CASSANDRA-97:
-------------------------------------

First off, I think these patches (000[1-3]) look good. I don't see a reason for the key state collections that currently exist; IMO this is how the code should look, +1 for applying it.

However, I still believe there is a race condition here. Or rather, I am experiencing what seems to be a race condition between the select() call in SelectorManager.run and the invocation of SelectorManager.register() from the main thread.

Is no one else seeing this?


> race condition prevents startup under Xen vm
> --------------------------------------------
>
>                 Key: CASSANDRA-97
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-97
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.3
>
>         Attachments: 0001-r-m-unused-code-do-minor-cleanup.patch, 0002-r-m-unnecessary-race-prone-cancelled-read-write-ke.patch, 0003-renaming-and-final-cleanup.patch, cassandra_race_condition_in_xen.patch
>
>
> Reported by Soo Hwan Park on the mailing list.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.