Hi again,
Small update on the issue,
*KeyspaceDefinition keyspaceDefinition =
HFactory.createKeyspaceDefinition(KEYSPACE_NAME,
org.apache.cassandra.locator.SimpleStrategy, 1, Arrays.asList(cfDef));*
works fine with cassandra-0.7.4/thrift-19.4.0.
But when I am running the same
I am having an issue with del CF[key] not deleting data in CLI on 0.7.4.
Here is how I can reproduce:
1. create a CF with UUID as row key and run 'assume CF keys as lexicaluuid'
2. insert a row, with 62397363-7d4f-4b12-a1eb-f0cd29dca735 as key (just an
example).
3. 'get
managed to resolve the earlier error
but is getting this exception now, any way to increase the heap space, or is a
non-related issue?
Exception in thread main java.lang.OutOfMemoryError: Java heap space
at
see conf/cassandra-env.sh to increase the JVM Heap Background reading
http://wiki.apache.org/cassandra/MemtableThresholds
There is a fix in 0.7.5 that would help you right now :) If you cannot increase
the JVM Heap reduce the in_memory_compaction_limit in conf/cassandra/yaml
Aaron
On 13 Apr
I am not running any firewall this physical machine not EC2,I can telnet
to port 8080
telnet 127.0.0.1 8080
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
On 04/13/2011 06:59 AM, aaron morton wrote:
Can you connect from the local machine
This solved we are doing some thing wrong in our application thanks for
your help.
On 04/13/2011 01:43 AM, Peter Schuller wrote:
I have two cassandra node's,If Boot strapped nodes goes down my service
remains alive,But if my non Bootstrap (master) node goes down my live site
goes down as
I have questions below.
1. In cassandra server, row key, column name and column value are saved in
byte[], aren't they?
2. If I call hector's mutator.addInsertion(rowKey, cfName, HColumnString,
Integer), does the transformation from String/Integer to byte[] occur at
client? or server?
3. If 2
Peter all great questions. Let me try to answer them.
You are right about the automatic fallback to ONE. Its quite possible, if 2
nodes die for some reason I will have the same problem. So probably the right
thing to do would be to read/write at ONE only when we lose a DC by changing
some
Hi all,
Just some thoughts and question I have about cassandra data modeling.
If I understand well, cassandra is better on writing than on reading.
So you have to think about your queries to design cassandra schema. We
are doing incremental design, and already have our system in
production and
The apache Hudson server address needs to be updated on the download
page, it is now:
https://builds.apache.org
The link to the latest builds from the download page:
http://cassandra.apache.org/download/
Needs to be updated from:
On Wed, Apr 13, 2011 at 10:39 AM, Jean-Yves LEBLEU jleb...@gmail.com wrote:
Hi all,
Just some thoughts and question I have about cassandra data modeling.
If I understand well, cassandra is better on writing than on reading.
So you have to think about your queries to design cassandra schema.
I'd be more inclined to suspect a bug in sstable2json.
On Wed, Apr 13, 2011 at 8:59 AM, Terje Marthinussen
tmarthinus...@gmail.com wrote:
Hi,
we do see occasional row corruptions now and then and especially in hinted
handoffs.
This may be related to fairly long rows (millions of columns)
I
Dear Jean-Yves,
You can have a different approach of the problem.
You need on one side a relational database (MySQL, PostGreSQL) or SolR (as
an very efficient index) and on the other side Cassandra. The relational
database or SolR must contain the minimum amount of information possible : a
date
Peter Schuller wrote:
Saturated.
But read latency is still something like 30ms which I would think would be
much higher if it's saturated.
--
View this message in context:
Is it possible in 0.7.x to have indexes on heterogeneous rows, which have
different sets of columns?
For example, let's say you have three types of objects (1, 2, 3) which each
had three members. If your rows had the following pattern
type=1 a=? b=? c=?
type=2 d=? e=? f=?
type=3 g=? h=? i=?
One correction qu size in iostat ranges between 6-120. But still this doesn't
explain why read latency is low in cfstats.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/flush-largest-memtables-at-messages-in-7-4-tp6266221p6269875.html
Sent from
Sorry for the complex setup, took a while to identify the behavior and
I'm still not sure I'm reading the code correctly.
Scenario:
Six node ring w/ SimpleSnitch and RF3. For the sake of discussion
assume the token space looks like:
node-0 1-10
node-1 11-20
node-2 21-30
node-3 31-40
node-4
*Prasanna Jayapalan Senior Solution Consultant Evident Software
**O:(973)-622-5656 X 253
*
First, our contract with the client says we'll give you the answer or
a timeout after rpc_timeout. Once we start trying to cheat on that
the client has no guarantee anymore when it should expect a response
by. So that feels iffy to me.
Second, retrying to a different node isn't expected to give
But read latency is still something like 30ms which I would think would be
much higher if it's saturated.
No. You're using stress, so you have some total cap on concurrency.
Given a fixed concurrency, you'll saturate at some particular average
latency which is mostly a function of the backlog
http://wiki.apache.org/cassandra/FAQ#unsubscribe
--
/ Peter Schuller
On Tue, Apr 12, 2011 at 7:16 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
As some may have heard, CQL is going to be in 0.8. It's a level of
abstraction that will hopefully make the lives of client developers
substantially easier. The ideal is to make it so client devs only need to do
So we're not currently using a dynamic snitch, only the SimpleSnitch
is at play (lots of history as to why, I won't go into it). If this
would solve our problems I'm fine changing it.
Understood re: client contract. I guess in this case my issue is that
the server we're connected to never tries
Yes, we've had dynamic snitch on by default in all the 0.7 releases so
it's pretty well tested by this point.
On Wed, Apr 13, 2011 at 1:17 PM, Erik Onnen eon...@gmail.com wrote:
So we're not currently using a dynamic snitch, only the SimpleSnitch
is at play (lots of history as to why, I won't
I still don't understand. You would expect read latency to increase
drastically when it's fully saturated and lot of READ drop messages also,
correct? I don't see that in cfstats or system.log which I don't really
understand why.
--
View this message in context:
1. Yes
2. Client
3. NA
4. Not sure how Hector handles it, try
https://github.com/zznate/cassandra-tutorial or
https://github.com/zznate/hector-examples
Aaron
On 14/04/2011, at 1:28 AM, 박용욱 colin.wook.p...@gmail.com wrote:
I have questions below.
1. In cassandra server, row key, column
One last coda, for other noobs to cassandra like me. If you use
NetworkTopologyStrategy with replication_factor 1, make sure you have EC2
instance in multiple availability zones. I was doing baby steps, and tried
doing a cluster in one AZ (before spreading to multiple AZs) and was getting
the
I still don't understand. You would expect read latency to increase
drastically when it's fully saturated and lot of READ drop messages also,
correct? I don't see that in cfstats or system.log which I don't really
understand why.
No. With a fixed concurrency there is only so many outstanding
Hi Everyone,
I was going thru Cassandra By Example Blog
http://www.rackspace.com/cloud/blog/2010/05/12/cassandra-by-example/ and I had
a question about the user sign up section:
username = 'jericevans'
password = '**'
useruuid = str(uuid())
columns = {'id': useruuid, 'username':
We have been successful in implementing, at scale, the comments you
posted here. I'm wondering what we can do about deleting data
however.
The way I see it, we have considerably more storage capacity in NY,
but not in the other sites. Using this technique here, it occurs to
me that we would
Actually when I run 2 stress clients in parallel I see Read Latency stay the
same. I wonder if cassandra is reporting accurate nos.
I understand your analogy but for some reason I don't see that happening
with the results I am seeing with multiple stress clients running. So I am
just confused
On Wed, 2011-04-13 at 15:07 -0700, Drew Kutcharian wrote:
username = 'jericevans'
password = '**'
useruuid = str(uuid())
columns = {'id': useruuid, 'username': username, 'password': password}
USER.insert(useruuid, columns)
USERNAME.insert(username, {'id': useruuid})
How can I
Thanks for your response. In general, seems like you always need some kind of
external coordination if you are doing inverted indexes. How do others tackle
this issue?
Now would using secondary indexes be a good idea in this case considering
cardinality of the keys will be pretty high?
Thanks very much Aaron!
4. Not sure how Hector handles it, try
https://github.com/zznate/cassandra-tutorial or
https://github.com/zznate/hector-examples
https://github.com/zznate/hector-examplesLet me ask question 4 again. :)
1. RandomPartitioner and OrderPreservingPartitioner response same
Hi All,
We are using three ssd disks with cassandra 0.7.3 , should we set
them as raid0 .What are the advantages and disadvantages of doing this.
Please advise.
Thanks
Anurag
RAID 0 is the fastest, but you'll lose the whole array if you lose a drive. One
thing to keep in mind is that SSDs get slower as they get filled up and closer
to their capacity due to garbage collection.
If you want more info on how SSDs perform in general, Percona guys have done
extensive
36 matches
Mail list logo
