cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2953) Use lazy initialization instead of class initialization in NodeId
Date Wed, 27 Jul 2011 09:00:11 GMT

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

Sylvain Lebresne updated CASSANDRA-2953:
----------------------------------------

    Attachment: 0001-Use-lazy-initialization-for-NodeId.patch

> Use lazy initialization instead of class initialization in NodeId
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-2953
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2953
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>             Fix For: 0.8.3
>
>         Attachments: 0001-Use-lazy-initialization-for-NodeId.patch
>
>
> The class initialization of NodeId triggers a read to a system table. When using the
class introduced in CASSANDRA-2911, this happens to be triggered even though this is not necessary.
This a a pain because when you use those classes, you don't have to have to set reasonable
values for the data_dir and commitlog_dir in cassandra.yaml (it is a pain to have to have
a cassandra.yaml in the classpath in the first place, but that's for another ticket).
> This ticket proposes using lazy initialization in NodeId to avoid that.

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

        

Mime
View raw message