On Wed, 2012-09-05 at 13:23 +1200, aaron morton wrote:
> > I believe the question is why is the maximum 2**127 and not
> > 0x
oops - I got the wrong number of digits there.
> The maximum is the size of the digest created by MD5.
(I may be mistaken) - isn't the range of MD5 value
Is there a specific metric you can recommend?
VR
On Wed, Sep 5, 2012 at 9:19 PM, Mohit Anchlia wrote:
> Cassandra exposes lot of metrics through Jconsole. You might be able to
> get some information from Jconsole.
>
>
> On Wed, Sep 5, 2012 at 8:47 PM, Venkat Rama wrote:
>
>> Thanks for the quick
Hi All,
I am a new bee to Cassandra and trying to understand how secondary indexes
work. I have been going over the discussion on
https://issues.apache.org/jira/browse/CASSANDRA-749 about local secondary
indexes. And interesting question on
http://www.mail-archive.com/user@cassandra.apache.org/ms
Thanks, this is exactly it. We'd like to do a rolling upgrade - this is a
production cluster - so I guess we'll upgrade 1.0.6 -> 1.0.11 -> 1.1.4,
then.
/Martin
On Thu, Sep 6, 2012 at 2:35 AM, Omid Aladini wrote:
> Do you see exceptions like "java.lang.UnsupportedOperationException:
> Not a time
Cassandra exposes lot of metrics through Jconsole. You might be able to get
some information from Jconsole.
On Wed, Sep 5, 2012 at 8:47 PM, Venkat Rama wrote:
> Thanks for the quick reply, Mohit.Can we measure/monitor the size of
> Hinted Handoffs? Would it be a good enough indicator of my b
Thanks for the quick reply, Mohit.Can we measure/monitor the size of
Hinted Handoffs? Would it be a good enough indicator of my back log?
Although we know when a network is flaky, we are interested in knowing how
much data is piling up in local DC that needs to be transferred.
Greatly apprec
On Sun, Jul 29, 2012 at 7:40 PM, Dustin Wenz wrote:
> We've just set up a new 7-node cluster with Cassandra 1.1.2 running under
> OpenJDK6.
It's worth noting that Cassandra project recommends Sun JRE. Without
the Sun JRE, you might not be able to use JAMM to determine the live
ratio. Very few pe
As far as I know Cassandra doesn't use internal queueing mechanism specific
to replication. Cassandra sends the write the remote DC and after that it's
upto the tcp/ip stack to deal with buffering. If requests starts to timeout
Cassandra would use HH upto certain time. For longer outage you would h
Hi,
We have multi DC Cassandra ring with 2 DCs setup. We use LOCAL_QUORUM for
writes and reads. The network we have seen between the DC is sometimes
flaky lasting few minutes to few 10 of minutes.
I wanted to know what is the best way to measure/monitor either the lag or
replication latency be
Do you see exceptions like "java.lang.UnsupportedOperationException:
Not a time-based UUID" in log files of nodes running 1.0.6 and 1.0.9?
Then it's probably due to [1] explained here [2] -- In this case you
either have to upgrade all nodes to 1.1.4 or if you prefer keeping a
mixed-version cluster,
http://wiki.apache.org/cassandra/FAQ#unsubscribe
On Wed, Aug 29, 2012 at 3:57 PM, Juan Antonio Gomez Moriano <
mori...@exciteholidays.com> wrote:
>
> --
> *Juan Antonio Gomez Moriano*
> DEVELOPER TEAM LEADER [image: Excite Holidays]
>
> T +61 2 8061 2917
>
> emori...@exciteholidays.com
>
> Www
Surge [1] is scalability focused conference in late September hosted in
Baltimore. It's a pretty cool conference with a good mix of
operationally minded people interested in scalability, distributed
systems, systems level performance and good stuff like that. You should
go! [2]
For those of you
I would try nodetool resetlocalschema.
On 12-09-05 07:08 AM, Martin Koch wrote:
Hi list
We have a 5-node Cassandra cluster with a single 1.0.9 installation
and four 1.0.6 installations.
We have tried installing 1.1.4 on one of the 1.0.6 nodes (following
the instructions on http://www.datas
Hi list
We have a 5-node Cassandra cluster with a single 1.0.9 installation and
four 1.0.6 installations.
We have tried installing 1.1.4 on one of the 1.0.6 nodes (following the
instructions on http://www.datastax.com/docs/1.1/install/upgrading).
After bringing up 1.1.4 there are no errors in th
Hello Aaron,
Thanks a lot for the response. Raised a request
https://issues.apache.org/jira/browse/CASSANDRA-4619
Here is the nodetool dump: (from one of the two nodes in the cluster)
Token: 0
Gossip active: true
Thrift active: true
Load : 147.64 GB
Generation No
Hey folks,
I have a 1.0.11 ring running in production with 6 nodes. Trying to
bootstrap a new node in, and I'm getting the following consistently:
INFO [main] 2012-09-05 04:24:13,317 StorageService.java (line 668)
JOINING: waiting for schema information to complete
After waiting for over 30
forgot to answer your first question. I see this:
INFO 14:31:31,896 No saved local node id, using newly generated:
92109b80-ea0a-11e1--51be601cd0af
On Wed, Sep 5, 2012 at 8:41 AM, Thomas van Neerijnen
wrote:
> Thanks for the help Aaron.
> I've checked NodeIdInfo and LocationInfo as below.
>
You can try increasing streaming throttle.
2012/9/4 Dustin Wenz
> I'm following up on this issue, which I've been monitoring for the last
> several weeks. I thought people might find my observations interesting.
>
> Ever since increasing the heap size to 64GB, we've had no OOM conditions
> that
Thanks for the help Aaron.
I've checked NodeIdInfo and LocationInfo as below.
What am I looking at? I'm guessing the first row in NodeIdInfo represents
the ring with the node ids, but the second row perhaps dead nodes with old
schemas? That's a total guess, I'd be very interested to know what it an
19 matches
Mail list logo
