No. Cleanup will scan each sstable to remove data that is no longer
owned by that specific node. It won't compact the sstables together
however.
On Tue, Jun 19, 2012 at 11:11 PM, Raj N wrote:
> But wont that also run a major compaction which is not recommended anymore.
>
> -Raj
>
>
> On Sun, Jun
But wont that also run a major compaction which is not recommended anymore.
-Raj
On Sun, Jun 17, 2012 at 11:58 PM, aaron morton wrote:
> Assuming you have been running repair, it' can't hurt.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thel
On Mon, Jun 18, 2012 at 12:07 AM, Jason Tang wrote:
> After I enable key cache and row cache, the problem gone, I guess it because
> we have lots of data in SSTable, and it takes more time, memory and cpu to
> search the data.
The Key Cache is usually a win if added like this. The Row cache is
le
On Tue, Jun 19, 2012 at 8:55 PM, Rob Coli wrote:
> On Tue, Jun 19, 2012 at 2:55 AM, Alain RODRIGUEZ wrote:
>> Unable to create hard link from
>> /raid0/cassandra/data/cassa_teads/stats_product-hc-233-Data.db to
>> /raid0/cassandra/data/cassa_teads/snapshots/1340099026781/stats_product-hc-233-Data
On Tue, Jun 19, 2012 at 2:55 AM, Alain RODRIGUEZ wrote:
> Unable to create hard link from
> /raid0/cassandra/data/cassa_teads/stats_product-hc-233-Data.db to
> /raid0/cassandra/data/cassa_teads/snapshots/1340099026781/stats_product-hc-233-Data.db
Are you able to create this hard link via the file
Hi Jonathan, thanks for the reference. will read up on it.
Yuhan
That this will get you *worse* performance than just doing a seq scan would.
Details as to why this is, are here:
http://www.datastax.com/dev/blog/whats-new-cassandra-07-secondary-indexes
On Tue, Jun 19, 2012 at 2:48 PM, Yuhan Zhang wrote:
> To anwser my own question:
>
> There should be at leas
rows_cached is actually obsolete in 1.1. New hotness explained here:
http://www.datastax.com/dev/blog/caching-in-cassandra-1-1
On Mon, Jun 18, 2012 at 7:43 PM, Chris Burroughs
wrote:
> Check out the "rows_cached" CF attribute.
>
> On 06/18/2012 06:01 PM, Oleg Dulin wrote:
>> Dear distinguished c
On Tue, Jun 19, 2012 at 2:30 PM, Edward Capriolo wrote:
> You final two sentences are good ground rules. In our case we have
> some column families that have high churn, for example a gc_grace
> period of 4 days but the data is re-written completely every day.
> Write activity over time will event
Thanks Ed. I am on 0.8.4. So I don't have Leveled option, only SizeTiered.
I have a strange problem. I have a 6 node cluster(DC1=3, DC2=3). One of the
nodes has 105 GB data where as every other node has 60 GB in spite of each
one being a replica of the other. And I am contemplating whether I shoul
Hi Jeremy,
Glad to see the update. It would be nice if secondary index in
cassandra-unit supports DoubleType.
Yuhan
On Wed, Jun 13, 2012 at 1:32 PM, Jérémy SEVELLEC wrote:
> Hi all,
>
> cassandra-unit 1.1.0.1 is now release. cassandra-unit helps you writing
> isolated Junit Test using cassandra
To anwser my own question:
There should be at least on "equal" expression in the indexed query to
combine with a "gte".
so, I just added an trivial column that stays constant for equal
comparison. and it works.
not sure why this requirement exists.
Thank you.
Yuhan
On Tue, Jun 19, 2012 at 12:2
Hey my favorite question! It is a loaded question and it depends on
your workload. The answer has evolved over time.
In the old days <0.6.5 the only way to remove tombstones was major
compaction. This is not true in any modern version.
(Also in the old days you had to run cleanup to clear hints)
Hi all,
I'm trying to search by the secondary index of cassandra with "greater than
or equal". but reached an exception stating:
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:No indexed columns present in index clause with
operator EQ)
However, the sam
Hello
We started using cassandra at version 0.7, which allowed duplicate
names for indexes. We upgraded to version 0.8.10 a while ago and
everything has been working fine. Now I am not able to run 'update
column family' on CF with duplicate index names with other CFs.
If I update the CF with sa
DataStax recommends not to run major compactions. Edward Capriolo's
Cassandra High Performance book suggests that major compaction is a good
thing. And should be run on a regular basis. Are there any ground rules
about running major compactions? For example, if you have write-once kind
of data that
Hi again,
apt-get install libjna-java installed nothing, I was already up to date.
I made the symbolic link jna.jar to target jna-3.4.1.jar (downloaded @
the given link) instead of jna-3.2.4.jar.
I could restart with the 'JNA mlockall successful' message.
I am still unable to snapshot my data.
The code is processing the file name, without the path and appears to be
correct.
Can you show the full error (including any other output) and the directory /
files you are running the bulk load against when in windows ?
Bulk load expects
keyspace/
column_family/
sstable
Nothing has changed in the server, try the Hector user group.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 19/06/2012, at 12:02 PM, Edward Sargisson wrote:
> Hi all,
> Was there a change of behaviour in multiget_slice query in Cassandra
19 matches
Mail list logo
