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

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:00 UTC

[jira] [Updated] (ZOOKEEPER-1520) A txn log record with a corrupt sentinel byte looks like EOF

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

Michael Han updated ZOOKEEPER-1520:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> A txn log record with a corrupt sentinel byte looks like EOF
> ------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1520
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1520
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.3.5
>         Environment: all
>            Reporter: Bill Bridge
>            Assignee: Bill Bridge
>            Priority: Minor
>              Labels: newbie, patch
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ant.out, checkout.out, init.out, init.out, ZOOKEEPER-1520.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In Util.readTxnBytes() the sentinel is compared with 0x42 and if it does not match then the record is considered partially written and thus the EOF. However if it is a partial record the sentinel should be 0x00 since that is what the log is initialized with. Any other value would indicate corruption and should throw an IOException rather than indicate EOF. See [ZOOKEEPER-1453|https://issues.apache.org/jira/browse/ZOOKEEPER-1453] for a related issue. 



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