Re: Forming a cluster of embedded Cassandra instances

Thanks for sharing your experience! I also found a similar solution in TitanDB[1], but that also seem to be intended for development use. I think the consensus here seems to be that one should not be embedding Cassandra into another JVM. > For production, we have to support single node clusters (n

Re: Forming a cluster of embedded Cassandra instances

But again, you could also simply spawn a process running Cassandra as-is in its intended form which would eliminate the potential for conflict between the app heap and Casandra's JVM heap. -- Jack Krupansky On Mon, Feb 15, 2016 at 12:56 AM, Jan Kesten wrote: > Hi, > > the embedded cassandra to

Re: Forming a cluster of embedded Cassandra instances

Hi, the embedded cassandra to speedup entering the project may will work for developers, we used it for junit. But a simple clone and maven build - I guess it will end in a single node cassandra cluster. Remember cassandra is a distributed database, one will need more than one node to get perfo

Re: Forming a cluster of embedded Cassandra instances

The motivation was to make it easy for someone to get up and running quickly with the project. Clone the git repo, run the maven build, and then you are all set. It definitely does lower the learning curve for someone just getting started with a project and who is not really thinking about Cassandr

Re: Forming a cluster of embedded Cassandra instances

What motivated the use of an embedded instance for development - as opposed to simply spawning a process for Cassandra? -- Jack Krupansky On Sun, Feb 14, 2016 at 2:05 PM, John Sanda wrote: > The project I work on day to day uses an embedded instance of Cassandra, > but it is intended for prim

Re: Forming a cluster of embedded Cassandra instances

The project I work on day to day uses an embedded instance of Cassandra, but it is intended for primarily for development. We embed Cassandra in a WildFly (i.e., JBoss) server. It is packaged and deployed as an EAR. I personally do not do this. I use and recommend ccm

Re: Forming a cluster of embedded Cassandra instances

+1 to what jack said. Don't mess with embedded till you understand the basics of the db. You're not making your system any less complex, I'd say you're most likely going to shoot yourself in the foot. On Sat, Feb 13, 2016 at 2:22 PM Jack Krupansky wrote: > HA requires an odd number of replicas -

Re: Forming a cluster of embedded Cassandra instances

HA requires an odd number of replicas - 3, 5, 7 - so that split-brain can be avoided. Two nodes would not support HA. You need to be able to reach a quorum, which is defined as n/2+1 where n is the number of replicas. IOW, you cannot update the data if a quorum cannot be reached. The data on any gi