It would be good to have index_interval configurable per keyspace.
Preferably in cassandra.yaml because i use it as tuning on nodes running
out of memory without affecting performance noticeably.
I would like to know it also - actually is should be similar, plus there
are no dependencies to sun.misc packages.
Regards,
Maciej
On Thu, Nov 10, 2011 at 1:46 PM, Benoit Perroud wrote:
> Thanks for the answer.
> I saw the move to sun.misc.
> In what sense allocateDirect is broken ?
>
> Thanks,
i have problem with large CF (about 200 billions entries per node).
While i can configure index_interval to lower memory requirements, i
still have to stick with huge bloom filters.
Ideal would be to have bloom filters configurable like in hbase.
Cassandra standard is about 1.05% false possiti
Dne 11.11.2011 5:58, Yan Chunlu napsal(a):
I think cassandra is doing great job on key-value data store, it saved
me tremendous work on maintain the data consistency and service
availability.But I think it would be great if it could support
more data structures such as key-list, currently I
Dne 10.11.2011 22:18, Dan Hendry napsal(a):
Is it possible to downgrade back to 0.8? Is there any way to convert 'h'
version SSTables to the old 'g' version? Any other data file changes to be
aware of?
try to add 0.8 node to cluster and decommission 1.0 node. maybe 0.8 will
understand streams fr
I am using Hector to do a range query for a column family that uses TimeUUIDs
as column names. However, I'm not sure how to create the "range". I figured
I'd create some UUIDs using the com.eaio.uuid library with timestamps for the
range I was interested in. When trying this, I don't get any
Hey all,
I know there are several tickets in the pipe that should make it possible
do use secondary indexes to run map reduce jobs that do not have to ingest
the entire dataset such as:
https://issues.apache.org/jira/browse/CASSANDRA-1600
I had ended up creating a sharded secondary index in user
I think cassandra is doing great job on key-value data store, it saved me
tremendous work on maintain the data consistency and service availability.
But I think it would be great if it could support more data structures
such as key-list, currently I am using key-value save the list, it seems
not
Thanks.
I'm gonna try and use QUORUM to read and/or write and see if data is
returned consistently.
On Thu, Nov 10, 2011 at 3:00 PM, Jeremiah Jordan <
jeremiah.jor...@morningstar.com> wrote:
> No, that is what I thought you wanted. I was thinking your machines in
> DC1 had extra disk space or
Is there a way to get only keys with get_indexed_slices?
Looking at the code, it's not possible, but -- is there some way anyhow?
I don't want to extract any data, just a list of matching keys.
TIA,
Maxim
Hello,
My data load comes in batches representing one day in the life of a
large computing facility.
I index the data by the day it was produced, to be able to quickly pull
data for a specific day
within the last year or two. There are 6 other indexes.
When it comes to retiring the data, I in
No, that is what I thought you wanted. I was thinking your machines in
DC1 had extra disk space or something...
(I stopped replying to the dev list)
On 11/10/2011 04:09 PM, Subrahmanya Harve wrote:
Thanks Ed and Jeremiah for that useful info.
"I am pretty sure the way you have K1 configured
Hello,
I notice that when starting a new node with same configuration(cluster name,
seeds, token etc) as an existing ring member, the new node will take over the
ownership from existing ring member. Is this expected behavior? I would like to
see Cassandra prevents new node from joining the rin
Thanks Ed and Jeremiah for that useful info.
"I am pretty sure the way you have K1 configured it will be placed across
both DC's as if you had large ring. If you want it only in DC1 you need to
say DC1:1, DC2:0."
Infact i do want K1 to be available across both DCs as if i had a large
ring. I just
I’m curious if anyone has ever seen this happen or has any idea how it
would happen. I have a 10 cluster node with 5 nodes in each data
center running .6 (we're working on the upgrade now). I had several
nodes with forgotten deletes so I failed the nodes and bootstrapped
them back into the cluste
I am pretty sure the way you have K1 configured it will be placed across
both DC's as if you had large ring. If you want it only in DC1 you need
to say DC1:1, DC2:0.
If you are writing and reading at ONE you are not guaranteed to get the
data if RF > 1. If RF = 2, and you write with ONE, you d
https://issues.apache.org/jira/browse/CASSANDRA-3482
I restarted the node and the problem has cropped up again.
Is it possible to downgrade back to 0.8? Is there any way to convert 'h'
version SSTables to the old 'g' version? Any other data file changes to be
aware of?
Dan
-Original Messa
On Thu, Nov 10, 2011 at 3:27 PM, Subrahmanya Harve <
subrahmanyaha...@gmail.com> wrote:
> I am facing an issue in 0.8.7 cluster -
>
> - I have two clusters in two DCs (rather one cross dc cluster) and two
> keyspaces. But i have only configured one keyspace to replicate data to the
> other DC and
I am facing an issue in 0.8.7 cluster -
- I have two clusters in two DCs (rather one cross dc cluster) and two
keyspaces. But i have only configured one keyspace to replicate data to the
other DC and the other keyspace to not replicate over to the other DC.
Basically this is the way i ran the keys
That would be a bug (as any assertion error would be), likely some
race condition.
Could you open a ticket?
The fact that this block the MemtablePostFlusher is unfortunately
related. Restarting the
node would fix but we need to make that more solid too.
--
Sylvain
On Thu, Nov 10, 2011 at 9:04 PM,
Just happened again, seems to be with the same column family (at least on a
flusher thread for which the last activity was flushing a memtable for that
CF).
It also looks like MemtablePostFlusher tasks blocked (and not getting
cleared) as evidenced by tpstats:
Pool NameA
All,
In 0.8.6 I got myself into a bit of a fix. First I tried to drop a column
family. This failed because I didn't have JNA installed (known and
documented). To fix this I drained the node, stopped the process, installed
JNA, and restarted C*.
Unfortunately this lead to an inconsistency in sche
Just saw this weird assertion after upgrading one of my nodes from 0.8.6 to
1.0.2 (its been running fine for a few hours now):
INFO [FlushWriter:9] 2011-11-10 13:08:58,882 Memtable.java (line 237)
Writing Memtable-Data@13889553
hi,
i've been looking at the model below from Ed Anuff's presentation at
Cassandra CF (http://www.slideshare.net/edanuff/indexing-in-cassandra).
Couple of questions:
1) Isn't there still the chance that two concurrent updates may end up
with the index containing two entries for the given us
At first, I was also thinking that one or more nodes in the cluster are broken
or not responding. But through nodetool cfstats, it looks like all the nodes
are working as expected and pings gives me the expected inter-node latencies.
Also the scores calculated by dynamic snitch in the steady sta
what about keeping a record per device and recording there that you've seen
it, and only incrementing the counters (or a different set of counters)
based on that?
On Wed, Nov 9, 2011 at 6:09 PM, Philippe wrote:
> Hello, I'd like to get some ideas on how to model counting uniques with
> cassandr
Hi,
I faced a similar issue as described there :
http://comments.gmane.org/gmane.comp.db.cassandra.user/11184.
I was running Cassandra 1.0.0 with a 3 node cluster on 3 t1.micro from
Amazon EC2.
I have no error in cassandra logs, but an OOM in /var/log/kern.log which
put one of my nodes down.
Af
Thanks for the answer.
I saw the move to sun.misc.
In what sense allocateDirect is broken ?
Thanks,
Benoit.
2011/11/9 Jonathan Ellis :
> allocateDirect is broken for this purpose, but we removed the JNA
> dependency using sun.misc.Unsafe instead:
> https://issues.apache.org/jira/browse/CASSANDR
We have a new 6-node cluster running 0.6.13 (Due to some client side issues
we need to be on 0.6x for time being) that we are injecting data into and
ran into some issues with nodes going down and then up quickly in the
ring. All nodes are effected and we have rules out the network layer.
It happ
29 matches
Mail list logo
