[GEODE-2802] TombstoneMessage can throw SerializationException when region is configured as persistent and non-persistent in cluster (in different nodes).

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: regions
• Labels: storage_2
• Assignee: Anilkumar Gingade
• Reporter: Anilkumar Gingade
• Created: 20/Apr/17 00:17
• Updated: 17/Jun/17 18:04
• Resolved: 08/May/17 17:27

Description

TombstoneMessage serialization code assumes the member info in RVV to be either membership-id or disk-id and uses this info while de-serializing.
When there is a mix of persistent and non-persistent region in the cluster (between nodes), the above assumption will not hold good; resulting in data serialization exception.

DistributedTombstoneOperation$TombstoneMessage
toData() {
-
-
if (persistent)

{ DiskStoreID id = new DiskStoreID(); InternalDataSerializer.invokeFromData(id, in); mbr = id; }

-
-