[MESOS-4210] Investigate increasing protobuf protocol message size limit.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Assignee: Unassigned
• Reporter: Artem Harutyunyan
• Created: 19/Dec/15 23:33
• Updated: 26/May/17 17:18
• Resolved: 26/May/17 17:18

Description

[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) 

The error is presumably caused by a "user sending a very large command line".

Issue Links

• is blocked by: MESOS-7228 Upgrade Mesos to build with proto3.
• Is contained by: MESOS-7228 Upgrade Mesos to build with proto3.
• is related to: MESOS-6644 Mesos master failed to devolve Scheduler HTTP v1 Call
• is related to: MESOS-7017 HTTP API responses can crash the master.
• is related to: MESOS-7123 Investigate splitting offer messages instead of sending a giant single resource offer message.