There appears to be consensus that this is a critical fix. The following commits have been brought into support/1.10.0 <https://github.com/apache/geode/tree/release/1.10.0> as the critical fix for GEODE-7085 <https://issues.apache.org/jira/browse/GEODE-7085>:
git cherry-pick -x f58710116db1cd8c509b59a43ffa050a073234d7 <https://github.com/apache/geode/commit/f58710116db1cd8c509b59a43ffa050a073234d7> git cherry-pick -x f17931bf541fc0255112f713931388d9ee0bbc30 <https://github.com/apache/geode/commit/f17931bf541fc0255112f713931388d9ee0bbc30> GEODE-7085 <https://issues.apache.org/jira/browse/GEODE-7085> has been marked as 'resolved in' 1.10.0. Regards, -Owen > On Aug 26, 2019, at 10:50 AM, Eric Shu <e...@pivotal.io> wrote: > > +1 > > On Mon, Aug 26, 2019 at 10:40 AM Alexander Murmann <amurm...@apache.org> > wrote: > >> +1 >> >> While it's not new, it's critical >> >> On Mon, Aug 26, 2019 at 10:38 AM Juan José Ramos <jra...@pivotal.io> >> wrote: >> >>> +1 >>> >>> On Mon, Aug 26, 2019 at 6:36 PM Dan Smith <dsm...@pivotal.io> 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 >>> >>
