Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-2133

Enforce max hostname length of 60 characters in postConfigure

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Fix
    • 1.2.2
    • Icebox
    • ?, installation
    • None
    • 2019-01, 2019-02, 2019-03, 2019-04

    Description

      To avoid UM replication errors between UMs if hostnames are chosen, hostnames need to have less than 61 characters, as mysql.user only allows 60 characters for hostnames. Consequently, postConfigure shouldn't accept hostnames or reverse DNS hostnames longer than 60 characters.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MCOL-1607 postConfigure must support hostnames as cluster nodes network endpoints.

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

          New Feature - A new feature of the product, which has yet to be developed. MCOL-2129 Add a new postConfigure flag to resolve submitted hostnames to correct reverse dns names

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              jens.rowekamp Jens Röwekamp (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 2h 5m
                  2h 5m

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.