cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9054) Let DatabaseDescriptor not implicitly startup services
Date Thu, 18 Aug 2016 23:58:20 GMT

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

Robert Stupp commented on CASSANDRA-9054:
-----------------------------------------

[~jjordan] applied the changes. Wanna take a look?
||trunk|[branch|https://github.com/apache/cassandra/compare/trunk...snazy:9054-followup-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-9054-followup-trunk-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-9054-followup-trunk-dtest/lastSuccessfulBuild/]


> Let DatabaseDescriptor not implicitly startup services
> ------------------------------------------------------
>
>                 Key: CASSANDRA-9054
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9054
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremiah Jordan
>            Assignee: Robert Stupp
>             Fix For: 3.10
>
>
> Right now to get at Config stuff you go through DatabaseDescriptor.  But when you instantiate
DatabaseDescriptor it actually opens system tables and such, which triggers commit log replays,
and other things if the right flags aren't set ahead of time.  This makes getting at config
stuff from tools annoying, as you have to be very careful about instantiation orders.
> It would be nice if we could break DatabaseDescriptor up into multiple classes, so that
getting at config stuff from tools wasn't such a pain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message