You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by "Anilkumar Gingade (JIRA)" <ji...@apache.org> on 2017/03/15 21:31:41 UTC

[jira] [Reopened] (GEODE-2398) Sporadic Oplog corruption due to channel.write failure

     [ https://issues.apache.org/jira/browse/GEODE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anilkumar Gingade reopened GEODE-2398:
--------------------------------------

We need to make similar change (as done by ken in Oplog)  in OverflowOplog".

> Sporadic Oplog corruption due to channel.write failure
> ------------------------------------------------------
>
>                 Key: GEODE-2398
>                 URL: https://issues.apache.org/jira/browse/GEODE-2398
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Kenneth Howe
>            Assignee: Kenneth Howe
>             Fix For: 1.2.0
>
>
> There have been some occurrences of Oplog corruption during testing that have been traced to failures in writing oplog entries to the .crf file. When it fails, Oplog.flush attempts to write a ByteBuffer to the file channel. The call to channel.write(bb) method returns 0 bytes written, but the source ByteBuffer position is moved to the ByteBuffer limit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)