The quorum write would fail, but the data would not be rolled back. Assuming
the offline nodes recover, the data would eventually replicate.
This question belongs on the user list, though.
-Original Message-
From: Maifi Khan
Date: Thu, 19 Aug 2010 13:00:47
To:
Reply-To: dev@cassandra.
That is impossible to implement without making the write path at least as slow
as the read path. Things like this typically get layed on Cassandra by using an
external locking framework, like Zookeeper.
-Original Message-
From: Rishi Bhardwaj
Date: Sun, 20 Jun 2010 14:57:46
To:
Reply-
en Tornado and Pylons. I'm willing to run a few
test cases on both scenarios.
On Tue, Apr 13, 2010 at 2:27 PM, David Timothy Strauss
wrote:
> Please use something like Tornado. A Cassandra web GUI should not require a
> heavyweight framework and hopefully nothing other than a Cassandra
Please use something like Tornado. A Cassandra web GUI should not require a
heavyweight framework and hopefully nothing other than a Cassandra connection
to run.
-Original Message-
From: Pablo Cuadrado
Date: Fri, 9 Apr 2010 11:55:46
To:
Subject: python web framework suggestions (for C
