Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1620

Consensus peer proxy hostnames should be reresolved on failure

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.0
    • Fix Version/s: None
    • Component/s: consensus
    • Labels:
      None

      Description

      Noticed this while documenting the workflow to replace a dead master, which currently bypasses Raft config changes in favor of having the replacement master "masquerade" as the dead master via DNS changes.

      Internally we never rebuild consensus peer proxies in the event of network failure; we assume that the peer will return at the same location. Nominally this is reasonable; allowing peers to change host/port information on the fly is tricky and has yet to be implemented. But, we should at least retry the DNS resolution; not doing so forces the workflow to include steps to restart the existing masters, which creates a (small) availability outage.

        Issue Links

          Activity

          Hide
          adar Adar Dembo added a comment -

          KUDU-418 describes the larger problem of changing host/port information on the fly.

          And of course, if we fix KUDU-75, this becomes a non-issue.

          Show
          adar Adar Dembo added a comment - KUDU-418 describes the larger problem of changing host/port information on the fly. And of course, if we fix KUDU-75 , this becomes a non-issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              adar Adar Dembo
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development