Re: [ANNOUNCE] New HBase committer Istvan Toth
Congratulations Istvan, welcome !! On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that > Istvan Toth(stoty) > has accepted the PMC's invitation to become a committer on the > project. We appreciate all > of Istvan Toth's generous contributions thus far and look forward to > his continued involvement. > > Congratulations and welcome, Istvan Toth! > > 我很高兴代表 Apache HBase PMC 宣布 Istvan Toth 已接受我们的邀请，成 > 为 Apache HBase 项目的 Committer。感谢 Istvan Toth 一直以来为 HBase 项目 > 做出的贡献，并期待他在未来继续承担更多的责任。 > > 欢迎 Istvan Toth！ >
Re: [ANNOUNCE] New HBase committer Istvan Toth
Congratulations Istvan, welcome !! On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that > Istvan Toth(stoty) > has accepted the PMC's invitation to become a committer on the > project. We appreciate all > of Istvan Toth's generous contributions thus far and look forward to > his continued involvement. > > Congratulations and welcome, Istvan Toth! > > 我很高兴代表 Apache HBase PMC 宣布 Istvan Toth 已接受我们的邀请，成 > 为 Apache HBase 项目的 Committer。感谢 Istvan Toth 一直以来为 HBase 项目 > 做出的贡献，并期待他在未来继续承担更多的责任。 > > 欢迎 Istvan Toth！ >
Re: [ANNOUNCE] Please welcome Bryan Beaudreault to the HBase PMC
Congratulations Bryan !! Very well deserved for all the hard work you put in the HBase project ! On Mon, Oct 16, 2023 at 6:32 PM Duo Zhang wrote: > On behalf of the Apache HBase PMC I am pleased to announce that > Bryan Beaudreault has accepted our invitation to become a PMC member > on the Apache HBase project. We appreciate Bryan Beaudreault > stepping up to take more responsibility in the HBase project. > > Please join me in welcoming Bryan Beaudreault to the HBase PMC! > > 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请， > 成为 Apache HBase 项目的 PMC 成员。感谢 Bryan Beaudreault 愿意在 HBase > 项目中承担更大的责任。 > > 欢迎 Bryan Beaudreault！ >
Re: [ANNOUNCE] Please welcome Bryan Beaudreault to the HBase PMC
Congratulations Bryan !! Very well deserved for all the hard work you put in the HBase project ! On Mon, Oct 16, 2023 at 6:32 PM Duo Zhang wrote: > On behalf of the Apache HBase PMC I am pleased to announce that > Bryan Beaudreault has accepted our invitation to become a PMC member > on the Apache HBase project. We appreciate Bryan Beaudreault > stepping up to take more responsibility in the HBase project. > > Please join me in welcoming Bryan Beaudreault to the HBase PMC! > > 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请， > 成为 Apache HBase 项目的 PMC 成员。感谢 Bryan Beaudreault 愿意在 HBase > 项目中承担更大的责任。 > > 欢迎 Bryan Beaudreault！ >
Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)
Congratulations Hui Ruan !! On Fri, Sep 15, 2023 at 2:08 AM 张铎(Duo Zhang) wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that Hui > Ruan(frostruan) > has accepted the PMC's invitation to become a committer on the > project. We appreciate all > of Hui's generous contributions thus far and look forward to his > continued involvement. > > Congratulations and welcome, Hui Ruan! > > 我很高兴代表 Apache HBase PMC 宣布阮辉已接受我们的邀请，成 > 为 Apache HBase 项目的 Committer。感谢阮辉一直以来为 HBase 项目 > 做出的贡献，并期待他在未来继续承担更多的责任。 > > 欢迎阮辉！ >
Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)
Congratulations Hui Ruan !! On Fri, Sep 15, 2023 at 2:08 AM 张铎(Duo Zhang) wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that Hui > Ruan(frostruan) > has accepted the PMC's invitation to become a committer on the > project. We appreciate all > of Hui's generous contributions thus far and look forward to his > continued involvement. > > Congratulations and welcome, Hui Ruan! > > 我很高兴代表 Apache HBase PMC 宣布阮辉已接受我们的邀请，成 > 为 Apache HBase 项目的 Committer。感谢阮辉一直以来为 HBase 项目 > 做出的贡献，并期待他在未来继续承担更多的责任。 > > 欢迎阮辉！ >
Re: [ANNOUNCE] New HBase committer Nihal Jain
Congratulations Nihal !!! On Wed, May 3, 2023 at 7:28 AM Tak Lon (Stephen) Wu wrote: > Congratulations and well-deserved! > > -Stephen > > On Wed, May 3, 2023 at 5:45 AM Wei-Chiu Chuang wrote: > > > Congrats! > > > > On Wed, May 3, 2023 at 5:42 AM rajeshb...@apache.org < > > chrajeshbab...@gmail.com> wrote: > > > > > Congratulations Nihal!!! > > > > > > > > > Thanks, > > > Rajeshbabu. > > > > > > On Wed, May 3, 2023, 5:42 PM Nick Dimiduk wrote: > > > > > > > Hello! > > > > > > > > On behalf of the Apache HBase PMC, I am pleased to announce that > Nihal > > > Jain > > > > has accepted the PMC's invitation to become a committer on the > project. > > > We > > > > appreciate all of Nihal's generous contributions thus far and look > > > forward > > > > to his continued involvement. > > > > > > > > Congratulations and welcome, Nihal Jain! > > > > > > > > Thanks, > > > > Nick > > > > > > > > > >
Re: [ANNOUNCE] New HBase committer Nihal Jain
Congratulations Nihal !!! On Wed, May 3, 2023 at 7:28 AM Tak Lon (Stephen) Wu wrote: > Congratulations and well-deserved! > > -Stephen > > On Wed, May 3, 2023 at 5:45 AM Wei-Chiu Chuang wrote: > > > Congrats! > > > > On Wed, May 3, 2023 at 5:42 AM rajeshb...@apache.org < > > chrajeshbab...@gmail.com> wrote: > > > > > Congratulations Nihal!!! > > > > > > > > > Thanks, > > > Rajeshbabu. > > > > > > On Wed, May 3, 2023, 5:42 PM Nick Dimiduk wrote: > > > > > > > Hello! > > > > > > > > On behalf of the Apache HBase PMC, I am pleased to announce that > Nihal > > > Jain > > > > has accepted the PMC's invitation to become a committer on the > project. > > > We > > > > appreciate all of Nihal's generous contributions thus far and look > > > forward > > > > to his continued involvement. > > > > > > > > Congratulations and welcome, Nihal Jain! > > > > > > > > Thanks, > > > > Nick > > > > > > > > > >
Re: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the HBase PMC
Congratulations Stephen ! On Mon, Jan 30, 2023 at 10:54 PM Tak Lon (Stephen) Wu wrote: > Thank you everyone ! So happy to be here and will continue to interact > with you guys. > > -Stephen > > On Mon, Jan 30, 2023 at 9:06 PM rajeshb...@apache.org > wrote: > > > > Congratulations Stephen. > > > > > > Thanks, > > Rajeshbabu. > > > > On Mon, Jan 30, 2023, 7:33 PM Bryan Beaudreault > > wrote: > > > > > Congrats! > > > > > > On Mon, Jan 30, 2023 at 4:10 AM Balazs Meszaros > > > wrote: > > > > > > > Congratulations! > > > > > > > > On Mon, Jan 30, 2023 at 9:19 AM Jan Hentschel > > > > wrote: > > > > > > > > > Congratulations and welcome! > > > > > > > > > > From: Duo Zhang > > > > > Date: Monday, January 30, 2023 at 3:50 AM > > > > > To: HBase Dev List , hbase-user < > > > > > u...@hbase.apache.org>, user-zh > > > > > Subject: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the > HBase > > > PMC > > > > > On behalf of the Apache HBase PMC I am pleased to announce that > > > > > Tak Lon (Stephen) Wu has accepted our invitation to become a PMC > member > > > > > on the Apache HBase project. We appreciate Tak Lon (Stephen) Wu > > > stepping > > > > > up to take more responsibility in the HBase project. > > > > > > > > > > Please join me in welcoming Tak Lon (Stephen) Wu to the HBase PMC! > > > > > > > > > > 我很高兴代表 Apache HBase PMC 宣布 Tak Lon (Stephen) Wu 已接受我们的邀请， > > > > > 成为 Apache HBase 项目的 PMC 成员。感谢 Tak Lon (Stephen) Wu 愿意在 HBase > > > > > 项目中承担更大的责任。 > > > > > > > > > > 欢迎 Tak Lon (Stephen) Wu！ > > > > > > > > > > > > >
Re: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the HBase PMC
Congratulations Stephen ! On Mon, Jan 30, 2023 at 10:54 PM Tak Lon (Stephen) Wu wrote: > Thank you everyone ! So happy to be here and will continue to interact > with you guys. > > -Stephen > > On Mon, Jan 30, 2023 at 9:06 PM rajeshb...@apache.org > wrote: > > > > Congratulations Stephen. > > > > > > Thanks, > > Rajeshbabu. > > > > On Mon, Jan 30, 2023, 7:33 PM Bryan Beaudreault > > wrote: > > > > > Congrats! > > > > > > On Mon, Jan 30, 2023 at 4:10 AM Balazs Meszaros > > > wrote: > > > > > > > Congratulations! > > > > > > > > On Mon, Jan 30, 2023 at 9:19 AM Jan Hentschel > > > > wrote: > > > > > > > > > Congratulations and welcome! > > > > > > > > > > From: Duo Zhang > > > > > Date: Monday, January 30, 2023 at 3:50 AM > > > > > To: HBase Dev List , hbase-user < > > > > > user@hbase.apache.org>, user-zh > > > > > Subject: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the > HBase > > > PMC > > > > > On behalf of the Apache HBase PMC I am pleased to announce that > > > > > Tak Lon (Stephen) Wu has accepted our invitation to become a PMC > member > > > > > on the Apache HBase project. We appreciate Tak Lon (Stephen) Wu > > > stepping > > > > > up to take more responsibility in the HBase project. > > > > > > > > > > Please join me in welcoming Tak Lon (Stephen) Wu to the HBase PMC! > > > > > > > > > > 我很高兴代表 Apache HBase PMC 宣布 Tak Lon (Stephen) Wu 已接受我们的邀请， > > > > > 成为 Apache HBase 项目的 PMC 成员。感谢 Tak Lon (Stephen) Wu 愿意在 HBase > > > > > 项目中承担更大的责任。 > > > > > > > > > > 欢迎 Tak Lon (Stephen) Wu！ > > > > > > > > > > > > >
Re: [ANNOUNCE] New HBase committer Rushabh Shah
Thank you everyone for the warm welcome and all the help you have provided along the way ! On Fri, Dec 16, 2022 at 12:54 AM Xiaolin Ha wrote: > Congratulations and welcome! > > 张铎(Duo Zhang) 于2022年12月15日周四 14:57写道： > > > On behalf of the Apache HBase PMC, I am pleased to announce that > > Rushabh Shah(shahrs87) > > has accepted the PMC's invitation to become a committer on the > > project. We appreciate all > > of Rushabh's generous contributions thus far and look forward to his > > continued involvement. > > > > Congratulations and welcome, Rushabh Shah! > > > > 我很高兴代表 Apache HBase PMC 宣布 Rushabh Shah 已接受我们的邀请，成 > > 为 Apache HBase 项目的 Committer。感谢 Rushabh Shah 一直以来为 HBase 项目 > > 做出的贡献，并期待他在未来继续承担更多的责任。 > > > > 欢迎 Rushabh Shah！ > > >
Re: [ANNOUNCE] New HBase PMC Bharath Vissapragada
Congratulations Bharath !! Rushabh Shah On Fri, Jul 30, 2021 at 9:26 AM Viraj Jasani wrote: > On behalf of the Apache HBase PMC I am pleased to announce that Bharath > Vissapragada has accepted our invitation to become a PMC member on the > HBase project. We appreciate Bharath stepping up to take more > responsibility for the project. > > Congratulations and welcome, Bharath! >
Re: ZK replication node grows exponentially though datas properly replication for peers
Hi Roshan, Are you seeing any replication related exception in your RS logs ? On Tue, Apr 27, 2021 at 1:59 PM Roshan wrote: > Hi, > > In the hbase-1.4.10, I have enabled replication for all tables and > configured the peer_id. the list_peers provide the below result: > > hbase(main):001:0> list_peers > > PEER_ID CLUSTER_KEY ENDPOINT_CLASSNAME STATE TABLE_CFS BANDWIDTH > > 1 10.XX.221.XX,10.XX.234.XX,10.XX.212.XX:2171:/hbase nil ENABLED nil 0 > > 1 row(s) in 0.1430 seconds > > > But the status_replication shows replication lag > > hbase(main):002:0> status 'replication' > > version 1.4.10 > > 3 live servers > > 10.XX.232.XX: > >SOURCE: PeerID=1, AgeOfLastShippedOp=0, SizeOfLogQueue=1, > > TimeStampsOfLastShippedOp=Thu Jan 01 05:30:00 IST 1970, Replication Lag= > > *1619545264329* > >SINK : AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Tue Apr 27 > > 23:09:23 IST 2021 > > 10.XX.118.XX: > >SOURCE: PeerID=1, AgeOfLastShippedOp=0, SizeOfLogQueue=1, > > TimeStampsOfLastShippedOp=Thu Jan 01 05:30:00 IST 1970, Replication Lag= > > *1619545264663* > >SINK : AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Tue Apr 27 > > 18:53:23 IST 2021 > > 10.XX.138.XX: > >SOURCE: PeerID=1, AgeOfLastShippedOp=0, SizeOfLogQueue=1, > > TimeStampsOfLastShippedOp=Thu Jan 01 05:30:00 IST 1970, Replication Lag= > > *1619545263509* > >SINK : AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Tue Apr 27 > > 10:31:05 IST 2021 > > > > But all the data are replicated properly to the defined cluster. I have > checked the table in both clusters. > > I have verified using VerifyReplication Mapreduce to check unreplicated > rows. But there are no rows in the unreplicated one. All are good Rows. > > ./hbase org.apache.hadoop.hbase.mapreduce.replication.VerifyReplication 1 > > tablename > > > > org.apache.hadoop.hbase.mapreduce.replication.VerifyReplication$Verifier$Counters > > GOODROWS=45 > > File Input Format Counters > > Bytes Read=0 > > File Output Format Counters > > Bytes Written=0 > > > Due to this issue, I have Zknodes under replication is growing > exponentially which causes issues in running ZK cluster which eventually > affects the Hbase Connection too. Below exception occurs in ZK > > *ERROR java.io.IOException: Len error* > > Increasing jute.maxbuffer in ZK will not solve the problem as replication > znode is increasing though the data are replicated properly to the given > cluster Peer_id. > > I have enabled two-way replication between the cluster. It happens in both > the cluster. > > hbase version - 1.4.10 > ZK Version - 3.4.10 > Hadoop version - 2.7.3 > > Please help to fix this. > > Regards, > Roshan >
Re: [ANNOUNCE] New HBase committer Geoffrey Jacoby
Congratulations Geoffrey ! Rushabh Shah - Software Engineering LMTS | Salesforce - - Mobile: 213 422 9052 On Fri, Apr 9, 2021 at 4:24 AM Viraj Jasani wrote: > On behalf of the Apache HBase PMC I am pleased to announce that Geoffrey > Jacoby has accepted the PMC's invitation to become a committer on the > project. > > Thanks so much for the work you've been contributing. We look forward to > your continued involvement. > > Congratulations and welcome, Geoffrey! >
Re: [DISCUSS] Removing problematic terms from our project
+1 to renaming. Rushabh Shah - Software Engineering SMTS | Salesforce - - Mobile: 213 422 9052 On Mon, Jun 22, 2020 at 1:18 PM Josh Elser wrote: > +1 > > On 6/22/20 4:03 PM, Sean Busbey wrote: > > We should change our use of these terms. We can be equally or more clear > in > > what we are trying to convey where they are present. > > > > That they have been used historically is only useful if the advantage we > > gain from using them through that shared context outweighs the potential > > friction they add. They make me personally less enthusiastic about > > contributing. That's enough friction for me to advocate removing them. > > > > AFAICT reworking our replication stuff in terms of "active" and "passive" > > clusters did not result in a big spike of folks asking new questions > about > > where authority for state was. > > > > On Mon, Jun 22, 2020, 13:39 Andrew Purtell wrote: > > > >> In response to renewed attention at the Foundation toward addressing > >> culturally problematic language and terms often used in technical > >> documentation and discussion, several projects have begun discussions, > or > >> made proposals, or started work along these lines. > >> > >> The HBase PMC began its own discussion on private@ on June 9, 2020 > with an > >> observation of this activity and this suggestion: > >> > >> There is a renewed push back against classic technology industry terms > that > >> have negative modern connotations. > >> > >> In the case of HBase, the following substitutions might be proposed: > >> > >> - Coordinator instead of master > >> > >> - Worker instead of slave > >> > >> Recommendations for these additional substitutions also come up in this > >> type of discussion: > >> > >> - Accept list instead of white list > >> > >> - Deny list instead of black list > >> > >> Unfortunately we have Master all over our code base, baked into various > >> APIs and configuration variable names, so for us the necessary changes > >> amount to a new major release and deprecation cycle. It could well be > worth > >> it in the long run. We exist only as long as we draw a willing and > >> sufficient contributor community. It also wouldn’t be great to have an > >> activist fork appear somewhere, even if unlikely to be successful. > >> > >> Relevant JIRAs are: > >> > >> - HBASE-12677 <https://issues.apache.org/jira/browse/HBASE-12677>: > >> Update replication docs to clarify terminology > >> - HBASE-13852 <https://issues.apache.org/jira/browse/HBASE-13852>: > >> Replace master-slave terminology in book, site, and javadoc with a > more > >> modern vocabulary > >> - HBASE-24576 <https://issues.apache.org/jira/browse/HBASE-24576>: > >> Changing "whitelist" and "blacklist" in our docs and project > >> > >> In response to this proposal, a member of the PMC asked if the term > >> 'master' used by itself would be fine, because we only have use of > 'slave' > >> in replication documentation and that is easily addressed. In response > to > >> this question, others on the PMC suggested that even if only 'master' is > >> used, in this context it is still a problem. > >> > >> For folks who are surprised or lacking context on the details of this > >> discussion, one PMC member offered a link to this draft RFC as > background: > >> https://tools.ietf.org/id/draft-knodel-terminology-00.html > >> > >> There was general support for removing the term "master" / "hmaster" > from > >> our code base and using the terms "coordinator" or "leader" instead. In > the > >> context of replication, "worker" makes less sense and perhaps > "destination" > >> or "follower" would be more appropriate terms. > >> > >> One PMC member's thoughts on language and non-native English speakers is > >> worth including in its entirety: > >> > >> While words like blacklist/whitelist/slave clearly have those negative > >> references, word master might not have the same impact for non native > >> English speakers like myself where the literal translation to my mother > >> tongue does not have this same bad connotation. Replacing all references > >> for word *master *on our docs/codebase
Re: Coprocessor restart after region split rollback
Looks like we need to open a ticket in hbase to fix this at hbase layer. Rushabh Shah - Software Engineering SMTS | Salesforce - - Mobile: 213 422 9052 On Fri, Nov 1, 2019 at 1:32 PM Stack wrote: > On Fri, Oct 25, 2019 at 12:40 AM Ondrej Kvasnicka > wrote: > > > Hi all, > > > > we are seeing the following behavior in our HBase (version 1.1) and are > > not sure whether it is an intended behavior or possibly a bug: > > > > We have a custom coprocessor loaded (RegionObserver implementation) and > > see that whenever a region split takes place, prior to the split the > > coprocessor is stopped automatically (this is expected). > > > > However, occasionally the region split will fail and will be rolled > > back. After a successful rollback, the coprocessor will _not_ be > > restarted for the region, even though it _was_ running prior to the split > > attempt. > > > > Can someone confirm that this is an intended behavior? We would expect > > the coprocessor to be automatically re-started after successful region > > split rollback, but it does not seem to be the case. > > > > > Sounds like a bug to me or more like an oversight in the split rollback > code; we probably forgot to re-enable any CPs. > > > > Are coprocessors supposed to handle the restart themselves after a > > region split rollback, e.g. in RegionObserver#postRollbackSplit, such as > > in the following example?: > > > > > > > https://github.com/splicemachine/spliceengine/blob/master/hbase_pipeline/src/main/java/com/splicemachine/derby/hbase/SpliceIndexObserver.java#L206 > > > > > Looks like they ran into your problem (smile) and this was their > workaround. > > Any chance of upgrading? 1.1. is pretty old by now. > > Thanks, > S > > > > Thanks, > > Ondrej > > >
Re: Region-server crash: Added a key not lexically larger than previous
Hi Alexander, This is not the right forum to report a bug. Please open a jira in HBASE <https://issues.apache.org/jira/projects/HBASE/> project with relevant stack traces. Rushabh Shah - Software Engineering SMTS | Salesforce - - Mobile: 213 422 9052 On Thu, Aug 15, 2019 at 8:57 AM Alexander Batyrshin <0x62...@gmail.com> wrote: > > Hello all, > > We observer error "Added a key not lexically larger than previous” that > cause most of our region-servers to crash in our cluster. > HBase-1.4.10 > > 2019-08-15 18:02:10,554 INFO [MemStoreFlusher.0] regionserver.HRegion: > Flushing 1/1 column families, memstore=56.08 MB > 2019-08-15 18:02:10,727 WARN [MemStoreFlusher.0] regionserver.HStore: > Failed flushing store file, retrying num=0 > java.io.IOException: Added a key not lexically larger than previous. > Current cell = > \x0901820448218>wGavb'/d:elr/1565881054828/DeleteColumn/vlen=0/seqid=44456567, > lastCell = > \x0901820448218>wGavb'/d:elr/1565881054828/Put/vlen=1/seqid=44457770 > at org.apache.hadoop.hbase.io > .hfile.AbstractHFileWriter.checkKey(AbstractHFileWriter.java:204) > at org.apache.hadoop.hbase.io > .hfile.HFileWriterV2.append(HFileWriterV2.java:279) > at org.apache.hadoop.hbase.io > .hfile.HFileWriterV3.append(HFileWriterV3.java:87) > at > org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:1127) > at > org.apache.hadoop.hbase.regionserver.StoreFlusher.performFlush(StoreFlusher.java:139) > at > org.apache.hadoop.hbase.regionserver.DefaultStoreFlusher.flushSnapshot(DefaultStoreFlusher.java:75) > at > org.apache.hadoop.hbase.regionserver.HStore.flushCache(HStore.java:1003) > at > org.apache.hadoop.hbase.regionserver.HStore$StoreFlusherImpl.flushCache(HStore.java:2523) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2622) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2352) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2314) > at > org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2200) > at > org.apache.hadoop.hbase.regionserver.HRegion.flush(HRegion.java:2125) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:512) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:482) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$900(MemStoreFlusher.java:76) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:264) > at java.lang.Thread.run(Thread.java:748) > > 2019-08-15 18:02:21,776 WARN [MemStoreFlusher.0] regionserver.HStore: > Failed flushing store file, retrying num=9 > java.io.IOException: Added a key not lexically larger than previous. > Current cell = > \x0901820448218>wGavb'/d:elr/1565881054828/DeleteColumn/vlen=0/seqid=44456567, > lastCell = > \x0901820448218>wGavb'/d:elr/1565881054828/Put/vlen=1/seqid=44457770 > at org.apache.hadoop.hbase.io > .hfile.AbstractHFileWriter.checkKey(AbstractHFileWriter.java:204) > at org.apache.hadoop.hbase.io > .hfile.HFileWriterV2.append(HFileWriterV2.java:279) > at org.apache.hadoop.hbase.io > .hfile.HFileWriterV3.append(HFileWriterV3.java:87) > at > org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:1127) > at > org.apache.hadoop.hbase.regionserver.StoreFlusher.performFlush(StoreFlusher.java:139) > at > org.apache.hadoop.hbase.regionserver.DefaultStoreFlusher.flushSnapshot(DefaultStoreFlusher.java:75) > at > org.apache.hadoop.hbase.regionserver.HStore.flushCache(HStore.java:1003) > at > org.apache.hadoop.hbase.regionserver.HStore$StoreFlusherImpl.flushCache(HStore.java:2523) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2622) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2352) > at > org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2314) > at > org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2200) > at > org.apache.hadoop.hbase.regionserver.HRegion.flush(HRegion.java:2125) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:512) > at > org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:482) > at > org.apache.hadoop.hbase.regionserver.MemS
Re: [ANNOUNCE] new HBase committer Sakthi
Congratulations Sakthi !! On Wed, Jul 31, 2019 at 5:05 PM Sean Busbey wrote: > On behalf of the HBase PMC, I'm pleased to announce that Sakthi has > accepted our invitation to become an HBase committer. > > We'd like to thank Sakthi for all of his diligent contributions to the > project thus far. We look forward to his continued participation in our > community. > > Congrats and welcome Sakthi! > -- Rushabh Shah - Software Engineering SMTS | Salesforce - - Mobile: 213 422 9052
