Hi!
I accidentally swapped the thrift and JMX port when I tried to connect to the
JMX interface. This crashes cassandra instantaneously with OOM.
$ jconsole service:jmx:rmi:///jndi/rmi://localhost:9160/jmxrmi
INFO 16:55:36,568 Binding thrift service to localhost/127.0.0.1:9160
INFO 16:55:36,
On Thu, Jun 10, 2010 at 10:05 AM, Timo Nentwig wrote:
> Hi!
>
> I accidentally swapped the thrift and JMX port when I tried to connect to
> the JMX interface. This crashes cassandra instantaneously with OOM.
>
https://issues.apache.org/jira/browse/THRIFT-601
-Brandon
Supposedly that's fixed now, so I've re-opened
https://issues.apache.org/jira/browse/CASSANDRA-475
On Thu, Jun 10, 2010 at 8:20 AM, Brandon Williams wrote:
> On Thu, Jun 10, 2010 at 10:05 AM, Timo Nentwig wrote:
>
>> Hi!
>>
>> I accidentally swapped the thrift and JMX port when I tried to connect
Hi,
We've been fiddling around with a small Cassandra cluster, bringing
nodes up and down, to get a feel for how things are replicated and how
spinning up a new node works (before having to learn it live :). We are
using the trunk because we want to use the expiration feature. Along
with th
On Thu, Jun 10, 2010 at 17:16, Ronald Park wrote:
> What we found was that, if the node on which we originally installed the
> keyspace was down when a new node is added, the new node does not get the
> keyspace schema. In some regards, it is now the 'master', at least in
> distributing the keysp
I am looking at Cassandra 0.6.2's source code, and am unable to figure
out where, if at all, repartitioning happens in the case of failure.
The Gossiper's onDead message is ignored. Can someone please clarify
this for me?
