Hi,
I've a strange problem with my test cluster. Calling truncate on a
small ColumnFamily on idle cluster of 4 nodes returns
UnavailableException after 10s. That 10s is set in rpc_timeout_in_ms.
All nodes are up and running, here is nodetool ring:
Address DC RackStatus
Yes, the exception is for CounterColumn on Standard column family.
Created https://issues.apache.org/jira/browse/CASSANDRA-3870
Best regards/ Pagarbiai
Viktor Jevdokimov
Senior Developer
Email: viktor.jevdoki...@adform.com
Phone: +370 5 212 3063. Fax: +370 5 261 0453
J. Jasinskio
Hello
I think that in http://www.apache.org/dist/cassandra/debian repo there is
incorret version for 0.8 branch. There is 0.8.8, but latest version is
0.8.9. May be this repository is abandoned?
On Tue, Feb 7, 2012 at 2:17 AM, Patrik Modesto patrik.mode...@gmail.com wrote:
Hi,
I've a strange problem with my test cluster. Calling truncate on a
small ColumnFamily on idle cluster of 4 nodes returns
UnavailableException after 10s. That 10s is set in rpc_timeout_in_ms.
Make sure you have
FYI -- we moved Virgil to Github to make it easier for people to contribute.
https://github.com/hmsonline/virgil
Also, we created an organization profile (hmsonline) to house all of our
storm/cassandra related work.
https://github.com/hmsonline
Under that profile, we'll be releasing
It looks like what you're seeing is, stress far outpaced the ability
of compaction to keep up (which is normal for our default settings,
which prioritize maintaining request throughput over compaction), so
LCS will grab a bunch of L0 sstables, compact them together with L1
resulting in a spike of
Just to ask the stupid question, have you tried setting it really high ? Like
50 ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 7/02/2012, at 10:27 AM, Ajeet Grewal wrote:
Here are the last few lines of strace (of one of the
I do not think the mmap OOM is connected with the row size.
Add some info to the other thread if you think it's relevant.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 7/02/2012, at 10:33 AM, Ajeet Grewal wrote:
It's also a good idea
None of those jump out at me as horrible for my case. If I modelled with
Super Columns I would have less than 10,000 Super Columns with an average of
50 columns - big but no insane ?
I would still try to do it without super columns. The common belief is they are
about 10% slower, and they
On Wed, Feb 8, 2012 at 6:05 AM, aaron morton aa...@thelastpickle.comwrote:
None of those jump out at me as horrible for my case. If I modelled with
Super Columns I would have less than 10,000 Super Columns with an average
of 50 columns - big but no insane ?
I would still try to do it without
On Tue, Feb 7, 2012 at 10:45 AM, aaron morton aa...@thelastpickle.com wrote:
Just to ask the stupid question, have you tried setting it really high ?
Like 50 ?
No I have not. I moved to mmap_index_only as a stopgap solution.
Is it possible for there to be that many mmaps for about 300 db
It happens to me like this.
I have 2 node Cassandra cluster with one column space. No super columns.
Start server freshly (no commit logs, no SSTables, no saves caches,
basically nothing). Then write process starts (not much write load). See
what my log says:
2012-02-06 13:06:13,598 INFO
On Tue, Feb 7, 2012 at 18:35, Brandon Williams dri...@gmail.com wrote:
Make sure you have JNA, without it the cost of forking ln to snapshot
is expensive.
I assume JNA is enabled.
From the output.log:
INFO 10:16:20,725 JNA mlockall successful
Regards,
P.
13 matches
Mail list logo
