Re: Creating two instances in code

+ 1 to all suggestions from Bjorn, but I'm sorry I can't devote time to it. FWIW there's an old issue I once reported which tells part of the story. At the time it was resolved as Won't Fix, but as Gary mentioned, time change https://issues.apache.org/jira/browse/CASSANDRA-741 (Refactor for testabi

Re: Creating two instances in code

Gary Dusbabek writes: > > I looked into doing this when I was first learning the code and had an > experience simliar to yours. At the time there wasn't much interest > in seeing it through to fruition, but maybe times have changed. any lack of interest in solving these problems just means that

Re: Creating two instances in code

On Fri, Aug 13, 2010 at 11:28, Bjorn Borud wrote: > Ryan Daum writes: > >> This is very discouraging; I've looked several times at this code and could >> not believe my eyes in regard to the wanton use of global statics. In >> addition to smelling bad, it makes it difficult to embed Cassandra. Is

Re: Creating two instances in code

Ryan Daum writes: > This is very discouraging; I've looked several times at this code and could > not believe my eyes in regard to the wanton use of global statics. In > addition to smelling bad, it makes it difficult to embed Cassandra. Is there > no will at all to fix this? I experienced all m

Re: Creating two instances in code

This is very discouraging; I've looked several times at this code and could not believe my eyes in regard to the wanton use of global statics. In addition to smelling bad, it makes it difficult to embed Cassandra. Is there no will at all to fix this? Ryan On Fri, Jul 30, 2010 at 4:50 PM, wrote:

Re: Creating two instances in code

>From what I found, I'd say it lies somewhere between pointless and impossible. :-\ Alexander > Several more. Without much thinking there are Gossiper, > MessageService and StorageService. All are singletons that > encapsulate much of the functionality of Cassandra. We've been very > consisten

Re: Creating two instances in code

Several more. Without much thinking there are Gossiper, MessageService and StorageService. All are singletons that encapsulate much of the functionality of Cassandra. We've been very consistent about naming the singleton instances "instance," so if you search for "public static final [\w]+ insta

Re: Creating two instances in code

Thank you for your answer. I know I should change the code. My question was mainly on how to change the code to do this. For example, will making DatabaseDescriptor a non-static class be enough? I could have Cassandra build a DatabaseDescriptor instance at startup, which could be a class variable

Re: Creating two instances in code

The resource file (cassandra.yaml) is statically defined that is brought in from the classpath. To do what you desire will require changing the code. You could modify DatabaseDescriptor.getStorageConfigPath() to accept some kind of variable to indicate the instance and then load a different file.

Creating two instances in code

Hello, I'd like to make some changes to cassandra so that when starting up a node in a cluster, another node starts in another cluster. That requires that the two nodes have different configurations, but DatabaseDescriptor (where I think all the config reading is done) seems to load everything sta