I agree that while the perf issues are important they should not hold up moving the stable pointer from one minor version to another when both would benefit from the changes.
How smooth is the upgrade process from 2.2.x to 2.3.x? The upgrade section for it in the ref guide[1] suggests it should smoothly "just work"? How confident are we about that in the face of failures? [1]: http://hbase.apache.org/book.html#upgrade2.3 On Tue, Sep 1, 2020 at 3:09 AM 张铎(Duo Zhang) <[email protected]> wrote: > But there is no difference betwee 2.2.x and 2.3.x? The stable pointer is > already on 2.2.x now. > > Pankaj kr <[email protected]> 于2020年9月1日周二 上午11:58写道： > > > We have observed performance degrade in Scan and Bulk load as compared to > > 1.x, there are couple of JIRAs already in-progress to handle them > > HBASE-24754, HBASE-24637 & HBASE-24850. > > IMO we should move stable pointer after fixing these important issues. > > > > Regards, > > Pankaj > > > > -----Original Message----- > > From: Viraj Jasani [mailto:[email protected]] > > Sent: Tuesday, September 1, 2020 12:12 AM > > To: [email protected] > > Subject: [DISCUSS] Move stable pointer to the latest 2.3.x release > > > > Hello everyone, > > > > While voting for 2.2.6 RC0, we had a short discussion reg moving stable > > pointer to the latest 2.3.x and the decision was to initiate the discuss > > thread when 2.3.1 and 2.2.6 are out. > > > > Since 2.3.1 is already out and our RM is busy with 2.2.6 release process, > > I am initiating this thread to discuss the same. > > > > Would you all like to consider moving stable release pointer to 2.3.x > > release line? > > Given the stabilization efforts and some latest features available with > > stable tests, I am +1 for the same. > > > > >
