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

improve VerifyReplication to compute BADROWS more accurately

    Details

    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      VerifyReplicaiton reports the following counters besides the existing ones:

      ONLY_IN_SOURCE_TABLE_ROWS: number of rows found only in source
      ONLY_IN_PEER_TABLE_ROWS: number of rows found only in peer
      CONTENT_DIFFERENT_ROWS: number of rows whose contents are different between source and peer
      Show
      VerifyReplicaiton reports the following counters besides the existing ones: ONLY_IN_SOURCE_TABLE_ROWS: number of rows found only in source ONLY_IN_PEER_TABLE_ROWS: number of rows found only in peer CONTENT_DIFFERENT_ROWS: number of rows whose contents are different between source and peer

      Description

      VerifyReplicaiton could compare the source table with its peer table and compute BADROWS. However, the current BADROWS computing method might not be accurate enough. For example, if source table contains rows as

      {r1, r2, r3, r4}

      and peer table contains rows as

      {r1, r3, r4}

      BADROWS will be 3 because 'r2' in source table will make all the later row comparisons fail. Will it be better if the BADROWS is computed to 1 in this situation? Maybe, we can compute the BADROWS more accurately in merge comparison?

        Attachments

        1. 10153-0.98.txt
          5 kB
          Ted Yu
        2. 10153-v2-trunk.txt
          5 kB
          Ted Yu
        3. HBASE-10153-trunk.patch
          5 kB
          Jianwei Cui
        4. HBASE-10153-0.94-v1.patch
          4 kB
          Jianwei Cui

          Activity

            People

            • Assignee:
              cuijianwei Jianwei Cui
              Reporter:
              cuijianwei Jianwei Cui
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: