Hi Michael, That indicates some inconsistency in your hbase:meta, where that region info is not up to date, showing the region online on a region server (RS) instance that doesn't exist anymore (the 1580999341692 indicates the timestamp of when that RS instance was started. Everytime you restart an RS, a new instance is created and that "code" receives the timestamp of the new start time).
What are the (possible) reasons for the error? > Looks familiar to a few known issues, such as HBASE-23594 or HBASE-21344, to mention a few, but a thorough investigation would be needed to determine what actually caused this, in this specific case. Where there any RS crashes/restarts or any sort of manual intervention applied to this hbase cluster? How do I get the region online > again? > You would need to force this region to get re-assigned. If you can afford temporary unavailability of this table region, you could try hbase shell disable/enable command for this table. If disable fails to complete because of this inconsistency, next resource would be to use hbck2 unassigns/assigns command pair on that region. HBCK2 is shipped as a separate project, you can download it from: https://hbase.apache.org/downloads.html Em sex., 7 de fev. de 2020 às 10:47, Michael Wohlwend < mich...@fantasymail.de> escreveu: > Hi, > > I have the following error in the logs: > > Not running balancer because 1 regions found not on an online server > {...} state=OPEN ts=... server=hadoop-data04, 16020, 1580999341692 's > server > is not in the online server list > > All five region servers are working, it's this one region which doesn't > seem to > be found. No other errors are reported. > > In the log, the server is identified with > server=hadoop-data04, 16020, 1580999341692 > > On the webinterface the server is identified with > server=hadoop-data04, 16020, 1581068616107 > > Is this ok, that the last number is different? > > What are the (possible) reasons for the error? How do I get the region > online > again? > > Thanks > Michael > > > > >
