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

Master aborting if not able to talk to overloaded RS

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Duplicate
    • Affects Version/s: 0.90.0
    • Fix Version/s: 0.90.0
    • Component/s: None
    • Labels:
      None

      Description

      Had lots of inserts into a a single region going on. It caused the RS stop responding to a split request by the master, which caused the master to abort. We should not abort but instead try again.

      Master logs attached

      1. master.rtf
        10 kB
        Amandeep Khurana

        Activity

        Hide
        stack stack added a comment -

        Andrew... I'm moving it out. Was found in RC0. I believe this fixed in RC1 (We added catch of socket timeout). Moving out till Aman verifies its not in 0.90 tip of the branch.

        Show
        stack stack added a comment - Andrew... I'm moving it out. Was found in RC0. I believe this fixed in RC1 (We added catch of socket timeout). Moving out till Aman verifies its not in 0.90 tip of the branch.
        Hide
        stack stack added a comment -

        Fix is HBASE-3301 Treat java.net.SocketTimeoutException same as ConnectException assigning/unassigning region

        Show
        stack stack added a comment - Fix is HBASE-3301 Treat java.net.SocketTimeoutException same as ConnectException assigning/unassigning region
        Hide
        tlipcon Todd Lipcon added a comment -

        Resolving as dup, please re-open if you see this again

        Show
        tlipcon Todd Lipcon added a comment - Resolving as dup, please re-open if you see this again
        Hide
        lars_francke Lars Francke added a comment -

        This issue was closed as part of a bulk closing operation on 2015-11-20. All issues that have been resolved and where all fixVersions have been released have been closed (following discussions on the mailing list).

        Show
        lars_francke Lars Francke added a comment - This issue was closed as part of a bulk closing operation on 2015-11-20. All issues that have been resolved and where all fixVersions have been released have been closed (following discussions on the mailing list).

          People

          • Assignee:
            Unassigned
            Reporter:
            amansk Amandeep Khurana
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development