Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-18401

Region Replica shows up in meta table after split

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Duplicate
    • 1.3.1, 1.2.6, 2.0.0-alpha-1
    • None
    • regionserver
    • None

    Description

      Read replica is broken in branch-1, after the region split, we saw replica region as content in hbase:meta, while the previous behavior is that replica region should not show up in info:regioninfo.

      t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, NAME => 't1,r2111,1500340472229_0001.d8faa669dde7
       e73ca.                                             75c323f6e55fd5aa36e0.', STARTKEY => 'r2111', ENDKEY => 'r21111', REPLICA_ID => 1}                                                                     
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:seqnumDuringOpen, timestamp=1500340472379, value=\x00\x00\x00\x00\x00\x00\x00\x02                                                         
       e73ca.                                                                                                                                                                                                   
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:seqnumDuringOpen_0001, timestamp=1500340472406, value=\x00\x00\x00\x00\x00\x00\x00\x02                                                    
       e73ca.                                                                                                                                                                                                   
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105                                                            
       e73ca.                                                                                                                                                                                                   
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105                                                       
       e73ca.                                                                                                                                                                                                   
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:serverstartcode, timestamp=1500340472379, value=1500340443589                                                                             
       e73ca.                                                                                                                                                                                                   
       t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:serverstartcode_0001, timestamp=1500340472406, value=\x00\x00\x01]SBY\xC5            
      

      This was introduced by https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464

      It does not consider that case that regionInfo could come from a replica region.

      Attachments

        1. HBASE-18401-branch-1.2-v003.patch
          3 kB
          Hua Xiang
        2. HBASE-18401-branch-1.2-v002.patch
          3 kB
          Hua Xiang
        3. HBASE-18401-branch-1.2-v001.patch
          1.0 kB
          Hua Xiang
        4. HBASE-18401.master.001.patch
          2 kB
          Hua Xiang

        Issue Links

          Activity

            People

              huaxiang Hua Xiang
              huaxiang Hua Xiang
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: