[
https://issues.apache.org/jira/browse/MESOS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864636#comment-15864636
]
Santhosh Kumar Shanmugham commented on MESOS-4210:
--------------------------------------------------
{quote}
There is a default byte size limit of 64MB when parsing protocol buffers - if a
message is larger than that, it will fail to parse. This can be configured if
you really need to parse larger messages, but it is generally not recommended.
Additionally, ByteSize() returns a 32-bit integer, so there's an implicit limit
on the size of data that can be serialized.
You can certainly use protocol buffers in large data sets, but it's not
recommended to have your entire data set be represented by a single message.
Instead, see if you can break it up into smaller messages.
{quote}
https://groups.google.com/forum/#!topic/protobuf/pb4DaQLHPu8
> Investigate increasing protobuf protocol message size limit.
> ------------------------------------------------------------
>
> Key: MESOS-4210
> URL: https://issues.apache.org/jira/browse/MESOS-4210
> Project: Mesos
> Issue Type: Bug
> Reporter: Artem Harutyunyan
>
> {noformat}
> [libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
> was rejected because it was too big (more than 67108864 bytes). To increase
> the limit (or to disable these warnings), see
> CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
> F20151217 16:33:44.832834 4076 construct.cpp:48] Check failed: parsed
> Unexpected failure while parsing protobuf
> Check failure stack trace: ***
> @ 0x2b9bab353b68 (unknown)
> @ 0x2b9bab353ac4 (unknown)
> @ 0x2b9bab3534ba (unknown)
> @ 0x2b9bab356274 (unknown)
> @ 0x2b9bab339d09 (unknown)
> @ 0x2b9bab338917 (unknown)
> @ 0x2b9bab33f404 (unknown)
> @ 0x2b9b68350e18 (unknown)
> {noformat}
> The error is presumably caused by a "user sending a very large command line".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
