You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/06/23 22:31:07 UTC
[jira] Updated: (HBASE-1573) Holes in master state change; updated
startcode and server go into .META. but catalog scanner just got old values
[ https://issues.apache.org/jira/browse/HBASE-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1573:
-------------------------
Summary: Holes in master state change; updated startcode and server go into .META. but catalog scanner just got old values (was: Scan of large meta takes a long time and so can see stale data; can result is double region assignment)
Changed issue title.
So digging, the serverName we find when we scan is that of a dead server since processed but the region has just been opened on its new server. The batchupdate of .META. has just been run in the master but the outstanding catalog scanner is not seeing new entry, either because the next took too long to come across or because we're using caching in our .META. scanning.
> Holes in master state change; updated startcode and server go into .META. but catalog scanner just got old values
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1573
> URL: https://issues.apache.org/jira/browse/HBASE-1573
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.19.4
>
> Attachments: 1573-v2.patch, 1573.patch
>
>
> Here is example of a scan that takes a while because 6k regions acting on stale data resulting in double assignment of region:
> {code}
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:06,220 INFO org.apache.hadoop.hbase.master.ServerManager: Received MSG_REPORT_OPEN: enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748: safeMode=false from XX.XX.45.121:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:06,220 INFO org.apache.hadoop.hbase.master.RegionServerOperation: enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748 open on XX.XX.45.121:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:06,220 INFO org.apache.hadoop.hbase.master.RegionServerOperation: updating row enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748 in region .META.,,1 with with startcode !?B and server XX.XX.45.121:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:06,397 DEBUG org.apache.hadoop.hbase.master.BaseScanner: Current assignment of enwikibase,Cwj0sehVeEbnrUDR_j0xok==,1245604540748 is not valid; Server 'XX.XX.44.95:20020' unknown.
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:06,582 INFO org.apache.hadoop.hbase.master.RegionManager: Assigning region enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748 to XX.XX.45.97:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:09,587 INFO org.apache.hadoop.hbase.master.ServerManager: Received MSG_REPORT_PROCESS_OPEN: enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748: safeMode=false from XX.XX.45.97:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:12,614 INFO org.apache.hadoop.hbase.master.ServerManager: Received MSG_REPORT_OPEN: enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748: safeMode=false from XX.XX.45.97:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:13,549 INFO org.apache.hadoop.hbase.master.RegionServerOperation: enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748 open on XX.XX.45.97:20020
> hbase-Powerset-master-aa0-000-8.u.powerset.com.log.2009-06-22:2009-06-22 10:56:13,549 INFO org.apache.hadoop.hbase.master.RegionServerOperation: updating row enwikibase,Cwj1sehVeEbnrUDR_j0xok==,1245604540748 in region .META.,,1 with with startcode !?? and server XX.XX.45.97:20020
> {code}
> We've just updated the server info in the master because of the region open message but the scan sees old info in the .META. table though .META. was just updated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.