[
https://issues.apache.org/jira/browse/BOOKKEEPER-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856249#comment-15856249
]
ASF GitHub Bot commented on BOOKKEEPER-998:
-------------------------------------------
Github user eolivelli commented on the issue:
https://github.com/apache/bookkeeper/pull/104
@revans2
IMHO it would be better to make it configurable as system property or in
ServerConfiguration it would be even better, so it would be more "testable".
I'm not aware of some system property naming convention, maybe you can
suggest one and then the discuss is open.
IMHO the max entry size can be related to the max Netty frame size but
maybe we can use two different limits. For instance on the wire we need headers
@sijie what to you think ?
I think that at Salesforce they make large use of big entries (as they
store BLOBs on BK), maybe JV as some number to share
For me, I'm starting a new project which will need to store "huge" (more
than 10 MB) entries and so I will need to set this limit to a greater value
that 5MB
> Increased the max entry size to 5MB
> -----------------------------------
>
> Key: BOOKKEEPER-998
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-998
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> In practice we have found the Bookkeeper can handle 5MB entries without
> issue. We should make the {{PerChannelBookieClient.MAX_FRAME_LENGTH}}, the
> {{BookieNettyServer.maxMessageSize}} and the
> {{EntryLogger.MAX_SANE_ENTRY_SIZE}} size all consistent with one another, and
> ideally 5MB.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
