OK, Gester, please merge.
Thanks,
Dave
On Wed, Jul 1, 2020 at 8:33 AM Bruce Schuchardt wrote:
> +1
> I reviewed this PR and, as Gester said, it's low risk. If it fixes a
> problem someone is having let's backport it.
>
> On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote:
>
> Customer
+1
I reviewed this PR and, as Gester said, it's low risk. If it fixes a problem
someone is having let's backport it.
On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote:
Customer encountered a singlehop getAll failure due to
SerializationException which is identified as socket error. The
n Tue, Jun 30, 2020 at 3:58 PM Jinmei Liao wrote:
>
>> +1
>>
>> From: Owen Nichols
>> Sent: Tuesday, June 30, 2020 3:56 PM
>> To: dev@geode.apache.org
>> Subject: Re: [PROPOSAL] merge GEODE-8259 to support branc
n Nichols
> Sent: Tuesday, June 30, 2020 3:56 PM
> To: dev@geode.apache.org
> Subject: Re: [PROPOSAL] merge GEODE-8259 to support branches
>
> +1
>
> On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote:
>
> Customer encountered a singlehop getAll failure due to
&g
+1
On Tue, Jun 30, 2020 at 3:58 PM Jinmei Liao wrote:
> +1
>
> From: Owen Nichols
> Sent: Tuesday, June 30, 2020 3:56 PM
> To: dev@geode.apache.org
> Subject: Re: [PROPOSAL] merge GEODE-8259 to support branches
>
> +1
>
> On 6/
Customer encountered a singlehop getAll failure due to SerializationException
which is identified as socket error. The solution is to retry the getAll in
this race condition (currently we did not retry).
The fix is tested in both develop and support branches. The fix is conservative
and very
+1
From: Owen Nichols
Sent: Tuesday, June 30, 2020 3:56 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] merge GEODE-8259 to support branches
+1
On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote:
Customer encountered a singlehop getAll f
+1
On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote:
Customer encountered a singlehop getAll failure due to
SerializationException which is identified as socket error. The solution is
to retry the getAll in this race condition (currently we did not retry).
The fix is tested in both
Customer encountered a singlehop getAll failure due to
SerializationException which is identified as socket error. The solution is
to retry the getAll in this race condition (currently we did not retry).
The fix is tested in both develop and support branches. The fix is
conservative and very low
