Short answer: upgrade to 0.6.
On Sat, Apr 3, 2010 at 7:56 AM, Anty wrote:
> Does anyone have solve the problem?I encounter the same error too.
>
> On Mon, Mar 29, 2010 at 12:12 AM, Benoit Perroud wrote:
>>
>> I got the same error when the nodes are using lot of I/O, i.e during
>> compaction.
>>
My guess is that the servers I use have not enough I/O nor CPU power.
I run on a virtualized env, and even the vmstat command lag a lot.
But it do not appears that the overall application behavior is
degraded by this error, only the "eventually" takes a little longer.
--
Kind regads,
Benoit.
20
Does anyone have solve the problem?I encounter the same error too.
On Mon, Mar 29, 2010 at 12:12 AM, Benoit Perroud wrote:
> I got the same error when the nodes are using lot of I/O, i.e during
> compaction.
>
> 2010/3/28 Eric Yu :
> > I have not restart my nodes.
> > OK, may be I should give 0.
I got the same error when the nodes are using lot of I/O, i.e during compaction.
2010/3/28 Eric Yu :
> I have not restart my nodes.
> OK, may be I should give 0.6 a try.
>
> On Sun, Mar 28, 2010 at 9:53 AM, Jonathan Ellis wrote:
>>
>> It means that a MessagingService socket closed unexpectedly.
I have not restart my nodes.
OK, may be I should give 0.6 a try.
On Sun, Mar 28, 2010 at 9:53 AM, Jonathan Ellis wrote:
> It means that a MessagingService socket closed unexpectedly. If
> you're starting and restarting nodes that could cause it.
>
> This code is obsolete in 0.6 anyway.
>
> On S
It means that a MessagingService socket closed unexpectedly. If
you're starting and restarting nodes that could cause it.
This code is obsolete in 0.6 anyway.
On Sat, Mar 27, 2010 at 8:51 PM, Eric Yu wrote:
> And one more clue here, when ReplicateFactor is 1, it's OK, after changed to
> 2, the
And one more clue here, when ReplicateFactor is 1, it's OK, after changed to
2, the exception occurred.
On Sun, Mar 28, 2010 at 9:46 AM, Eric Yu wrote:
> Hi Jonathan,
>
> I upgraded my jdk to latest version, and I am sure I start Cassandra with
> it (set JAVA_HOME in cassansra.in.sh).
> But the
Hi Jonathan,
I upgraded my jdk to latest version, and I am sure I start Cassandra with it
(set JAVA_HOME in cassansra.in.sh).
But the exception still there, any idea?
On Sun, Mar 28, 2010 at 12:02 AM, Jonathan Ellis wrote:
> This means you need to upgrade your jdk to build 18 or later
>
> On Sa
Jonathan, thanks for your quick reply. I'll have a try now.
On Sun, Mar 28, 2010 at 12:02 AM, Jonathan Ellis wrote:
> This means you need to upgrade your jdk to build 18 or later
>
> On Sat, Mar 27, 2010 at 10:55 AM, Eric Yu wrote:
> > Hi, list
> > I got this exception when insert into a cluste
This means you need to upgrade your jdk to build 18 or later
On Sat, Mar 27, 2010 at 10:55 AM, Eric Yu wrote:
> Hi, list
> I got this exception when insert into a cluster with 5 node, is this a bug
> or something else is wrong.
>
> here is the system log:
>
> INFO [GMFD:1] 2010-03-27 23:15:16,14
Hi, list
I got this exception when insert into a cluster with 5 node, is this a bug
or something else is wrong.
here is the system log:
INFO [GMFD:1] 2010-03-27 23:15:16,145 Gossiper.java (line 543) InetAddress
/172.19.15.210 is now UP
ERROR [Timer-1] 2010-03-27 23:23:27,739 TcpConnection.java (
11 matches
Mail list logo