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

[AMv2] expireServers and ServerCrashProcedure cleanup

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Region Assignment
    • Labels:
      None

      Description

      In review of HBASE-18551, Umesh Agashe posed a scenario that revealed a hole in our processing of unassigns; there is case where a UP might not get notification from ServerCrashProcedure if the UP is scheduled AFTER a SCP has gotten past its handleRIT call (No new SCP will be queued because expireServer won't let it happen if crashed server is in dead server list which it will be).

      Chatting on it, expireServers is doing checks that belong inside ServerCrashProcedure. expireServers scheduling an SCP each time it is called would make it so SCP processing is serialized one behind the other. If the first does the clean up all subsequent will do no work but Procedures dependent on them will get their wakeup call.

      This issue is about implementing the above cleanup.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stack Michael Stack
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: