[jira] [Commented] (MESOS-4210) Investigate increasing protobuf protocol message size limit.

["John Garcia (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073156#comment-15073156 ] 

John Garcia commented on MESOS-4210:
------------------------------------

This came up during a test, where the end-user was attempting to flood the master with large messages. This test does not represent that user's actual production or development usage of the product. 

[The Google Developer's entro on Protobuf advises the following:|https://developers.google.com/protocol-buffers/docs/techniques#streaming]

{quote}Protocol Buffers are not designed to handle large messages. As a general rule of thumb, if you are dealing in messages larger than a megabyte each, it may be time to consider an alternate strategy.{quote}

> 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.4#6332)