user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>>
Date: Friday, October 14, 2016 at 1:47 PM
To: "user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>"
<user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>>
t;user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>"
<user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>>
Subject: Re: GemFire persisted data corruption - how to debug?
It is highly unusual to use Geode with just a single cache node. A big part
Hi Kapil,
Hmm, that's not good. It looks like it somehow ending up with a key that is
null. Did you have synchronous writes enabled before powering off the VM?
With or without synchronous writes enabled, this is not expected or a known
issue. Every write to the disk store files records an end of
gt;
> Regards
> Kapil
>
> From: Anilkumar Gingade <aging...@pivotal.io>
> Reply-To: "user@geode.incubator.apache.org" <user@geode.incubator.apache.
> org>
> Date: Friday, October 14, 2016 at 10:59 AM
> To: "user@geode.incubator.apache.org" <user@ge
.apache.org>"
<user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>>
Date: Friday, October 14, 2016 at 10:59 AM
To: "user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>"
<user@geode.incubator.apache.org<mailto:user@ge
ursday, October 13, 2016 at 8:31 PM
To: <user@geode.incubator.apache.org<mailto:user@geode.incubator.apache.org>>
Subject: Re: GemFire persisted data corruption - how to debug?
Hi Kapil,
Geode (by default) writes data synchronously to other cluster members. If a
node crashes like i
Kapil,
This is related to GemFire 8.2. If its a critical issue, please reach-out
to GemFire support so that it will be tracked and addressed in time.
Can you see this with Geode versions, this helps to eliminate/identify the
version where the issues i happening.
Is it possible for you to share
Hi Kapil,
Geode (by default) writes data synchronously to other cluster members. If a
node crashes like in your test, the update is preserved by the cluster even in
the absence of persistence. Synchronous disk writes can be turned on (see [1])
but many users prefer to avoid the fsync
Hi Folks,
I am doing some crash testing with a single cache node of GemFire, where I
power off the VM where cache is running and then bring it back up. Upon
restart, GemFire refuses to come up with this error:
Caused by: java.lang.NullPointerException
at
