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

Only fail cacheBlock if block collisions aren't related to next block metadata

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Hadoop Flags:
      Reviewed

      Description

      This is the issue I was originally having here: http://mail-archives.apache.org/mod_mbox/hbase-dev/201802.mbox/%3CCAN+qs_Pav=md_Aoj4Xji+KCNETubg2XOu2nTxV1g6m8-5VN-GA@mail.gmail.com%3E

       

      When we pread, we don't force the read to read all of the next block header.
      However, when we get into a race condition where two opener threads try to
      cache the same block and one thread read all of the next block header and the other one didn't, it will fail the open process. This is especially important
      in a splitting case where it will potentially fail the split process.
      Instead, in the caches, we should only fail if the required blocks are different.

        Attachments

        1. HBASE-20447.branch-1.001.patch
          27 kB
          Zach York
        2. HBASE-20447.branch-1.002.patch
          27 kB
          Zach York
        3. HBASE-20447.branch-1.003.patch
          27 kB
          Zach York
        4. HBASE-20447.branch-1.004.patch
          27 kB
          Zach York
        5. HBASE-20447.branch-1.005.patch
          28 kB
          Zach York
        6. HBASE-20447.branch-1.006.patch
          28 kB
          Zach York
        7. HBASE-20447.master.001.patch
          26 kB
          Zach York
        8. HBASE-20447.master.002.patch
          26 kB
          Zach York
        9. HBASE-20447.master.003.patch
          26 kB
          Zach York
        10. HBASE-20447.master.004.patch
          27 kB
          Zach York

        Issue Links

          Activity

            People

            • Assignee:
              zyork Zach York
              Reporter:
              zyork Zach York

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment