Will do the same!
Thanks,
Or.
On Tue, Aug 12, 2014 at 6:47 PM, Clint Kelly clint.ke...@gmail.com wrote:
Hi Or,
For now I removed the test that was failing like this from our suite
and made a note to revisit it in a couple of weeks. Unfortunately I
still don't know what the issue is. I'll
in composite column
or both.
For example,
With row key = 1, I have data
1 | 20140813, user1 | value1
1 | 20140813, user2 | value2
1 | 20140814, user1 | value3
1 | 20140814, user2 | value4
(1: rowkey, 20140813, user1: composite column, value1 : the value of
column)
So the number of columns of row
add an additional integer column to the partition key (making it a
composite partition key if it isn't already). When inserting, randomly
pick a value between, say, 0 and 10 to use for this column -- Due to the
low cardinality of bucket (only 10), there is no guarantee that the
partitions would
Graham,
Thanks for the reply. As I stated in mine first mail increasing the heap size
fixes the problem but I'm more interesting in figuring out the right properties
for commitlog and memtable sizes when we need to keep the heap smaller.
Also I think we are not seeing CASSANDRA-7546 as I apply
,UTF8Type)'
and default_validation_class = UTF8Type;
Number of columns will depend on only first column name in composite
column or both.
For example,
With row key = 1, I have data
1 | 20140813, user1 | value1
1 | 20140813, user2 | value2
1 | 20140814, user1 | value3
1 | 20140814
I am using jdbc driver (cassandra-jdbc-1.2.5.jar) for cassandra, i wrote
sample java code, did compiled it successfully but unable to run. any help
appreciated.
Any other jar i am missing here ?
[root@CSL-simulation conf]# /usr/java/jdk1.7.0_60/bin/java -cp
Hello,
I have used C* 2.1.0-rc1, 2.1.0-rc2, 2.1.0-rc3 and I currently use
2.1.0-rc5. Since 2.1.0-rc2, it appears that the secondary indexes are not
always working. Just after the INSERT of a row, the index seems to be
there. But after a while (I do not know when or why), SELECT statements
based
Hello,
We currently are at C* 1.2 and are using the SnappyCompressor for all our
CFs. Total data size is at 24 TB, and its a 12 node cluster. Avg node size
is 2 TB.
We are adding nodes currently and it seems like compression is falling
behind. I judge that by the fact that the new node which has
Confusingly, it appears to be the presence of an index on int_val that is
causing this timeout. If I drop that index (leaving only the index on
foo_name) the query works just fine.
On Tue, Aug 12, 2014 at 10:25 PM, Ian Rose ianr...@fullstory.com wrote:
Hi -
I am currently running a single
Hello Fabrice.
A quick hint, try to create your secondary index WITHOUT the IF NOT
EXISTS clause to see if you still have the bug.
Another idea is to activate query tracing on client side to see what's
going on underneath.
On Wed, Aug 13, 2014 at 2:48 PM, Fabrice Larcher
Hello Ian
Secondary index performs poorly with inequalities (, ≤, , ≥). Indeed
inequalities forces the server to scan all the cluster to find the
requested range, which is clearly not optimal. That's the reason why you
need to add ALLOW FILTERING for the query to be accepted.
ALLOW FILTERING
OK, now supposing Cassandra is run in a VM that crashes and I restore it from
a snapshot done some time ago. Data is stored redundantly (replication
factor 3) and I'm using consistency level QUORUM for reads and writes. That
means no data should be lost as the latest data will at least be stored
Agreed, but... in this case the table has ONE row, so what exactly could be
causing this timeout? I mean, it can’t be the row count, right?
-- Jack Krupansky
From: DuyHai Doan
Sent: Wednesday, August 13, 2014 9:01 AM
To: user@cassandra.apache.org
Subject: Re: range query times out (on 1 node,
That is the issue. Thanks..!!
The new node runs Spark work load so I changed seed ip to the newly added
node’s IP. Same with listen address.
Only common link between Cassandra nodes and Spark nodes is the cluster name.
Change seed IP fixed the issue.
Thanks,
Rahul Gupta
DEKA Research
Hello,
I am trying to figure out how to do a select * from a table that's stored
in a cassandra database.
[root@beta-new:/home/tiezinteractive/www/cassandra] #cqlsh
Connected to Jokefire Cluster at beta-new.jokefire.com:9160.
[cqlsh 4.1.0 | Cassandra 2.0.6 | CQL spec 3.0.0 | Thrift protocol
It does not matter that this table has one row or n rows. Before fetching
data in the table foo, C* must determine:
1) how many primary keys of table foo match the condition foo_name='dave'
-- read from the 2nd index foo_name where partition key = dave
2) how many primary keys of table foo match
Found the issue and the solution.
Every node has peers column family in system keyspace.
When a VM is copied over and ran as a new node, peers still have the old data
(host ids).
Deleting log files and data files do not solve this issue.
There are two solutions to this:
1. Do not clone
Frankly, no matter how inefficient / expensive the query is, surely it
should still work when there is only 1 row and 1 node (which is localhost)!
I'm starting to wonder if range queries on secondary indexes aren't
supported at all (although if that is the case, I would certainly prefer an
error
I think you just need to quote the Users identifier. Without quotes,
identifiers are treated as case-insensitive.
https://cassandra.apache.org/doc/cql3/CQL.html#identifiers
Adam
On Wed, Aug 13, 2014 at 9:27 AM, Tim Dunphy bluethu...@gmail.com wrote:
Hello,
I am trying to figure out how to
That sounds like a bug (the trace does look fishy). I'm not sure you've
indicated the Cassandra version you use so the first thing might be to
check that this hasn't been fixed in a recent version, but if you are using
a recent release (say 2.0.9), then please do open a JIRA ticket with your
I'm on 2.0.9 - I'll open a JIRA ticket.
thanks,
Ian
On Wed, Aug 13, 2014 at 10:43 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
That sounds like a bug (the trace does look fishy). I'm not sure you've
indicated the Cassandra version you use so the first thing might be to
check that this
I think you just need to quote the Users identifier. Without quotes,
identifiers are treated as case-insensitive.
https://cassandra.apache.org/doc/cql3/CQL.html#identifiers
Hi Adam!
Yes that was it. It's working now.
cqlsh:demo select * from Users;
key
We are building a historical timeseries database for stocks and futures,
with trade prices aggregated into daily bars (open, high, low, close values
for the day). The latest bar for each instrument needs to be updated as new
trades arrive on the realtime data feeds. Depending on the trading volume
On Wed, Aug 13, 2014 at 4:35 AM, DuyHai Doan doanduy...@gmail.com wrote:
add an additional integer column to the partition key (making it a
composite partition key if it isn't already). When inserting, randomly
pick a value between, say, 0 and 10 to use for this column -- Due to the
low
I have to come up with a “event dupe check” system that handles race conditions
where two requests come in at the same time. Obviously this can be solved with
lightweight transactions (if not exists), however I am concerned that there may
be costs/issues hidden to me for doing significant
On Wed, Aug 13, 2014 at 9:16 AM, Wayne Schroeder
wschroe...@pinsightmedia.com wrote:
Are there hidden costs to LWT (paxos) that are not represented in the
total time and number of operations? For example, are there some
under-the-hood locks that could cause contention issues when processing
On Wed, Aug 13, 2014 at 8:01 AM, Jeremy Jongsma jer...@barchart.com wrote:
I've read comments about frequent column updates causing compaction issues
with Cassandra. What is the recommended Cassandra configuration / best
practices for usage scenarios like this?
If your data is frequently
On Wed, Aug 13, 2014 at 7:33 AM, Ian Rose ianr...@fullstory.com wrote:
I'm starting to wonder if range queries on secondary indexes aren't
supported at all (although if that is the case, I would certainly prefer an
error rather than a timeout!). I've been scouring the web trying to find a
On Wed, Aug 13, 2014 at 7:28 AM, Rahul Gupta rgu...@dekaresearch.com
wrote:
Found the issue and the solution.
1. Do not clone existing Cassandra node and use it as additional
node. Always start with a fresh machine which never had any Cassandra
installed in it.
2. Fix the
On Wed, Aug 13, 2014 at 5:53 AM, Ruchir Jha ruchir@gmail.com wrote:
We are adding nodes currently and it seems like compression is falling
behind. I judge that by the fact that the new node which has a 4.5T disk
fills up to 100% while its bootstrapping. Can we avoid this problem with
the
Well… I didn’t expect them to be free :)
Knowing the price would help weigh the consequences of using them though. I
just don’t want to implement a check/write/double check solution if it ends up
being actually more expensive in total operations and time than simply using
LWT. Any thoughts
Can you just give the C* version and the complete DDL script to reproduce
the issue ?
On Wed, Aug 13, 2014 at 10:08 PM, Kevin Burton bur...@spinn3r.com wrote:
I'm tracking down a weird bug and was wondering if you guys had any
feedback.
I'm trying to create ten tables programatically.. .
I'm tracking down a weird bug and was wondering if you guys had any
feedback.
I'm trying to create ten tables programatically.. .
The first one I create, for some reason, isn't created.
The other 9 are created without a problem.
Im doing this with the datastax driver's session.execute().
No
2.0.5… I'm upgrading to 2.0.9 now just to rule this out….
I can give you the full CQL for the table, but I can't seem to reproduce it
without my entire app being included.
If I execute the CQL manually, it works… which is what makes this so weird.
On Wed, Aug 13, 2014 at 1:11 PM, DuyHai Doan
and I'm certain that the CQL is executing… because I get a ResultSet back
and verified that the CQL is correct.
On Wed, Aug 13, 2014 at 1:26 PM, Kevin Burton bur...@spinn3r.com wrote:
2.0.5… I'm upgrading to 2.0.9 now just to rule this out….
I can give you the full CQL for the table, but I
yeah… problem still exists on 2.0.9
On Wed, Aug 13, 2014 at 1:26 PM, Kevin Burton bur...@spinn3r.com wrote:
and I'm certain that the CQL is executing… because I get a ResultSet back
and verified that the CQL is correct.
On Wed, Aug 13, 2014 at 1:26 PM, Kevin Burton bur...@spinn3r.com
Maybe tracing the requests ? (just the one creating the schema of course)
On Wed, Aug 13, 2014 at 10:30 PM, Kevin Burton bur...@spinn3r.com wrote:
yeah… problem still exists on 2.0.9
On Wed, Aug 13, 2014 at 1:26 PM, Kevin Burton bur...@spinn3r.com wrote:
and I'm certain that the CQL is
ah.. good idea. I'll try that now.
On Wed, Aug 13, 2014 at 1:36 PM, DuyHai Doan doanduy...@gmail.com wrote:
Maybe tracing the requests ? (just the one creating the schema of course)
On Wed, Aug 13, 2014 at 10:30 PM, Kevin Burton bur...@spinn3r.com wrote:
yeah… problem still exists on
with key_validation_class = UTF8Type
and comparator = 'CompositeType(LongType,UTF8Type)'
and default_validation_class = UTF8Type;
Number of columns will depend on only first column name in composite column or
both.
For example,
With row key = 1, I have data
1 | 20140813, user1 | value1
1 | 20140813
It still failed. Tracing shows that the query is being executed. Just
that the table isn't created. I did a diff against the two table names and
the only difference is the table name.
I even reversed their creation to see if that fixes it… but it still fails.
Very very weird.
On Wed, Aug
Can you provide the code that you use to create the table? This feels like
code error rather than a database bug.
On Wed, Aug 13, 2014 at 1:26 PM, Kevin Burton bur...@spinn3r.com wrote:
2.0.5… I'm upgrading to 2.0.9 now just to rule this out….
I can give you the full CQL for the table, but
Looks like C* isn't creating the table with the lowest value integer
suffix. I created more tables and even if I reverse their order, the one
with the lowest integer suffix isn't being created.
The CQL is being sent to the server, executed (confirmed via the trace),
but when I read the tables
On Wed, Aug 13, 2014 at 1:59 PM, Kevin Burton bur...@spinn3r.com wrote:
Looks like C* isn't creating the table with the lowest value integer
suffix. I created more tables and even if I reverse their order, the one
with the lowest integer suffix isn't being created.
The CQL is being sent to
Honestly, I'm hoping it's code rather than a database bug (and normally I'd
agree with you).
I'm working on a reduction to see if I can get a basic unit test.
On Wed, Aug 13, 2014 at 1:58 PM, Jonathan Haddad j...@jonhaddad.com wrote:
Can you provide the code that you use to create the
On Wed, Aug 13, 2014 at 12:28 PM, Wayne Schroeder
wschroe...@pinsightmedia.com wrote:
Knowing the price would help weigh the consequences of using them
though. I just don’t want to implement a check/write/double check solution
if it ends up being actually more expensive in total operations
Hi, All,
We are using Cassandra 2.0.7 in a multi DCs environments. If a connected DC is
powered off, we use the 'nodetool removenode' command to remove it from the
connected DCs.
But we found that once the disconnected DC is powered on, it will connect to
other DCs automatically.
How can we
46 matches
Mail list logo
