Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
This was reported by Kevin Sweeney.
An error deserializing a protobuf, for example from a network scanner or a slave that didn't get upgraded, should not cause the master process to crash. It should instead log an exception.
Attachments
Issue Links
- duplicates
-
MESOS-4 Master and slaves should be defensive of badly formed protobufs
- Resolved