Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-7823 SCM HA Phase 2
  3. HDDS-4230

SCMBlockLocationFailoverProxyProvider should handle LeaderNotReadyException

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • SCM
    • None

    Description

      It is an enhancement for HDDS-3188.

      Like OMFailoverProxyProvider, SCMBlockLocationFailoverProxyProvider should also handle LeaderNotReadyException.

      If SCM client (like OzoneManager) has touched leader SCM, meanwhile leader SCM is stuck in replaying raft log entries(e.g., that SCM restarts and becomes leader, it needs time to recover its state machine by replaying all raft log entries), SCM client should not round robin to the next SCM, It should wait and retry the same SCM later.

      Attachments

        Issue Links

          is a clone of

          Sub-task - The sub-task of the issue HDDS-3188 Add failover proxy to SCM block protocol

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              amaliujia Rui Wang
              glengeng Glen Geng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: