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

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2015/03/24 08:38:52 UTC

[jira] [Updated] (BOOKKEEPER-833) EntryLogId and EntryLogLimit should not be larger than Integer.MAX_VALUE

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

Sijie Guo updated BOOKKEEPER-833:
---------------------------------
    Attachment: BOOKKEEPER-833.patch

add constraints on entry log id and entry log size.

> EntryLogId and EntryLogLimit should not be larger than Integer.MAX_VALUE
> ------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-833
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-833
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>            Priority: Blocker
>             Fix For: 4.4.0, 4.3.1
>
>         Attachments: BOOKKEEPER-833.patch
>
>
> currently the index entry position is combined with log id and entry offset inside a log. so it means that log id and entry log file size shouldn't be larger than Integer.MAX_VALUE. otherwise, it would cause trouble.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)