What is the 'inconsistency'? Overlapped regions? Or holes between regions? Have checked the SPLIT/MERGE related logs on master?
Jean-Marc Spaggiari <[email protected]> 于2019年4月12日周五 下午9:23写道： > Same error. > > I will re-pull, re-build, re-deployed. I clean clean the table again, > sanitize everything, document all the steps and report here...What is > interesting is that I have 2 tables but only one get corrupted. > > JMS > > Le jeu. 11 avr. 2019 à 15:55, Jean-Marc Spaggiari <[email protected] > > > a écrit : > > > Ok. Let me pull the last 2.2 branch, build that, deploy and retry... I > > might be able to let you know tomorrow morning. > > > > Le jeu. 11 avr. 2019 à 14:19, Sean Busbey <[email protected]> a écrit : > > > >> Maybe worth trying out the HEAD of branch-2.2 prior to the next RC? That > >> way if you hit a blocker like your current ones we can fix them before > RC > >> generation happens. > >> > >> On Thu, Apr 11, 2019, 13:08 Jean-Marc Spaggiari < > [email protected]> > >> wrote: > >> > >> > Thanks Guanghao. > >> > > >> > I'm having consistant issues with RC0. I had some issues with a table > >> this > >> > morning. Dropped it, recreated it, made it clean, restart my > >> application, > >> > and I have again some inconsistencies on the regions. There is > something > >> > wrong somewhere. I'm not able to identify where, but I can easily get > my > >> > tables corrupted by running my client application. So I'm eager to try > >> the > >> > next RC to see if it helps. > >> > > >> > JMS > >> > > >> > JMS > >> > > >> > Le jeu. 11 avr. 2019 à 13:33, Guanghao Zhang <[email protected]> a > >> écrit > >> > : > >> > > >> > > Sorry for late... I am testing the ITBLL for 2.2.0 and it passed > >> > > yesterday. See https://issues.apache.org/jira/browse/HBASE-21886. > I > >> > will > >> > > generate RC1 later. Thanks. > >> > > > >> > > Jean-Marc Spaggiari <[email protected]> 于2019年4月11日周四 > >> 下午10:52写道： > >> > > > >> > > > Hi all, > >> > > > > >> > > > Any chance to get an updated RC soon? > >> > > > > >> > > > JM > >> > > > > >> > > > Le mar. 12 mars 2019 à 12:23, Sean Busbey <[email protected]> a > >> écrit > >> > : > >> > > > > >> > > > > quick follow-up here. the full version info is in fact missing > the > >> > > > > revision: > >> > > > > > >> > > > > hbase-2.2.0 busbey$ ./bin/hbase version > >> > > > > HBase 2.2.0 > >> > > > > Source code repository > >> > > > > git://hao-OptiPlex-7050/home/hao/open_source/hbase revision= > >> > > > > Compiled by hao on 2019年 03月 07日 星期四 14:05:34 CST > >> > > > > From source with checksum 783fee467bb1b28666f0d904437862c4 > >> > > > > > >> > > > > I think this is the issue stack ran into on > >> HBASE-21935/HBASE-21999 > >> > > > > where HBASE-20764 introduced a git cli option that issn't > >> supported > >> > on > >> > > > > older versions of git. > >> > > > > > >> > > > > Guanghao for the next RC would it be possible to update your > local > >> > git > >> > > > > version? > >> > > > > > >> > > > > On Tue, Mar 12, 2019 at 9:37 AM Sean Busbey <[email protected]> > >> > wrote: > >> > > > > > > >> > > > > > locale of the build is up to the RM (this is why, for example, > >> the > >> > > 2.1 > >> > > > > > release line javadocs have chinese for the boilerplate > text[1]) > >> > > > > > > >> > > > > > however, it does look like that shell output might be missing > >> the > >> > > > > > build revision information from git or we might not be > properly > >> > > > > > parsing the output from git when a non-english locale is used. > >> > > > > > > >> > > > > > [1]: http://hbase.apache.org/2.1/apidocs/index.html > >> > > > > > > >> > > > > > > >> > > > > > On Tue, Mar 12, 2019 at 8:54 AM Jean-Marc Spaggiari > >> > > > > > <[email protected]> wrote: > >> > > > > > > > >> > > > > > > Also, in the shell,it displays Asian texte: > >> > > > > > > > >> > > > > > > "Version 2.2.0, r, 2019年 03月 07日 星期四 14:05:34 CST" > >> > > > > > > > >> > > > > > > Not sure if that's we want. > >> > > > > > > > >> > > > > > > JMS > >> > > > > > > > >> > > > > > > Le lun. 11 mars 2019 à 21:53, Guanghao Zhang < > >> [email protected] > >> > > > >> > > a > >> > > > > écrit : > >> > > > > > > > >> > > > > > > > Let me start a new RC1. HBASE-21970 should be included and > >> > need a > >> > > > > release > >> > > > > > > > note. > >> > > > > > > > > >> > > > > > > > Sean Busbey <[email protected]> 于2019年3月12日周二 上午8:35写道： > >> > > > > > > > > >> > > > > > > > > I'm -1 on RC0 as it is. > >> > > > > > > > > > >> > > > > > > > > The current release notes don't include any call out > about > >> > the > >> > > > > upgrade > >> > > > > > > > > steps needed. Since we don't usually have minor-version > >> > > specific > >> > > > > > > > > upgrade steps and especially since there are things > folks > >> > need > >> > > to > >> > > > > do > >> > > > > > > > > before installing 2.2.0, it's important that they be > front > >> > and > >> > > > > center. > >> > > > > > > > > Possibly that should mean a link to the ref guide > section > >> > from > >> > > > the > >> > > > > RC > >> > > > > > > > > instructions and eventual announcement. > >> > > > > > > > > > >> > > > > > > > > I think either HBASE-21075 needs to have 2.2.0 included > in > >> > its > >> > > > fix > >> > > > > > > > > version or the release note from that issue needs to be > >> > copied > >> > > > > over to > >> > > > > > > > > HBASE-21970 and it needs to have 2.2.0 included in its > fix > >> > > > > version(s). > >> > > > > > > > > In either case the release notes should link to the ref > >> guide > >> > > > > section. > >> > > > > > > > > > >> > > > > > > > > On Thu, Mar 7, 2019 at 3:44 AM Guanghao Zhang < > >> > > > [email protected]> > >> > > > > > > > wrote: > >> > > > > > > > > > > >> > > > > > > > > > Please vote on this release candidate (RC) for Apache > >> HBase > >> > > > > 2.2.0. > >> > > > > > > > > > This is the first release of the branch-2.2 line. > >> > > > > > > > > > > >> > > > > > > > > > The VOTE will remain open for at least 72 hours. > >> > > > > > > > > > > >> > > > > > > > > > [ ] +1 Release this package as Apache HBase 2.2.0 > >> > > > > > > > > > [ ] -1 Do not release this package because ... > >> > > > > > > > > > > >> > > > > > > > > > The tag to be voted on is 2.2.0-RC0 (commit > >> > > > > > > > > > 4ab2dc20f15e9b59477de4bd971c367f3ce342cb): > >> > > > > > > > > > > >> > > > > > > > > > https://github.com/apache/hbase/tree/2.2.0-RC0 > >> > > > > > > > > > > >> > > > > > > > > > The release files, including signatures, digests, etc. > >> can > >> > be > >> > > > > found at: > >> > > > > > > > > > > >> > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/ > >> > > > > > > > > > > >> > > > > > > > > > Maven artifacts are available in a staging repository > >> at: > >> > > > > > > > > > > >> > > > > > > > > > > >> > > > > > >> > > https://repository.apache.org/content/repositories/orgapachehbase-1286 > >> > > > > > > > > > > >> > > > > > > > > > Signatures used for HBase RCs can be found in this > file: > >> > > > > > > > > > > >> > > > > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > >> > > > > > > > > > > >> > > > > > > > > > The list of bug fixes going into 2.2.0 can be found in > >> > > included > >> > > > > > > > > > CHANGES.md and RELEASENOTES.md available here: > >> > > > > > > > > > > >> > > > > > > > > > > >> > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/CHANGES.md > >> > > > > > > > > > > >> > > > > > >> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/RELEASENOTES.md > >> > > > > > > > > > > >> > > > > > > > > > To learn more about Apache HBase, please see > >> > > > > http://hbase.apache.org/ > >> > > > > > > > > > > >> > > > > > > > > > Thanks, > >> > > > > > > > > > Guanghao Zhang > >> > > > > > > > > > >> > > > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > >
