Since JIRA is mostly dead right now, here is the patch to test against 0.4.
On Mon, Sep 28, 2009 at 4:30 PM, Edmond Lau edm...@ooyala.com wrote:
On Fri, Sep 25, 2009 at 8:10 PM, Jonathan Ellis jbel...@gmail.com wrote:
No, you're mixing two related concepts.
When you do a quorum read it will
Hi,
I'm not getting any responses on IRC, so figured I'd put this out on
the mailing list.
I had a 3 node cassandra cluster, replication factor 3 on
3 ec2 m1.large instances behind an haproxy. I restarted one
of the node to test out some modified sysctl's (tcp stack tuning).
As soon as I
More data, I decided to force a flush on the table I know was corrupt and
got this error
ERROR [MINOR-COMPACTION-POOL:1] 2009-09-30 18:42:01,010 DebuggableThreadPoolExec
utor.java (line 103) Error in executor
futuretaskjava.util.concurrent.ExecutionException: java.io.EOFException
at
Sweet. Jonathan, I patched in your change and no longer see a read
repair for every quorum read in the debug logs. I also reran a load
test consisting of only simple read operations, and my quorum read
throughput has doubled now that the extraneous read repairs aren't
occurring. This makes
On Wed, 2009-09-23 at 11:39 -0500, Eric Evans wrote:
A logo design contest is now underway at 99designs.com.
http://99designs.com/contests/28940
The contest brief can be found here:
http://99designs.com/contests/28940/brief. If you're worried that it's
missing something critical (or
