To trigger LCS you need to write to this CF and wait when new sstable flushes.
I can’t find any other way to start LCS.
Best regards / Pagarbiai
Viktor Jevdokimov
Senior Developer
Email: viktor.jevdoki...@adform.commailto:viktor.jevdoki...@adform.com
Phone: +370 5 212 3063, Fax +370 5 261 0453
What you mean 'you need write to this CF'? I've changed the schema by using
CQL3 'alter table' statments.
On Mon, May 5, 2014 at 2:28 PM, Viktor Jevdokimov
viktor.jevdoki...@adform.com wrote:
To trigger LCS you need to write to this CF and wait when new sstable
flushes. I can’t find any
If you want to trigger a conversion to LCS of the on-disk sstables, doing
nodetool compact cf should achieve what you want.
Be warned, if you have a lot of data in the CF, this could potentially take
a while depending on your compaction throttling.
Thanks,
Daniel
On Sun, May 4, 2014 at 11:54
Thanks for your prompt answer. It works great! (simple and efficient!)
Since I could not “bind” column name in prepared statement, I created 4
separate ones for each data type.
It would be nice to have “INSERT INTO data_table(key, ?) VALUES (?, ?)” ☺
Regards,
Minh
From: doanduy...@gmail.com
Hello,
After noticing that automatic tombstone removal (CASSANDRA-3442) was not
working in an append-only STCS CF with 40% of droppable tombstone ratio I
investigated why the compaction was not being triggered in the largest
SSTable with 16GB and about 70% droppable tombstone ratio.
When the
The Cassandra team is pleased to announce the release of the 2nd beta for
the future Apache Cassandra 2.1.0.
Let first stress that this is beta software and as such is *not* ready for
production use.
The goal of this release is to give a preview of what will become Cassandra
2.1 and to get wider
Hi,
I know this is a pretty common topic, but I haven't found any solution that
really satisfy me. The problem is well known: you have a table with user
information with a UUID as primary key, but you want to avoid email
duplicates when new users register.
The closest solution I've found is
On Mon, May 5, 2014 at 12:24 AM, Daniel Chia danc...@coursera.org wrote:
If you want to trigger a conversion to LCS of the on-disk sstables, doing
nodetool compact cf should achieve what you want.
For more detail and a caveat :
https://issues.apache.org/jira/browse/CASSANDRA-6092
The
On Sun, May 4, 2014 at 10:26 PM, Yatong Zhang bluefl...@gmail.com wrote:
2. Is there a way to convert these old huge sstables into small 'leveled'
ones? I tried 'sstablesplit' but always got an error with java EOF
exception.
Could you be more specific about how you are attempting to use
Running
# cat /proc/$(cat /var/run/cassandra.pid)/limits
as root or your cassandra user will tell you what limits it's actually
running with.
On Sun, May 4, 2014 at 10:12 PM, Yatong Zhang bluefl...@gmail.com wrote:
I am running 'repair' when the error occurred. And just a few days before
Hello all
I have a big col family and I see that cassandra is taking snapshots for it. I
do not have incremental enabled. What are the triggers that start the process
of taking a snapshot? Is is automatic ?
Thanks
On Mon, May 5, 2014 at 12:48 PM, Batranut Bogdan batra...@yahoo.com wrote:
I have a big col family and I see that cassandra is taking snapshots for
it. I do not have incremental enabled. What are the triggers that start the
process of taking a snapshot? Is is automatic ?
It's automatic if
Hello Robert,
Neither of those actions were taken on that cf as far as I know. In that cf we
only insert historical data. No deletes no drops / truncates.
Thanks
On Monday, May 5, 2014 10:50 PM, Robert Coli rc...@eventbrite.com wrote:
On Mon, May 5, 2014 at 12:48 PM, Batranut Bogdan
one query in our prod system under heavy load failed.
I cant tell which query it was. But I don't think we were using an invalid
consistency level since our configuration work all the time except when it
goes under heavy load.
If I can reproduce this I will pass more information.
I wonder if this
forgot to say which Cassandra version we are using.
Our prod deployment:
C* 2.0.5, DC1:3, DC2:3
On Mon, May 5, 2014 at 5:01 PM, Mohica Jasha mohica.ja...@gmail.com wrote:
one query in our prod system under heavy load failed.
I cant tell which query it was. But I don't think we were using
Most likely it is the following query:
DELETE from conditional_update_lock where resource_id = '${myresourceid}' IF
lock_id = ${myuuid};
We are using datastax 2.0.1 and the datastax threw a ReadtimeoutException
On Mon, May 5, 2014 at 5:03 PM, Mohica Jasha mohica.ja...@gmail.com wrote:
On Mon, May 5, 2014 at 2:03 PM, Mohica Jasha mohica.ja...@gmail.com wrote:
Our prod deployment:
C* 2.0.5, DC1:3, DC2:3
Not directly related to your bug report, which I would file an Apache JIRA
regarding, but...
https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/
I tried to run 'nodetool compact' (or with keyspace and cfname), seemed not
woking. The command hung there and nothing happened. But I noticed that
there was about more 3+ pending tasks when using 'nodetool
compactionsats'
On Tue, May 6, 2014 at 1:45 AM, Robert Coli rc...@eventbrite.com
18 matches
Mail list logo
