>> gemfire.ON_DISCONNECT_CLEAR_PDXTYPEIDS=true I agree that we should make this a public.
Applying the behavior of this by default (without any property setting) may have performance implication. Typically, this scenario is encountered when pdx registry is not persistent; and all the servers stopped/crashed with clients are still running. Which is mostly not recommended. Most of the cases, the pdx registry is configured to be persistent on the server side. -Anil On Thu, Sep 12, 2019 at 10:20 AM Anthony Baker <aba...@pivotal.io> wrote: > Mario, I agree that this seems like a logical choice to automatically > flush the client pdx registry after a disconnect. > > Are there any backwards compatibility concerns with changing the default? > > > Anthony > > > > On Sep 12, 2019, at 4:50 AM, Mario Kevo <mario.k...@est.tech> wrote: > > > > Hi, > > > > just to remind you. > > > > Thanks. > > > > On Mon, 2019-09-09 at 11:22 +0000, Mario Kevo wrote: > >> Hi all, > >> > >> We got the same exception as it is described in > >> > > > https://community.pivotal.io/s/article/Getting-stale-PdxType-error-on-client-after-clean-start-up-of-servers > >> > >> From Resolution part: > >> Instead of removing the PDX disk store manually on the client, set > >> the > >> following hidden GemFire property to clean the PDX disk store on the > >> client when it is disconnected from the cluster: > >> > >> gemfire.ON_DISCONNECT_CLEAR_PDXTYPEIDS=true > >> > >> This can be done setting the property in the client start-up script: > >> > >> -J-Dgemfire.ON_DISCONNECT_CLEAR_PDXTYPEIDS=true > >> > >> > >> Is it possible to get this property as not-hidden and be documented > >> somewhere? > >> > >> Should this property be TRUE by default? > >> > >> This question has been already asked on dev list: > >> > >> > > > http://mail-archives.apache.org/mod_mbox/geode-dev/201703.mbox/%3cecfea1a6-5777-2127-c7ee-caa8039fe...@pivotal.io%3e > >> > >> Thanks and BR, > >> Mario > >> > >> > >> > >> > >
