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

Dynamically update peer host-ports based on registration in master

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • M4
    • None
    • consensus, master

    Description

      Currently we assume that, once initialized, a tserver never changes its IP or port. That's a poor assumption (eg environments like ec2, or even on-premise when a network gets renumbered).

      We should introduce a "resolver" interface to map from uuid->hostport by contacting the master (the master already maintains this registry locally). Consensus needs to be able to use this interface when it has trouble connecting to its cached peer hostport info.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tlipcon Todd Lipcon
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: