I believe we'll have to cherry-pick 1448c83c2a910b2891b4c13f1b4cbed2920252de across. Unfortunately it went in as a merge (there was a hiccup on squash and merge where the try-again didn't do a squash merge :-(.
On Wed, Dec 11, 2019 at 11:30 AM Mark Hanson <mhan...@pivotal.io> wrote: > Can I get the SHA of the commit? > > Thanks, > Mark > > > On Dec 11, 2019, at 11:02 AM, Jason Huynh <jhu...@pivotal.io> wrote: > > > > Hello, > > > > GEODE-7538 was highlighted as blocking the 1.11 release. This has now > been > > addressed and propose that this gets merged over to release 1.11. > > > > This issue solves a few things, most notably: GEODE-7510 shows > > inconsistency between secondaries and primaries. GEODE-7538 showed > > operations not consistently being applied. The code change is a revert > > that modified profile calculation. It may affect other areas that were > > showing up as flaky as it's timing related. > > > > Thanks, > > -Jason > >
