Damn, how embarrassing! User error.Thank you so much for the help.
On Fri, Aug 28, 2009 at 1:00 PM, Jonathan Ellis wrote:
> Oh, I see the problem: nodeprobe uses the jmx port (specified in
> cassandra.in.sh -- default 8080), not the thrift port.
>
Oh, I see the problem: nodeprobe uses the jmx port (specified in
cassandra.in.sh -- default 8080), not the thrift port.
Can you file a bug with Thrift/java not to OOM when someone connects
to the socket and sends nonsense? :)
https://issues.apache.org/jira/browse/THRIFT
-Jonathan
On Fri, Aug 28,
I went and grabbed apache-cassandra-incubating-2009-08-20_13-02-45-src
and I get the same symptoms when using that version.
Thanks again - Simon
On Fri, Aug 28, 2009 at 12:34 PM, Jonathan Ellis wrote:
> On Fri, Aug 28, 2009 at 11:25 AM, Simon Smith wrote:
>> I'm getting a traceback when using nod
On Fri, Aug 28, 2009 at 11:25 AM, Simon Smith wrote:
> I'm getting a traceback when using nodeprobe against Cassandra.
That looks like a Thrift bug. :(
Can you try an older version of Cassandra, e.g. trunk from a week ago,
or the beta1 release, to see if the Thrift library upgrade from
yesterday
I'm getting a traceback when using nodeprobe against Cassandra.
Immediately below is the traceback on the screen running cassandra -f
that I get when when I do a nodeprobe command, (e.g. ./nodeprobe -host
myhostname.localdomain -port 9160 info). The config and the
traceback on the nodeprobe scr
