Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-5122

Scale everything according to the amount of available container resources

Details

    • MXS-SPRINT-215

    Description

      MXS-4155 already checked limitation of a container regarding --cpu and --memory
      and throw a warning.

      It should be possible, that Maxscale automatically respect the limitation in a container, so all values related to memory and cpus should be set to container values.
      (-memory --cpu etc)

      Attachments

        Issue Links

          Activity

            Isn't this fixed by MXS-4155? Is this a bug?

            JoeCotellese Joe Cotellese (Inactive) added a comment - Isn't this fixed by MXS-4155 ? Is this a bug?
            abhisrao Abhishek added a comment -

            From whatever I understand, MXS-4155 only provides a warning log. It does not restrict the memory and cpu to container limits.

            abhisrao Abhishek added a comment - From whatever I understand, MXS-4155 only provides a warning log. It does not restrict the memory and cpu to container limits.
            johan.wikman Johan Wikman added a comment -

            No, a note is logged if MaxScale thinks it is not configured appropriately for the environment it is running in, but does not adapt. The reason is that there were doubts whether MaxScale could accurately detect the environment in all circumstances.

            I don't think that is a good reason for not doing it. I believe MaxScale will either be able to find correct resource information (cgroups) or not at all, if it is not present in the usual location. That is, MaxScale would either adapt correctly or not adapt at all, but it would never adapt incorrectly.

            johan.wikman Johan Wikman added a comment - No, a note is logged if MaxScale thinks it is not configured appropriately for the environment it is running in, but does not adapt. The reason is that there were doubts whether MaxScale could accurately detect the environment in all circumstances. I don't think that is a good reason for not doing it. I believe MaxScale will either be able to find correct resource information (cgroups) or not at all, if it is not present in the usual location. That is, MaxScale would either adapt correctly or not adapt at all, but it would never adapt incorrectly.

            People

              johan.wikman Johan Wikman
              Richard Richard Stracke
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.