cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2490) DatabaseDescriptor.defsVersion should be volatile
Date Sat, 16 Apr 2011 16:15:05 GMT

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

Jonathan Ellis updated CASSANDRA-2490:
--------------------------------------

             Reviewer: jbellis
             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 0.7.3)
                       0.7.0
        Fix Version/s: 0.7.5
             Assignee: Jeffrey Wang

committed volatile change in r1094011. thanks!

> 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

Mime
View raw message