So.

About one hour after I started to run the tests, one of my servers crashed
(Not surprising, it was over heating) and table go corrupted. I restored it
again, and re-run everything for the last 20 hours and there isn't any
issue. I'm now re-activating the normalizer. Seems that where there is
regions re-assigned to a different server, some writes are still going in
the previous server? Don'T know yet :(

JM

Le ven. 12 avr. 2019 à 10:23, Jean-Marc Spaggiari <[email protected]>
a écrit :

> Performed those steps and got a branch new 2.2.1-SNAPSHOT running
> instance. one master, 7 workers. Disabled the splits and the normalizer.
> Will report later in the day when  (if) it fails.
>
> git clone https://github.com/apache/hbase.git hbase-2.2.1
> export JAVA_HOME=/usr/local/jdk1.8.0_151/
> mvn -DskipTests -Dhadoop-two.version=2.7.5 clean install && mvn
> -Dhadoop-two.version=2.7.5 -DskipTests package assembly:single
> for i in {1..8}; do echo node$i; scp
> hbase-assembly/target/hbase-2.2.1-SNAPSHOT-bin.tar.gz node$i:/tmp; done
> for i in {1..8}; do ssh node$i cp /home/hbase/hbase-2.2.0/conf/*
> /home/hbase/hbase-2.2.1-SNAPSHOT/conf/; done
> for i in {1..8}; do ssh node$i tar -xzf
> /tmp/hbase-2.2.1-SNAPSHOT-bin.tar.gz --directory /home/hbase; done
> copy native libs
> start HBase
>
> To restore my table:
> form shell: disable 'stones5'
> from bash hdfs dfs -mv /hbase/data/default/stones5/*/A/* /temp/A/
> from shell:  enable 'stones5'; truncate 'stones5'; disable 'stones5'
> from bash: hdfs dfs -ls /hbase/data/default/stones5/ (Capture region name)
> from bash: hdfs dfs -mv /temp/A/*
> /hbase/data/default/stones5/12546c6eac93c2c9caccddf57e1c020b/A
> from shell: enable 'stones5'
> from shell: major_compact 'stones5'
> Changed the split policy to avoid splitting, disabled normalizer.
>
> Validate that there is just a single store file in the region, validate
> HBCK:
> 0 inconsistencies detected.
> Status: OK
>
> Table ok in UI.
> Splitting the tables few times (split, balancer,  compact, janitor,
> repeat). Got 16 regions, HBCK still ok.
>
> Restarting client application.
>
> Le ven. 12 avr. 2019 à 09:43, Jean-Marc Spaggiari <[email protected]>
> a écrit :
>
>> Overlaps:
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x00\x00\x00\x01\x04\x00\x01\x02\x03\x00\x00\x00\x03\x02\x03\x00\x02\x00\x02,1555035157984.1b1493533a4140732b5a3cfc3da52176.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x00\x00\x00\x03\x02\x01\x02\x05\x02\x05\x02\x03\x01\x01\x01\x01\x01\x00\x02,1555046849488.ba3c45f7bb5c9134ba78f35e4454e79f.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x00\x01\x01\x01\x01\x00\x00\x00\x03\x01\x03\x00\x02\x01\x01\x02\x00\x00\x02,1555030949303.446399be95af2396c0ed5dfe705a90dc.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x00\x01\x03\x02\x05\x00\x02\x01\x00\x01\x00\x01\x05\x02\x01\x01\x00\x00\x01\x01,1555031867671.2ecb6a00a4c3df38b9e6e02546e8f09a.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x00\x02\x01\x03\x00\x01\x03\x01\x03\x05\x00\x04\x00\x00\x00\x01,1555031584820.76cbd1d32c6874f522061a8c20cbb792.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x01\x00\x00\x03\x01\x00\x04\x02\x03\x03\x00\x04\x00\x03\x04\x00\x01,1555027357980.3792e707669986039cefda8781c31cdf.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x01\x01\x03\x03\x00\x00\x00\x00\x01\x01\x02\x02\x01\x00\x04\x00\x00\x00\x02,1555027357980.26ab4bfd50ca39a82227f03254a13ea0.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x01\x02\x00\x01\x01\x00\x00\x00\x02\x03\x01\x01\x01\x01\x01\x01\x02,1555054349272.c220877e57ecadf55925a3c927b62e12.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x01\x03\x01\x01\x02\x02\x01\x04\x04\x01\x00\x02\x01\x02\x04\x00\x02\x02\x00\x01,1555031249434.e919ba9eafac6f1ac9a42fcd3cbd9bc5.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x02\x00\x02\x02\x01\x03\x00\x00\x03\x02\x03\x03\x00\x01\x03\x02\x02,1555041449331.d8d72f9649d8c347cd0daefd42fb478f.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x00\x02\x03\x02\x00\x00\x01\x05\x00\x03\x02\x03\x01\x00\x02\x01\x02\x02,1555037257863.2eb4c29b2b87ce9bca3c9e850b378894.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x00\x01\x01\x00\x04\x00\x01\x06\x02\x05\x02\x05\x03\x02\x01\x00\x01,1555027668004.9372857902cba5ed444c82c295588ba6.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x00\x02\x00\x04\x00\x02\x00\x03\x00\x01\x03\x02\x00\x02\x02\x01\x02\x01,1555031849317.e14a6990fda17f481a38165c94402ed9.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x00\x02\x03\x01\x00\x06\x02\x04\x03\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F,1555035158241.25c9071f60b9fa08d34b8c082ebf97f0.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x01\x01\x02\x00\x02\x01\x00\x01\x02\x02\x00\x03\x03\x01\x02\x01\x00\x02,1555034849250.ace3d152adcd28082cdea81304402d8f.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x01\x01\x03\x03\x00\x00\x01\x03\x02\x04\x02\x03\x02\x02\x01,1555017598461.9c80f37a9b14dff0c0784a178d1b7ed0.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x01\x03\x02\x03\x05\x01\x00\x00\x04\x01\x00\x01\x03\x02\x04\x01\x00\x01\x01,1555031549353.91cde474448c193ae224c25961a1d9c7.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x02\x01\x00\x03\x00\x03\x01\x02\x02\x00\x00\x00\x00\x01\x01\x02\x02,1555031549353.c5e045c0ba1bff8ebc018afb9517d34b.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x02\x02\x01\x00\x00\x02\x00\x04\x00\x01\x00\x01\x02\x03\x02\x02\x02,1555031585927.0b03eb31bc027c3e5cc89015f04de7f9.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x01\x02\x03\x02\x02\x01\x01\x01\x02\x02\x03\x02\x02\x02\x02\x00\x01,1555037249380.3e2f508fb15d3a5bbbdace7bdf367a23.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x00\x04\x04\x01\x03\x00\x01\x00\x00\x01\x01\x00\x00\x01\x01,1555037249380.4d091aac5af4f6428c29890b16e52757.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x01\x00\x00\x01\x00\x01\x03\x00\x03\x04\x03\x00\x02\x03\x01\x00\x00\x00\x01,1555027649323.6ac99e4c0b1c88e5c8a45f0fb91b8310.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x02\x00\x02\x02\x00\x00\x04\x01\x03\x00\x02\x03\x01,1555060350354.a869499d008b869d0537111eb86eba4b.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x03\x00\x02\x00\x02\x01\x04\x01\x01\x00\x00\x01\x03\x00\x01\x00\x00\x01,1555023498688.2cf666c41559252ecb9dde88a9ef8f96.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x03\x02\x03\x01\x02\x02\x03\x00\x05\x01\x02\x01\x01\x00\x03\x00\x02,1555028249271.937ac47e0691a36ecd9b921342da70c4.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x00\x04\x03\x04\x06\x04\x03\x04\x03\x04\x00\x04\x01\x00\x01\x04\x01\x02,1555028249271.a378c6c6cf28101dc107aa54ca74675c.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x01\x01\x00\x02\x00\x03\x00\x02\x03\x01\x06\x00\x03\x01\x02\x00\x01,1555023490409.1f2f2c0a0120b172cda6a041ce3af5a5.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x01\x02\x00\x01\x00\x03\x00\x03\x00\x02\x01\x02\x02\x01\x00\x01\x01\x01,1555053749269.66f81f20b77f75e10d1656bb574fc764.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x01\x02\x01\x03\x00\x02\x00\x05\x01\x00\x03\x04\x02\x03\x00\x00\x00\x01,1555053749269.a3ed0c36c0d64abbaf2bcba1fb562d45.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x01\x03\x00\x01\x02\x01\x06\x00\x01\x00\x00\x02\x01\x01\x00\x03,1555035149255.84bb950c9310f9d6cc938e8227519379.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x02\x00\x04\x00\x00\x00\x02\x04\x01\x00\x02\x02\x03\x00\x00\x01\x01\x01,1555028849272.1999405b98a58fadf646d3ced3337c4e.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x02\x01\x04\x01\x01\x02\x04\x01\x03\x03\x05\x00\x03\x02\x00\x01\x01,1555029449377.f8108ca9d5783308628bd4dd9719c0d4.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x02\x02\x01\x03\x01\x01\x01\x03\x00\x00\x00\x00\x00\x02\x01\x03\x00\x01,1555036058052.eb718757f76ddb2ee5ec6518401f9da7.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x02\x02\x03\x03\x03\x04\x01\x00\x02\x01\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F,1555035749414.f66097b314af9d847eeeb07efeeca3d6.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x00\x01\x01\x05\x02\x04\x04\x03\x01\x01\x02\x00\x03\x03\x01\x01\x01,1555049849371.b5a3eaa74a323b3e367d010dc60a9e3e.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x00\x02\x00\x03\x00\x00\x01\x04\x01\x05\x02\x01\x02\x02\x03\x00\x01,1555036349746.0def87ba07cc522683f0fa9291442d78.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x00\x04\x00\x03\x01\x01\x03\x02\x02\x05\x02\x03\x01\x00\x00\x04\x01\x02\x01\x01,1555027349298.906bb886571b27522cfda99d34898ed9.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x01\x00\x04\x00\x01\x03\x01\x04\x02\x01\x02\x06\x00\x06\x00\x01\x00\x02,1555027349298.9905bd5a10714e7e669568aaa5e317f6.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x01\x02\x01\x02\x01\x04\x02\x02\x05\x01\x02\x00\x01\x00\x04\x00\x00\x01,1555023165925.f0f60e6d298cbca9fb06ea59d8de03eb.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x01\x03\x01\x01\x02\x02\x02\x01\x00\x01\x02\x02\x00\x01\x01\x04\x01\x00\x00\x01,1555027366401.8b5b5fea4c95b7bb9e95b99360425d81.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x01\x03\x02\x02\x00\x00\x02\x05\x02\x00\x01\x00\x02\x02\x02,1555034249345.373ef8d16692e7e39ebb81787f138b0f.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x02\x00\x01\x00\x02\x03\x01\x02\x00\x01\x04\x03\x02\x00\x00\x00\x02,1555034249345.cf6fbfdbbb541ca22dfb1de337b3eb42.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x02\x01\x01\x01\x04\x01\x03\x03\x02\x00\x03\x00\x04\x03\x01\x01,1555030049511.d260897d0c8c5d156edc7c3ef220fd9c.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x02\x02\x00\x04\x05\x07\x04\x04\x02\x03\x01\x02\x01\x04\x02\x02,1555023149297.1ecd9a495183397ea8cce6e34805e0b8.)
>> There is an overlap in the region chain.
>> ERROR: (regions stones5,,1555031586547.96b7f40ded8459db044cdb447d9a12c8.
>> and
>> stones5,\x03\x02\x02\x01\x01\x03\x05\x01\x00\x01\x03\x02\x00\x02\x01\x02,1555030349356.b04b4fd705b3c348c58a91b1670d4fee.)
>> There is an overlap in the region chain.
>>
>>
>> I'm re-building the environment. I will start with a brand new clean
>> directory and will check the logs. The normalizer is running and split some
>> regions.
>> 2019-04-12 05:07:29,256 INFO  [master/node2:60000.Chore.2]
>> normalizer.SimpleRegionNormalizer: Table stones5, large region
>> stones5,\x02\x00\x02\x00\x02\x02\x00\x00\x04\x01\x03\x00\x02\x03\x01,1555054054003.aa5fbcf8a100aee7f784c4e32bcdbc0f.
>> has size 9, more than twice avg size, splitting
>>
>> 2019-04-12 05:12:30,332 INFO  [master/node2:60000.Chore.1]
>> normalizer.MergeNormalizationPlan: Executing merging normalization plan:
>> MergeNormalizationPlan{firstRegion={ENCODED =>
>> 3d498e6d2748d9ef7cd1a477f1334a1c, NAME =>
>> 'stones5,\x02\x00\x02\x00\x02\x02\x00\x00\x04\x01\x03\x00\x02\x03\x01,1555060049267.3d498e6d2748d9ef7cd1a477f1334a1c.',
>> STARTKEY => '\x02\x00\x02\x00\x02\x02\x00\x00\x04\x01\x03\x00\x02\x03\x01',
>> ENDKEY =>
>> '\x02\x00\x02\x01\x01\x02\x06\x01\x06\x04\x01\x04\x04\x03\x01\x02\x00\x01'},
>> secondRegion={ENCODED => 8c3e3d8542b405546a8f076fa4311172, NAME =>
>> 'stones5,\x02\x00\x02\x01\x01\x02\x06\x01\x06\x04\x01\x04\x04\x03\x01\x02\x00\x01,1555060049267.8c3e3d8542b405546a8f076fa4311172.',
>> STARTKEY =>
>> '\x02\x00\x02\x01\x01\x02\x06\x01\x06\x04\x01\x04\x04\x03\x01\x02\x00\x01',
>> ENDKEY =>
>> '\x02\x00\x03\x00\x02\x00\x02\x01\x04\x01\x01\x00\x00\x01\x03\x00\x01\x00\x00\x01'}}
>>
>>
>> I will try running with and without. But I suspect that splits/merges are
>> having issues... It seems that all error are related to the first region.
>>
>> JMS
>>
>> Le ven. 12 avr. 2019 à 09:29, 张铎(Duo Zhang) <[email protected]> a
>> écrit :
>>
>>> 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
>>> > >> > > > > > > > >
>>> > >> > > > > > > >
>>> > >> > > > >
>>> > >> > > >
>>> > >> > >
>>> > >> >
>>> > >>
>>> > >
>>> >
>>>
>>

Reply via email to