CASSANDRA-8285
https://issues.apache.org/jira/browse/CASSANDRA-8285 Aleksey Yeschenko
Move
all hints related tasks to hints private executor Pierre's reproducer
represents something we weren't doing, but that users are. Is that now
being tested?
That particular issue will not happen again. That
Hey Benedict,
My replies in line
According to some recordings from DataStax there is a plan to support in
Cassandra multiple kinds of store - document, graph so it won’t get easier
with the time but rather harder - ask yourself do you really want to mess
all these things together?
Well,
On Tue, Mar 17, 2015 at 4:06 PM, Jonathan Ellis jbel...@gmail.com wrote:
I’m optimistic that as we improve our process this way, our even releases
will become increasingly stable. If so, we can skip sub-minor releases
(3.2.x) entirely, and focus on keeping the release train moving. In the
Often we face errors on Cassandra start regarding unfinished compactions
particularly when cassandra was abrupty shut down . Problem gets resolved when
we delete /var/lib/cassandra/data/system/compactions_in_progress folder. Does
deletion of the folder has any impact on integrity of data or
Recently we faced an issue where every repair operation caused addition of
hundreds of sstables (CASSANDRA-9146). In order to bring situation under
control and make sure reads are not impacted, we were left with no option but
to run major compaction to ensure that thousands of tiny sstables are
I havent got much response regarding this on user list..so posting it on dev
list too..
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:Anuj Wadehra anujw_2...@yahoo.co.in
Date:Tue, 14 Apr, 2015 at 7:05 am
Subject:Drawbacks of Major Compaction now that Automatic Tombstone Compaction
every second minor release was fixing maven artifacts OR every second
release was broken due the maven artifacts
Well, it's also possible just one release had 116 build artefact problems?
Obviously that's the absurd extreme end, but the reason I was asking if you
had any idea, since you'd
According to some recordings from DataStax there is a plan to support in
Cassandra multiple kinds of store - document, graph so it won’t get easier
with the time but rather harder - ask yourself do you really want to mess
all these things together?
Well, these certainly won't live in the
On Fri, Apr 10, 2015 at 8:34 PM, Ariel Weisberg ariel.weisb...@datastax.com
wrote:
Hi Marcus,
CASSANDRA-8211 https://issues.apache.org/jira/browse/CASSANDRA-8211
Overlapping
sstables in L1+
So the question I would ask is would the workload that reproduces this
specific bug be interesting
Hi Benedict,
This only requires unit testing or dtests to be run this way. However for
the kitchen sink tests this is just another dimension in the configuration
state space, which IMO should be addressed as a whole methodically. Perhaps
we should file a central JIRA, or the Google doc you
10 matches
Mail list logo
