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

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

     [ https://issues.apache.org/jira/browse/GEODE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker closed GEODE-2802.
--------------------------------

> TombstoneMessage can throw SerializationException when region is configured as persistent and non-persistent in cluster (in different nodes).
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2802
>                 URL: https://issues.apache.org/jira/browse/GEODE-2802
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Anilkumar Gingade
>            Assignee: Anilkumar Gingade
>              Labels: storage_2
>             Fix For: 1.2.0
>
>
> 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;
>         } 
> -
> -



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)