I can't explain the technical reason why it's not advisable to bootstrap a
seed. However, from what I've read you would bootstrap the node as a non-seed
first, then add it as seed once it has finished bootstrapping.
On Apr 8, 2011, at 9:30 PM, mcasandra wrote:
in yaml:
# Set to true to
thanks! I'll be watching this issue closely.
On Apr 9, 2011, at 5:41 AM, Chris Goffinet wrote:
We also have a ticket open at
https://issues.apache.org/jira/browse/CASSANDRA-2399
We have observed in production the impact of streaming data to new nodes
being added. We actually have our
Thanks a lot Ed. I understand where was my problem. I thought that
compareWith applied for a rows not for columns.
9 квітня 2011 р. 01:46 Ed Anuff e...@anuff.com написав:
I think the problem is this then:
mutator.addInsertion(timeUUID, columnFamilyName, column);
I'm not sure what
from cassandra-env.sh:
# add this if you're having trouble connecting:
# JVM_OPTS=$JVM_OPTS -Djava.rmi.server.hostname=public name
#
# see
#
http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole
# for more on configuring JMX through firewalls, etc. (Short version:
#
Peter Schuller reported an important bug in
https://issues.apache.org/jira/browse/CASSANDRA-2435:
On one of our clusters with 5 nodes, we did some moves. All looked
well; the moves completed. For unrelated reasons, we wanted to restart
nodes after they had been moved. When we did, three of the 5,
We have a 5 Cassandra nodes with the following configuration:
Casandra Version: 0.6.11
Number of Nodes: 5
Replication Factor: 3
Client: Hector 0.6.0-14
Write Consistency Level: Quorum
Read Consistency Level: Quorum
Ring Topology:
OwnsRange Ring
Did the Cassandra cluster go down or did you start getting failures from the
client when it routed queries to the downed node? The key in the client is to
keep working around the ring if the initial node is down.
--Joe
On Apr 9, 2011, at 12:52 PM, Vram Kouramajian wrote:
We have a 5
The hector clients are used as part of our jetty servers. And, the
jetty servers stop responding when one of the Cassandra nodes go down.
Vram
On Sat, Apr 9, 2011 at 11:54 AM, Joe Stump j...@joestump.net wrote:
Did the Cassandra cluster go down or did you start getting failures from the
The storage proxy latencies are the primary metric: in particular, the
latency histograms show the distribution of query times.
On Fri, Apr 8, 2011 at 5:27 PM, mcasandra mohitanch...@gmail.com wrote:
What are the key things to monitor while running a stress test? There is
tons
of details in
Sounds like the problem might be on the hector side. Lots of hector
users on this list, but usually not a bad idea to ask on
hector-us...@googlegroups.com (cc'd).
The jetty servers stopping responding is a bit vague, somewhere in
your logs is an error message that should shed some light on where
Just tested the 0.7.4 cli against an clean 0.7.4 server and list worked.
If I restart the server while the cli is connected i get...
[default@dev] list data;
Using default limit of 100
null
Aaron
On 8 Apr 2011, at 17:23, Wenjun Che wrote:
Hello
I just upgraded a 1-node setup from rc2 to
What is a storage proxy latency?
By query latency you mean the one in cfstats and cfhistorgrams?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/What-need-to-be-monitored-while-running-stress-test-tp6255765p6257932.html
Sent from the
If there are multiple updates to same columns and scattered accross multiple
sstables then how does cassandra know which sstable has the most recent
value.
--
View this message in context:
Thanks for the info!
Does this also happens if initial_token is set?
Also, I am unable to understand the last line in that JIRA
A potential complication was that seed nodes were moved without using the
correct procedure of de-seeding them first. This was clearly wrong
What is de-seeding
By comparing timestamp. The highest value is supposed to be the most updated
Sent from my iPhone
On 09/04/2011, at 21:02, mcasandra mohitanch...@gmail.com wrote:
If there are multiple updates to same columns and scattered accross multiple
sstables then how does cassandra know which sstable
That I understand but my basic quesiton was how does it know that there are
multiple updates that have occurred on the same column? and how does it
efficiently knows which sstable have these updates?
--
View this message in context:
If an SSTable contains an update for a row (row, not just column), we need
to read from it. See #1608 for some of the ideas that have been floated on
how to improve this situation: the core ones are 1. partitioning local data
so that the the number of files involved in a read is smaller, 2. adding
Recent discussion on dynamic snitch for some background
http://www.mail-archive.com/user@cassandra.apache.org/msg12089.html
1) Adapted phi failure detector as used by gossip, see
o.a.c.locator.DynamicEndpointSnitch
2) tracks last 100 responses from a node
3) in memory only
4) it's expensive
If you just want to benchmark the cluster it wont matter too much, though I
would set keys_cached to 0 and increate memtable throughput to 64 or 128. If
you are testing to get a better idea for your app then use similar settings to
your app.
keys_cahced is the number of keys
for
My understanding of what they did with locking (based on the examples) was to
achieve a level of transaction isolation
http://en.wikipedia.org/wiki/Isolation_(database_systems)
I think the issue here is more about atomicity
http://wiki.apache.org/cassandra/FAQ#batch_mutate_atomic
We cannot
btw, the nodes are a tad out of balance was that deliberate ?
http://wiki.apache.org/cassandra/Operations#Token_selection
http://wiki.apache.org/cassandra/Operations#Load_balancing
Aaron
On 10 Apr 2011, at 08:44, Ed Anuff wrote:
Sounds like the problem might be on the hector side. Lots of
in jconsole MBean org.apache.cassandra.db.StorageProxy
It shows the latency for read and write operations, not just per CF
Aaron
On 10 Apr 2011, at 11:37, mcasandra wrote:
What is a storage proxy latency?
By query latency you mean the one in cfstats and cfhistorgrams?
--
View this
Sorry, I meant to say #2319:
https://issues.apache.org/jira/browse/CASSANDRA-2319
On Sat, Apr 9, 2011 at 6:04 PM, Stu Hood stuh...@gmail.com wrote:
If an SSTable contains an update for a row (row, not just column), we need
to read from it. See #1608 for some of the ideas that have been floated
Also, if you are concerned that your updates are being scattered through
multiple files, there is a metric exposed via JMX that can tell you how many
SSTables your reads need to hit: see the (Recent)SSTablePerRead histogram on
each column family.
Many write patterns won't be affected by the
What is the consistency level you are using ?
And as Ed said, if you can provide the stacktrace that would help too.
On Sat, Apr 9, 2011 at 7:02 PM, aaron morton aa...@thelastpickle.comwrote:
btw, the nodes are a tad out of balance was that deliberate ?
25 matches
Mail list logo
