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

Timeouts for row lock and scan should be separate

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.94.0
    • Fix Version/s: 0.95.0
    • Component/s: regionserver
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Release Note:
      Hide
      "hbase.regionserver.lease.period" is no longer supported.

      hbase.regionserver.rowlock.timeout.period controls the timeout for rowlock. Default is 60 seconds.

      hbase.client.scanner.timeout.period controls scanner timeout. Default is 60 seconds.
      Show
      "hbase.regionserver.lease.period" is no longer supported. hbase.regionserver.rowlock.timeout.period controls the timeout for rowlock. Default is 60 seconds. hbase.client.scanner.timeout.period controls scanner timeout. Default is 60 seconds.

      Description

      Apparently the timeout used for row locking and for scanning is global. It would be better to have two separate timeouts.
      (opening the issue to make Lars George happy)

        Attachments

        1. 6170.add2
          0.9 kB
          Ted Yu
        2. 6170.addendum
          2 kB
          Ted Yu
        3. 6170v4.patch
          14 kB
          Ted Yu
        4. HBASE-6170v3.patch
          14 kB
          Chris Trezzo
        5. HBASE-6170v2.patch
          14 kB
          Chris Trezzo
        6. HBASE-6170v1.patch
          14 kB
          Chris Trezzo
        7. HBASE-6170v1.patch
          14 kB
          Chris Trezzo
        8. HBASE-6170v1.patch
          14 kB
          Chris Trezzo

          Activity

            People

            • Assignee:
              ctrezzo Chris Trezzo
              Reporter:
              otis Otis Gospodnetic
            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: