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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/01/26 00:29:13 UTC

[jira] [Resolved] (CASSANDRA-3898) do not leak internal mutable TokenMetadata state

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

Jonathan Ellis resolved CASSANDRA-3898.
---------------------------------------

    Resolution: Won't Fix
    
> do not leak internal mutable TokenMetadata state
> ------------------------------------------------
>
>                 Key: CASSANDRA-3898
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3898
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Minor
>
> It would be great if TokenMetadata never ever leaked internal mutable state, avoiding once and for all further concurrency issues here. Persistent collections (CASSANDRA-3856) should be a good candidate here to accomplish this without additional complexity, as long as read performance is reasonably close to their non-persistent counterparts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira