Hi, I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13 release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might become more pronounced . It's not about every workload, but rather about some specific ones, of course. I think it's nice to have a way to mitigate the issue if it appears in the fields after upgrading to 1.13.
The change in the context of fixing KUDU-1587 consists of three patches posted for review: [3], [4], [5]. I think it's realistic to expect those patches to land this week, assuming I'm getting review feedback on those. At least Andrew Wong already took a look at [4] (thank you Andrew!) [1] https://issues.apache.org/jira/browse/KUDU-1587 [2] https://issues.apache.org/jira/browse/KUDU-2727 [3] https://gerrit.cloudera.org/#/c/16312/ [4] https://gerrit.cloudera.org/#/c/16332/ [5] https://gerrit.cloudera.org/#/c/16343/ Thanks! Kind regards, Alexey On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <[email protected]> wrote: > Hi, > > To make sure we don't break backward and/or forward compatibility, I > changed the > priority of KUDU-3176[1] to blocker and will fix it before I cut the > release. > I'll also be out of office next week, so I propose to postpone the cutting > of > the branch to 8/24 Monday. > > If you know of any other outstanding bugs that we should consider as > blockers, > please list them in this thread (and also change their priority on JIRA). > > Also, please don't forget to list your significant changes for the release > notes > in https://s.apache.org/kudu1.13rn > > Thanks, > Attila > > [1] https://issues.apache.org/jira/browse/KUDU-3176 > > On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote: > > Hi Kudu devs, > > > > It's been almost 3 months since Kudu 1.12.0 has been released on 5/19, > so I'd > > like to volunteer to RM Kudu 1.13.0. > > > > Based on previous experience, I'd like to have a window a bit longer > than usual > > to allow finishing any in-progress work that you'd like to squeeze in to > this > > release so I propose cutting the branch on 8/14 Friday. This will give > us a > > little over two weeks. > > > > In turn, I'd like to get the release notes committed before we cut the > RC1, this > > way it would actually be part of the release instead of available only > online. > > > > Please collect your significant changes for the release notes in this > document: > > https://s.apache.org/kudu1.13rn > > > > Thanks, > > Attila > > >
