You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2017/05/26 17:18:04 UTC

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

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

Anand Mazumdar commented on MESOS-4210:
---------------------------------------

This shouldn't be a concern anymore after the upgrade to proto3 as part of MESOS-7228 that supports message sizes up to 2GB. Marking it as resolved.

> 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
>             Fix For: 1.4.0
>
>
> {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)