[GEODE-9849] validate serialized blobs when they are stored on a server

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: client/server, core, serialization
• Assignee: Unassigned
• Reporter: Darrel Schneider
• Created: 24/Nov/21 00:08
• Updated: 08/Dec/21 01:08

Description

When a client sends a value to a server, geode try to not deserialize it. It instead just takes the bytes sent to it from the client and stores them on the server. But is some very rare instances the blob may be corrupt. It would be nice if the server could validate the blob BEFORE storing it (and distributing it to other servers and writing to a disk store and sending it over a gateway).
How much validation geode can do without impacting performance and without requiring the server to be able to fully deserialize it not clear. But one validation it could definitely do is to check the first byte of the blob and make sure it is a valid DSCODE. This would detect some of the corruptions we have seen in the past (i.e. "unknown header byte" issues) and be a very efficient check.