There is no way to set a max size on an sstable file. If your Cassandra
data directory is not your / filesystem you could reformat it as ext4 (or
at least ext3 with better options)
On Fri, Dec 2, 2011 at 8:35 AM, Alexandru Dan Sicoe <
sicoe.alexan...@googlemail.com> wrote:
> Ok, so my problem per
Jonathan Ellis gmail.com> writes:
>
> I think you're confusing "temporary space used during a compaction
> operation" with "total i/o done by compaction."
>
> Leveled compaction *will* do more i/o than size-tiered, because it's
> enforcing tighter guarantees on how compacted the data is.
>
I just tested with stress tool, it is reproducible and timeout happens always.
./stress -d -e QUORUM -l 3 -o RANGE_SLICE
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
0,0,0,NaN,10
0,0,0,NaN,20
0,0,0,NaN,30
0,0,0
The Cassandra team is pleased to announce the release of Apache Cassandra
version 0.8.8.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassand
Would be glad to be of any help; it's kind of annoying.
* Nothing unusual on any nodes that I can see
* Cannot reproduce on a single-node cluster; I see it only on our prod cluster
which was running 0.6.13 until this point (cluster conf is attached to the JIRA
issue mentioned below).
Let me kn
The first step towards determining how serious it is, is showing us
how to reproduce it or otherwise narrowing down what could be causing
it, because timeouts can be caused by a lot of non-bug scenarios.
Does it occur for every query or just some? Is there anything unusual
on the coordinator or re
Hello,
Is this bug serious enough for 1.0.6 to come out shortly or not?
Thank you,
PBR
On Thu, Dec 1, 2011 at 6:05 PM, Zhong Li wrote:
> After upgrade to 1.0.5 RangeSlice got timeout. Ticket
> https://issues.apache.org/jira/browse/CASSANDRA-3551
>
> On Dec 1, 2011, at 5:43 PM, Evgeniy Ryabits
In our case, we need to execute "unsafeAssassinateEndpoint" from
https://issues.apache.org/jira/browse/CASSANDRA-3337.How do we go about
applying the patch attached to CASSANDRA-3337? We always used the binary
distribution; never had to compile cassandra; so we are not sure of the
proper way t
I think you're confusing "temporary space used during a compaction
operation" with "total i/o done by compaction."
Leveled compaction *will* do more i/o than size-tiered, because it's
enforcing tighter guarantees on how compacted the data is.
On Fri, Dec 2, 2011 at 1:01 AM, liangfeng wrote:
> He
Ok, so my problem persisted. On the node that is filling up the harddisk, I
have a 230 GB disk. Right after I restart the node I it deletes tmp files
and reaches 55GB of data on disk. Then it start to quickly fill up the disk
- I see gigs added fast - it's not real data because other nodes don't ha
Dne 1.12.2011 23:30, Bill napsal(a):
> Our largest dataset has 1200 billion rows.
Radim, out of curiosity, how many nodes is that running across?
32
I've missed the vote email, thanks!
Patrik
On Fri, Dec 2, 2011 at 11:03, Sylvain Lebresne wrote:
> The release of 0.8.8 is under vote as of now. So it will be released
> as soon as it has been tested and voted on, which should hopefully
> happen soon (it could be today, it could be early next we
The release of 0.8.8 is under vote as of now. So it will be released
as soon as it has been tested and voted on, which should hopefully
happen soon (it could be today, it could be early next week).
--
Sylvain
On Fri, Dec 2, 2011 at 10:49 AM, Patrik Modesto
wrote:
> Hi,
>
> It's been almost 2 mon
Hi,
It's been almost 2 months since the release of the 0.8.7 version and
there are quite some changes in 0.8.8, so I'd like to ask is there a
release date?
Regards,
Patrik
14 matches
Mail list logo