Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21601 HBase (asyncwal?) can write a corrupted WAL record
  3. HBASE-21838

Create a special ReplicationEndpoint just for verifying the WAL entries are fine

    XMLWordPrintableJSON

    Details

    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      Introduce a VerifyWALEntriesReplicationEndpoint which replicates nothing but only verifies if all the cells are valid.
      It can be used to capture bugs for writing WAL, as most times we will not read the WALs again after writing it if there are no region server crashes.
      Show
      Introduce a VerifyWALEntriesReplicationEndpoint which replicates nothing but only verifies if all the cells are valid. It can be used to capture bugs for writing WAL, as most times we will not read the WALs again after writing it if there are no region server crashes.

      Description

      This is a missing part in our ITBLL. We can config a dummy replication endpoint which replicates nothing but only reads and verifies that all the wal files are readable and the entries are all fine.

      With this I think it will be much easier to catch the problem in the parent issue.

        Attachments

        1. HBASE-21838-v1.patch
          9 kB
          Duo Zhang
        2. HBASE-21838.patch
          9 kB
          Duo Zhang

          Activity

            People

            • Assignee:
              zhangduo Duo Zhang
              Reporter:
              zhangduo Duo Zhang
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: