Vahram, Thanks for advocating for this issue! While the release it pretty locked down for changes, this looks like a low risk change for an important issue. I’ll cherry-pick the changes onto release/1.2.0.
I also see that a breaking change to the REST API was made in ‘c39585395a’. Can someone take a look at the message vs cause naming for errors? Anthony > On Jun 12, 2017, at 9:43 AM, Vahram Aharonyan <vaharon...@vmware.com> wrote: > > Hi All, > > We really think fix done for GEODE-3023 should be considered for 1.2 version > as well. Especially since similar fix(GEODE-2898) has been already made it to > 1.2 version. So shipping a partial/incomplete fix in 1.2 version for the same > kind of problem does not really provide value, and still leaves the system > exposed with a resiliency problem in case of network problems. > > The problem is indeed critical, it is hitting on nearly every meaningfully > large environment which has reasonable amount of network issues. It turns out > that this problem is impacting entire Geode cluster, whenever there is Geode > client with let say imperfect quality of network connectivity. To overcome > this SSL should be disabled for the cluster, which is not the best way to > proceed. > > Thanks, > Vahram. > > -----Original Message----- > From: Anthony Baker [mailto:aba...@pivotal.io <mailto:aba...@pivotal.io>] > Sent: Monday, June 12, 2017 7:42 PM > To: dev@geode.apache.org <mailto:dev@geode.apache.org> > Subject: Re: release 1.2 > > Got it, thanks! > > Anthony > >> On Jun 10, 2017, at 7:15 PM, Udo Kohlmeyer <ukohlme...@pivotal.io> wrote: >> >> I thought we had moved GEODE-3052 to a later release, given that we have a >> work around for this. >> >> --Udo >> >> >> On 6/10/17 10:15, Anthony Baker wrote: >>> Status update: >>> >>> We have 2 issues left: GEODE-3054 and GEODE-3052. We also had a clean run >>> of the Geode-release jenkins job. So as soon as we can finish off these >>> issues and get another clean run through Jenkins I’ll create a release >>> candidate. How does early next week sound? >>> >>> Anthony >>> >>>> On Jun 8, 2017, at 5:38 PM, Anthony Baker <aba...@pivotal.io> wrote: >>>> >>>> Sounds good. Please cherry-pick these changes onto release/1.2.0 when >>>> ready. >>>> >>>> Anthony >>>> >>>> >>>>> On Jun 8, 2017, at 3:15 PM, Jared Stewart <jstew...@pivotal.io> wrote: >>>>> >>>>> I think we probably ought to include GEODE-3045 >>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3045&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=9jqjvxoQ-RJtsGGvTMldMcrooymcWVqjQhb4GoQ1GQ8&e= >>>>> >>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3045&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=9jqjvxoQ-RJtsGGvTMldMcrooymcWVqjQhb4GoQ1GQ8&e=> >>>>> > as well. >>>>> >>>>>> On Jun 8, 2017, at 3:12 PM, Kenneth Howe <kh...@pivotal.io >>>>>> <mailto:kh...@pivotal.io>> wrote: >>>>>> >>>>>> I think we should also include the fix for GEODE-3054 in 1.2. This is a >>>>>> bug that was introduced in the recent changes to the Gfsh parser, and >>>>>> affects Windows pathnames specified in options to gfsh commands. >>>>>> >>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3054&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=jSeNlEnjklIGLNnCF8I6cG0t06n2NT5xLBe86ewSmXc&e= >>>>>> >>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3054&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=jSeNlEnjklIGLNnCF8I6cG0t06n2NT5xLBe86ewSmXc&e=> >>>>>> >>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3054&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=jSeNlEnjklIGLNnCF8I6cG0t06n2NT5xLBe86ewSmXc&e= >>>>>> >>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3054&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=jSeNlEnjklIGLNnCF8I6cG0t06n2NT5xLBe86ewSmXc&e=> >>>>>> > >>>>>> >>>>>> The fix is currently in testing. >>>>>> >>>>>> >>>>>>> On Jun 8, 2017, at 2:23 PM, Bruce Schuchardt <bschucha...@pivotal.io >>>>>>> <mailto:bschucha...@pivotal.io>> wrote: >>>>>>> >>>>>>> I'd like to include the fix for GEODE-3052 in the 1.2 release. It's >>>>>>> under review now and has passed new tests and is in precheckin testing. >>>>>>> >>>>>>> >>>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3052&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=T_2Qx57Vhl2-Z_X8qw8OOSwcKYzGBg0IFafSWdbIMPs&e= >>>>>>> >>>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_GEODE-2D3052&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=wpTWSXVvcGFCkFEMePbOecdHHTbyiIj9aWq7oqKb0J8&m=3eSDKrOEyEHtI5Oe9-iROOP-AWX9d-a1B-s9UX41yU4&s=T_2Qx57Vhl2-Z_X8qw8OOSwcKYzGBg0IFafSWdbIMPs&e=> >>>>>>> >>>>>>> >>>>>>> "Restarting 2 locators within 1s of each other causes potential locator >>>>>>> split brain"
