Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-9790

Dockerized daemons should set --hostname to the resolved IP

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 4.0.0
    • Infrastructure
    • None
    • ghx-label-10

    Description

      In light of IMPALA-9788 (and also IMPALA-9026), it probably makes the most sense to avoid using hostnames for internal communication in containerized setups, since container orchestration frameworks tend to do non-trivial things with DNS and hostnames.

      We can do this in the entrypoint script. I tried --hostname=$(hostname -I) and it seemed to work. It might need some improvement to handle cases when there are multiple IPs, etc.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-9788 Weird things happen when impalad restarts with different hostname but same IP

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-9026 Add an option to use resolved IP address for Statestore subscriber

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              tarmstrong Tim Armstrong
              tarmstrong Tim Armstrong
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: