[CASSANDRA-2953] Use lazy initialization instead of class initialization in NodeId

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 0.8.3
• Assignee: Sylvain Lebresne Assign to me
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 27/Jul/11 08:59
• Updated: 16/Apr/19 09:32
• Resolved: 27/Jul/11 15:21

Description

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.