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

Acquiring readLock does not apply timeout in HRegion#flushcache

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.94.4, 0.95.2
    • Fix Version/s: 0.94.4, 0.95.0
    • Component/s: regionserver
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      HRegion
        public boolean flushcache() throws IOException {
             lock(lock.readLock());
        }
      

      The HRegion.flushcache is called by the normal flush cache, so if we use a timeout, the MemStoreFlusher may be get a RegionTooBusyException, it is safe to do not use a timeout.

        Attachments

        1. HBASE-7376-94.patch
          0.6 kB
          Lijin Bin
        2. HBASE-7376-trunk.patch
          0.7 kB
          Lijin Bin

        Issue Links

          Activity

            People

            • Assignee:
              binlijin Lijin Bin
              Reporter:
              binlijin Lijin Bin

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment