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

non-root install my.sql default location support

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0
    • MariaDB Server
    • None

    Description

      Customer request enhancement for non-root install and the default setup for my.cnf

      1. MYSQL_HOME is not defined - appears to be much more useful for non-root installs for apps to locate the my.cnf file

      2. When a my.cnf file cannot be located, the client tries to use a bogus internal default socket 'db/mysql.sock' file, which does not exist.

      3. software support the default /etc/my.cnf

      Attachments

        Activity

          toddstoffel In 1.4.0 the columnstore specific settings are stored in /etc/my.cnf.d/columnstore.cnf which is loaded in by my.cnf. Does that fulfil the requirements here?

          LinuxJedi Andrew Hutchings (Inactive) added a comment - toddstoffel In 1.4.0 the columnstore specific settings are stored in /etc/my.cnf.d/columnstore.cnf which is loaded in by my.cnf. Does that fulfil the requirements here?

          Support case ID has been corrected

          hill David Hill (Inactive) added a comment - Support case ID has been corrected

          customer feedback

          not sure which requirement they are trying to fulfil with that statement.

          Steps we took to resolve the issue was to define MYSQL_HOME
          $ env | grep MYSQL_HOME
          MYSQL_HOME=/home/mysql/mariadb/columnstore/mysql

          Add a custom cnf file to /home/mysql/mariadb/columnstore/mysql/my.cnf.d and edit /home/mysql/mariadb/columnstore/mysql/my.cnf to add a line with
          !includedir /home/mysql/mariadb/columnstore/mysql/my.cnf.d/
          so the files there would be read.

          After postConfigure is executed and it and the system startup puts all these files in place,
          we have to shut down the system and start it again to get all the changes to be active. Otherwise the mysql schema (and any schemas created after that) uses the previous system default character set latin1 instead of the final desired configuration of utf8.

          FYI on the 1.2.5 system we just stood up, there is not a columnstore.cnf in the specified location.
          $ pwd
          /home/mysql/mariadb/columnstore/mysql/my.cnf.d
          $ ls
          auth_gssapi.cnf client.cnf enable_encryption.preset mysql-clients.cnf rocksdb.cnf server.cnf tokudb.cnf z-sas.cnf

          The last one being our custom file.

          hill David Hill (Inactive) added a comment - customer feedback not sure which requirement they are trying to fulfil with that statement. Steps we took to resolve the issue was to define MYSQL_HOME $ env | grep MYSQL_HOME MYSQL_HOME=/home/mysql/mariadb/columnstore/mysql Add a custom cnf file to /home/mysql/mariadb/columnstore/mysql/my.cnf.d and edit /home/mysql/mariadb/columnstore/mysql/my.cnf to add a line with !includedir /home/mysql/mariadb/columnstore/mysql/my.cnf.d/ so the files there would be read. After postConfigure is executed and it and the system startup puts all these files in place, we have to shut down the system and start it again to get all the changes to be active. Otherwise the mysql schema (and any schemas created after that) uses the previous system default character set latin1 instead of the final desired configuration of utf8. FYI on the 1.2.5 system we just stood up, there is not a columnstore.cnf in the specified location. $ pwd /home/mysql/mariadb/columnstore/mysql/my.cnf.d $ ls auth_gssapi.cnf client.cnf enable_encryption.preset mysql-clients.cnf rocksdb.cnf server.cnf tokudb.cnf z-sas.cnf The last one being our custom file.

          In that case it will be fixed in 1.4. With 1.4 we load the default /etc/my.cnf and have ColumnStore specific options in /etc/my.cnf.d/columnstore.cnf. A user can add their own options in /etc/my.cnf.d.

          LinuxJedi Andrew Hutchings (Inactive) added a comment - In that case it will be fixed in 1.4. With 1.4 we load the default /etc/my.cnf and have ColumnStore specific options in /etc/my.cnf.d/columnstore.cnf. A user can add their own options in /etc/my.cnf.d.

          Question Is this the location for non-root installs or is non-root install supported in 1.4

          /etc/my.cnf.d/columnstore.cnf

          hill David Hill (Inactive) added a comment - Question Is this the location for non-root installs or is non-root install supported in 1.4 /etc/my.cnf.d/columnstore.cnf

          The former for now, we haven't made a decision on the latter.

          LinuxJedi Andrew Hutchings (Inactive) added a comment - The former for now, we haven't made a decision on the latter.

          Since this is non-root install related,
          I dont think it should be closed
          until we know how non-root
          will be supported in 1.4

          hill David Hill (Inactive) added a comment - Since this is non-root install related, I dont think it should be closed until we know how non-root will be supported in 1.4

          If non-root goes away it will be replaced by something else. Either way the paths have already changed in 1.4.

          LinuxJedi Andrew Hutchings (Inactive) added a comment - If non-root goes away it will be replaced by something else. Either way the paths have already changed in 1.4.

          People

            toddstoffel Todd Stoffel (Inactive)
            hill David Hill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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