Re: Propose including GEODE-7085 in 1.10

[Owen Nichols]

There appears to be consensus that this is a critical fix.

The following commits have been brought into support/1.10.0 
 as the critical fix for 
GEODE-7085 :

git cherry-pick -x f58710116db1cd8c509b59a43ffa050a073234d7 

git cherry-pick -x f17931bf541fc0255112f713931388d9ee0bbc30 


GEODE-7085  has been marked 
as 'resolved in' 1.10.0.

Regards,
-Owen


> On Aug 26, 2019, at 10:50 AM, Eric Shu  wrote:
> 
> +1
> 
> On Mon, Aug 26, 2019 at 10:40 AM Alexander Murmann 
> wrote:
> 
>> +1
>> 
>> While it's not new, it's critical
>> 
>> On Mon, Aug 26, 2019 at 10:38 AM Juan José Ramos 
>> wrote:
>> 
>>> +1
>>> 
>>> On Mon, Aug 26, 2019 at 6:36 PM Dan Smith  wrote:
>>> 
 Hi,
 
 I'd like to propose including the fixes for GEODE-7085 into 1.10 (SHA's
 below). This is not a new issue, but it does result not being able to
 recover from disk without this fix if a cluster has more than 2 billion
 updates to a single bucket from a single member.
 
 SHAs: f587101  ,  f17931bf
 
 Thanks,
 -Dan
 
>>> 
>>> 
>>> --
>>> Juan José Ramos Cassella
>>> Senior Software Engineer
>>> Email: jra...@pivotal.io
>>> 
>> 

Re: Propose including GEODE-7085 in 1.10

[Eric Shu]

+1

On Mon, Aug 26, 2019 at 10:40 AM Alexander Murmann 
wrote:

> +1
>
> While it's not new, it's critical
>
> On Mon, Aug 26, 2019 at 10:38 AM Juan José Ramos 
> wrote:
>
> > +1
> >
> > On Mon, Aug 26, 2019 at 6:36 PM Dan Smith  wrote:
> >
> > > Hi,
> > >
> > > I'd like to propose including the fixes for GEODE-7085 into 1.10 (SHA's
> > > below). This is not a new issue, but it does result not being able to
> > > recover from disk without this fix if a cluster has more than 2 billion
> > > updates to a single bucket from a single member.
> > >
> > > SHAs: f587101  ,  f17931bf
> > >
> > > Thanks,
> > > -Dan
> > >
> >
> >
> > --
> > Juan José Ramos Cassella
> > Senior Software Engineer
> > Email: jra...@pivotal.io
> >
>

Re: Propose including GEODE-7085 in 1.10

[Alexander Murmann]

+1

While it's not new, it's critical

On Mon, Aug 26, 2019 at 10:38 AM Juan José Ramos  wrote:

> +1
>
> On Mon, Aug 26, 2019 at 6:36 PM Dan Smith  wrote:
>
> > Hi,
> >
> > I'd like to propose including the fixes for GEODE-7085 into 1.10 (SHA's
> > below). This is not a new issue, but it does result not being able to
> > recover from disk without this fix if a cluster has more than 2 billion
> > updates to a single bucket from a single member.
> >
> > SHAs: f587101  ,  f17931bf
> >
> > Thanks,
> > -Dan
> >
>
>
> --
> Juan José Ramos Cassella
> Senior Software Engineer
> Email: jra...@pivotal.io
>

Re: Propose including GEODE-7085 in 1.10

[Juan José Ramos]

+1

On Mon, Aug 26, 2019 at 6:36 PM Dan Smith  wrote:

> Hi,
>
> I'd like to propose including the fixes for GEODE-7085 into 1.10 (SHA's
> below). This is not a new issue, but it does result not being able to
> recover from disk without this fix if a cluster has more than 2 billion
> updates to a single bucket from a single member.
>
> SHAs: f587101  ,  f17931bf
>
> Thanks,
> -Dan
>


-- 
Juan José Ramos Cassella
Senior Software Engineer
Email: jra...@pivotal.io

Propose including GEODE-7085 in 1.10

[Dan Smith]

Hi,

I'd like to propose including the fixes for GEODE-7085 into 1.10 (SHA's
below). This is not a new issue, but it does result not being able to
recover from disk without this fix if a cluster has more than 2 billion
updates to a single bucket from a single member.

SHAs: f587101  ,  f17931bf

Thanks,
-Dan