[
https://issues.apache.org/jira/browse/GEODE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982095#comment-15982095
]
ASF GitHub Bot commented on GEODE-2398:
---------------------------------------
GitHub user lgallinat opened a pull request:
https://github.com/apache/geode/pull/477
GEODE-2398: fix oplog corruption in overflow oplogs
* ported changes from original fix in Oplog.java to
OverflowOplog.java
@agingade @dschneider-pivotal @pivotal-eshu @pdxrunner
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/geode feature/GEODE-2398overflow
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/477.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #477
----
----
> 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: Anilkumar Gingade
> 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)
