Thanks for the update Philip, other people have reported high await on a single
volume previously but I don’t think it’s been blamed on noisy neighbours. It’s
interesting that you can have noisy neighbours for IO only.
Out of interest was there much steal reported in top or iostat ?
Cheers
--
> Basically this desire all stems from wanting efficient use of memory.
Do you have any real latency numbers you are trying to tune ?
Otherwise this sounds a little like premature optimisation.
Cheers
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder & Principal Consultant
Ap
> But this becomes troublesome if I add or remove nodes. What effectively I
> want is to partition on the unique id of the record modulus N (id % N; where
> N is the number of nodes).
This is exactly the problem consistent hashing (used by cassandra) is designed
to solve. If you hash the key and
AFAIK any value that is a valid output from murmor3 is a valid token.
The Murmur3Partitioner set’s min and max to long min and max…
public static final LongToken MINIMUM = new LongToken(Long.MIN_VALUE);
public static final long MAXIMUM = Long.MAX_VALUE;
Cheers
-
Aaron M
> I changed logging to debug level, but still nothing is logged.
> Again - any help will be appreciated.
There is nothing at the ERROR level on any machine ?
check nodetool compactionstats to see if a validation compaction is running,
the repair may be waiting on this.
check nodetool netstats
Filed a ticket for this issue :
https://issues.apache.org/jira/browse/CASSANDRA-6467
On Mon, Dec 9, 2013 at 9:56 AM, Parth Patil wrote:
> Thanks Nate, I will file a ticket.
>
>
> On Mon, Dec 9, 2013 at 7:34 AM, Nate McCall wrote:
>
>> If you got that error on an unmodified example from the late
What is the problem to put all nodes on the seed list without any exclusion.
Constant list is the simplest solution.
You should write it once in cassandra.yaml, tar with everything you need
(cassandra, jdk) and copy as many as number of your nodes on the list.
Really 1 thing you should generate is
Look at GossipingPropertyFileSnitch
(http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.html#cassandra/architecture/architectureSnitchesAbout_c.html)
and just use simple seed provider as described in the Datastax multi dc
documentation.
That way for each new node you just need to
My experience is that you must upgrade to 2.0.3 ASAP to fix this.
Michael
On Mon, Dec 9, 2013 at 6:39 PM, David Laube wrote:
> Hi All,
>
> We are running Cassandra 2.0.2 and have recently stumbled upon an issue
> with nodetool repair. Upon running nodetool repair on each of the 5 nodes
> in th
Hi All,
We are running Cassandra 2.0.2 and have recently stumbled upon an issue with
nodetool repair. Upon running nodetool repair on each of the 5 nodes in the
ring (one at a time) we observe the following exceptions returned to standard
out;
[2013-12-08 11:04:02,047] Repair session ff16c510
Hi Data Model Experts,
I have a few questions with data modelling for a particular application.
example
create table messages(
body text,
username text,
tags set
PRIMARY keys(username,tags)
)
Requirements
1) I should be able to query by username and get all the messages for a
particular usernam
Hello everyone,
I have a cassandra cluster running at amazon. I am trying to add a new
datacenter for this cluster now, outside AWS. I know I could use
multiregion, but I would like to be vendor free in terms of cloud.
Reading the article
http://www.datastax.com/docs/datastax_enterprise3.2
Thanks Nate, I will file a ticket.
On Mon, Dec 9, 2013 at 7:34 AM, Nate McCall wrote:
> If you got that error on an unmodified example from the latest source,
> please open an issue:
> https://issues.apache.org/jira/browse/CASSANDRA
>
>
> On Sun, Dec 8, 2013 at 8:00 PM, Parth Patil wrote:
>
>>
2013/12/9 Nate McCall :
> Do you have any secondary indexes defined in the schema? That could lead to
> a 'mega row' pretty easily depending on the cardinality of the value.
That's an interesting point - but no, we don't have any secondary
indexes anywhere. From the heap dump, it's fairly evident
If you got that error on an unmodified example from the latest source,
please open an issue:
https://issues.apache.org/jira/browse/CASSANDRA
On Sun, Dec 8, 2013 at 8:00 PM, Parth Patil wrote:
> Hi Aaron,
> Thanks for your response. I didn't make any change to the code when I got
> that exceptio
For ease of maintenance and because we'll likely have many deployments
where the cluster size is very small (2 - 5 nodes), I'm wondering if I can
set my seed_provider list to contain all nodes except the local node's IP.
ie) For nodes A-C
A-> B, C
B-> A, C
C-> A, B
I think my question is more or
Do you have any secondary indexes defined in the schema? That could lead to
a 'mega row' pretty easily depending on the cardinality of the value.
On Mon, Dec 9, 2013 at 3:02 AM, Klaus Brunner wrote:
> We're running largely default settings, with the exception of shard
> (1) and replica (0-n) cou
We're running largely default settings, with the exception of shard
(1) and replica (0-n) counts and EC2-related snitch etc. No row
caching at all. The logs never showed the same kind of entries
pre-OOM, it basically occurred out of the blue.
However, it seems that the problem has now subsided aft
18 matches
Mail list logo
