You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/04/16 18:38:05 UTC

[jira] [Commented] (CASSANDRA-2490) DatabaseDescriptor.defsVersion should be volatile

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

Hudson commented on CASSANDRA-2490:
-----------------------------------

Integrated in Cassandra-0.7 #435 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/435/])
    make DD.defsVersion volatile
patch by Jeffrey Wang; reviewed by jbellis for CASSANDRA-2490


> DatabaseDescriptor.defsVersion should be volatile
> -------------------------------------------------
>
>                 Key: CASSANDRA-2490
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2490
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Jeffrey Wang
>            Assignee: Jeffrey Wang
>            Priority: Minor
>             Fix For: 0.7.5
>
>
> (Probably affects other versions, but I am on 0.7.3).
> DatabaseDescriptor.defsVersion should be protected by volatile since it is written to and read by multiple threads from unsynchronized methods. This can manifest itself in schema agreement never occurring due to a node broadcasting the wrong schema version.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira