Sorry, probably I didn't catch your setup fully.
Would you like to use shared data folder for both nodes, assuming you never run two Cassandra process simultaneously? Well, I guess it's possible. Running two Cassandra instances on the same data folder together won't work, so prevent this situation, may be with some sort of file locking. >multinode Cassandra for Node B is not free Sure, but besides higher reliability you also get increase in read queries speed (with consistency ONE). Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting, Zero production time ---- On Tue, 22 Nov 2016 14:28:33 -0500Lou DeGenaro <lou.degen...@gmail.com> wrote ---- Yes, change rpc_address to node B. Immutability aside, if Node A Cassandra and Node B Cassandra are using the same directory on the same shared filesystem, let's call it /cassandra/state/database, would that not be a problem? Or said differently, does not Node A need its own writable place /cassandra/state/database/nodeA and likewise /cassandra/state/database/nodeB for Node B's writable place? Multinode Cassandra may not always be available due to resource constraints. Presumably multinode Cassandra for Node B is not free: it takes up network, cpu, and replicated disk space, no? Lou. On 2016-11-22 11:10 (-0500), Vladimir Yudovin <v...@winguzone.com> wrote: > Hi Lou,> > > > > do you mean you set rpc_address (or broadcast_rpc_address) to Node_B_IP on second machine?> > > > > &gt;there would be potential database corruption, no?> > > Well, so SSTables are immutable, it can lead to unpredictable behavior, I guess. I don't believe anybody tested such setup before.> > > > > &gt;Is there any guidance on single instance failover?> > > I never saw one, the main Casandra idea that you build multinode cluster.> >%
