You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by B R <so...@gmail.com> on 2010/01/28 13:44:13 UTC
EOFException after upgrading to 0.5.0
Hi guys,
We are in the process of upgrading from Cassandra 0.4.2 to 0.5.0 The first
issue I faced was :
java.lang.OutOfMemoryError: Java heap space
at org.apache.cassandra.db.CommitLog.recover(CommitLog.java:318)
at
org.apache.cassandra.db.RecoveryManager.doRecovery(RecoveryManager.java:65)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:90)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:166)
After search the mailing lists, I found that it was because of an issue with
commit log format. After creating a new file, I could proceed to run a test
sample to insert and read back data. There are no problems with the
application, but in the system log, I have come across hundreds of entries
of the following type.
WARN [UDP Selector Manager] 2010-01-28 18:02:02,828 UdpConnection.java (line
152) Exception was generated at : 01/28/2010 18:02:02 on thread UDP Selector
Manager
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readUTF(DataInputStream.java:592)
at java.io.DataInputStream.readUTF(DataInputStream.java:547)
at
org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:160)
at
org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:133)
at
org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:156)
at
org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:144)
at org.apache.cassandra.net.UdpConnection.read(UdpConnection.java:143)
at
org.apache.cassandra.net.SelectorManager.doProcess(SelectorManager.java:149)
at
org.apache.cassandra.net.SelectorManager.run(SelectorManager.java:107)
Please suggest what could be the reason for this ?
Thanks,
~B
Re: EOFException after upgrading to 0.5.0
Posted by B R <so...@gmail.com>.
Thanks for your reply.
The issues have been solved.
~B
On Thu, Jan 28, 2010 at 7:30 PM, Jonathan Ellis <jb...@gmail.com> wrote:
> please read NEWS.txt, both of your problems are covered there (flush
> your commitlog, and don't mix 0.4 and 0.5 nodes in the same cluster)
>
> On Thu, Jan 28, 2010 at 6:44 AM, B R <so...@gmail.com>
> wrote:
> > Hi guys,
> >
> > We are in the process of upgrading from Cassandra 0.4.2 to 0.5.0 The
> first
> > issue I faced was :
> >
> > java.lang.OutOfMemoryError: Java heap space
> > at org.apache.cassandra.db.CommitLog.recover(CommitLog.java:318)
> > at
> >
> org.apache.cassandra.db.RecoveryManager.doRecovery(RecoveryManager.java:65)
> > at
> >
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:90)
> > at
> >
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:166)
> >
> > After search the mailing lists, I found that it was because of an issue
> with
> > commit log format. After creating a new file, I could proceed to run a
> test
> > sample to insert and read back data. There are no problems with the
> > application, but in the system log, I have come across hundreds of
> entries
> > of the following type.
> >
> > WARN [UDP Selector Manager] 2010-01-28 18:02:02,828 UdpConnection.java
> (line
> > 152) Exception was generated at : 01/28/2010 18:02:02 on thread UDP
> Selector
> > Manager
> >
> > java.io.EOFException
> > at java.io.DataInputStream.readFully(DataInputStream.java:180)
> > at java.io.DataInputStream.readUTF(DataInputStream.java:592)
> > at java.io.DataInputStream.readUTF(DataInputStream.java:547)
> > at
> > org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:160)
> > at
> > org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:133)
> > at
> > org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:156)
> > at
> > org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:144)
> > at org.apache.cassandra.net.UdpConnection.read(UdpConnection.java:143)
> > at
> >
> org.apache.cassandra.net.SelectorManager.doProcess(SelectorManager.java:149)
> > at
> > org.apache.cassandra.net.SelectorManager.run(SelectorManager.java:107)
> >
> > Please suggest what could be the reason for this ?
> >
> > Thanks,
> >
> > ~B
> >
>
Re: EOFException after upgrading to 0.5.0
Posted by Jonathan Ellis <jb...@gmail.com>.
please read NEWS.txt, both of your problems are covered there (flush
your commitlog, and don't mix 0.4 and 0.5 nodes in the same cluster)
On Thu, Jan 28, 2010 at 6:44 AM, B R <so...@gmail.com> wrote:
> Hi guys,
>
> We are in the process of upgrading from Cassandra 0.4.2 to 0.5.0 The first
> issue I faced was :
>
> java.lang.OutOfMemoryError: Java heap space
> at org.apache.cassandra.db.CommitLog.recover(CommitLog.java:318)
> at
> org.apache.cassandra.db.RecoveryManager.doRecovery(RecoveryManager.java:65)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:90)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:166)
>
> After search the mailing lists, I found that it was because of an issue with
> commit log format. After creating a new file, I could proceed to run a test
> sample to insert and read back data. There are no problems with the
> application, but in the system log, I have come across hundreds of entries
> of the following type.
>
> WARN [UDP Selector Manager] 2010-01-28 18:02:02,828 UdpConnection.java (line
> 152) Exception was generated at : 01/28/2010 18:02:02 on thread UDP Selector
> Manager
>
> java.io.EOFException
> at java.io.DataInputStream.readFully(DataInputStream.java:180)
> at java.io.DataInputStream.readUTF(DataInputStream.java:592)
> at java.io.DataInputStream.readUTF(DataInputStream.java:547)
> at
> org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:160)
> at
> org.apache.cassandra.net.HeaderSerializer.deserialize(Header.java:133)
> at
> org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:156)
> at
> org.apache.cassandra.net.MessageSerializer.deserialize(Message.java:144)
> at org.apache.cassandra.net.UdpConnection.read(UdpConnection.java:143)
> at
> org.apache.cassandra.net.SelectorManager.doProcess(SelectorManager.java:149)
> at
> org.apache.cassandra.net.SelectorManager.run(SelectorManager.java:107)
>
> Please suggest what could be the reason for this ?
>
> Thanks,
>
> ~B
>