You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Anilkumar Gingade (Jira)" <ji...@apache.org> on 2019/09/12 18:29:00 UTC

[jira] [Updated] (GEODE-7197) Improving the pdx type clear behavior with ON_DISCONNECT_CLEAR_PDXTYPEIDS

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

Anilkumar Gingade updated GEODE-7197:
-------------------------------------
    Affects Version/s: 1.11.0

> Improving the pdx type clear behavior with ON_DISCONNECT_CLEAR_PDXTYPEIDS
> -------------------------------------------------------------------------
>
>                 Key: GEODE-7197
>                 URL: https://issues.apache.org/jira/browse/GEODE-7197
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>    Affects Versions: 1.11.0
>            Reporter: Anilkumar Gingade
>            Priority: Major
>
> When the client connects to the servers, it will retrieve PDX type information from the servers and update the local PDX information.
> When pdx registry is not persistent on server or persistent pdx registry is removed; and all the servers are stopped/crashed with clients still running. 
> If the client with previous pdx type info connects to cluster with servers that are re-started, the client will see stale pdx type error.
> To fix this currently a system property is used to clear the pdx type on client side:
> gemfire.ON_DISCONNECT_CLEAR_PDXTYPEIDS=true
> Instead of this, the clients can detect if they have stale data and automatically initiate a recovery of the new pdx types. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)