Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 3 Aug 2012 10:33:03 +0000 (UTC)
From: =?utf-8?Q?Ivo_Mei=C3=9Fner_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <871790799.9621.1343989983683.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1624491622.4291.1343895182925.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (CASSANDRA-4481) Commitlog not replayed after
 restart - data lost
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-4481?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13427970#comment-13427970 ]=20

Ivo Mei=C3=9Fner commented on CASSANDRA-4481:
----------------------------------------

I am still trying to narrow it down. I have created a new keyspace ("testke=
yspace") with the same configuration and structure.=20
When I only use the testkeyspace, the error does not occur, everything in t=
he commitlog is available after reboot:=20

The following works as expected:=20
1. Insert dataA in testkeyspace
2. Reboot -> 1 replayed mutations
3. Get dataA returns data as expected

The following does not work:
1. Insert dataA in testkeyspace
2. Get dataA from testkeyspace -> returns data as expected
3. Insert dataB in brokenkeyspace
4. Get dataB from brokenkeypsace -> returns data as expected
5. Reboot -> 0 replayed mutations
6. Get dataA from testkeyspace -> NO DATA
7. Get dataB from brokenkeyspace -> NO DATA

So it seems to have something to do with the "broken" keyspace. I don't kno=
w yet how to get the keyspace into that state. So any input of how I can fi=
gure it out or what I could try would be appreciated.

I have changed the Fix-Version to 1.1.4.=20
               =20
> Commitlog not replayed after restart - data lost
> ------------------------------------------------
>
>                 Key: CASSANDRA-4481
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4481
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>         Environment: Single node cluster on 64Bit CentOS
>            Reporter: Ivo Mei=C3=9Fner
>            Priority: Critical
>             Fix For: 1.1.4
>
>
> When data is written to the commitlog and I restart the machine, all comm=
ited data is lost that has not been flushed to disk.=20
> In the startup logs it says that it replays the commitlog successfully, b=
ut the data is not available then.=20
> When I open the commitlog file in an editor I can see the added data, but=
 after the restart it cannot be fetched from cassandra.=20
> {code}
>  INFO 09:59:45,362 Replaying /var/myproject/cassandra/commitlog/CommitLog=
-83203377067.log
>  INFO 09:59:45,476 Finished reading /var/myproject/cassandra/commitlog/Co=
mmitLog-83203377067.log
>  INFO 09:59:45,476 Log replay complete, 0 replayed mutations
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira