Actually what I should say is that this does not entirely fix GEODE-8422 it
reduces the frequency to 1/3 of what it was and fixes one issue of GEODE-8422.
It is my understanding we didn't want to hold this release for the other part
of this issue. I will file that under a separate bug.
Thanks,
Mark
On 8/13/20, 9:29 AM, "Mark Hanson" <hans...@vmware.com> wrote:
Yes.
On 8/13/20, 7:27 AM, "Dave Barnes" <dbar...@apache.org> wrote:
Do I understand correctly that this fix, if validated, addresses the
last
remaining release-blocker for 1.13?
On Wed, Aug 12, 2020 at 6:02 PM Mark Hanson <hans...@vmware.com> wrote:
> Not yet, we will need to wait for that to finish cleanly relative to
this
> change. I guess I was just seeking to gain approval for priority of
it once
> it does pass. (Maybe I am being a little over zealous).
>
> Thanks,
> Mark
>
> On 8/12/20, 5:52 PM, "Dave Barnes" <dbar...@apache.org> wrote:
>
> Has the version on the develop branch completed a test cycle?
>
> On Wed, Aug 12, 2020 at 4:52 PM Jianxia Chen <jche...@apache.org>
> wrote:
>
> > +1
> >
> > On Wed, Aug 12, 2020 at 4:41 PM Mark Hanson <hans...@vmware.com>
> wrote:
> >
> > > Hi All,
> > >
> > > We have found a case where tombstones were being cleared when
the
> region
> > > was not initialized. This was causing some test failures and
> potential
> > > field failures. We would like to put this into support/1.13.
> > >
> > > Thanks,
> > > Mark
> > >
> >
>
>
