Percona Monitoring and Management 1.2.1

  • Date

    August 16, 2017

For install and upgrade instructions, see Deploying Percona Monitoring and Management.

This hotfix release improves memory consumption

Changes in PMM Server

The following changes were introduced in PMM Server 1.2.1:

Bug fixes

  • PMM-1280: PMM server affected by nGinx CVE-2017-7529

    An integer overflow exploit could result in a DOS (Denial of Service) for the affected nginx service with the max_ranges directive not set.

    This problem is solved by setting the set max_ranges directive to 1 in the nGinx configuration.

Improvements

  • PMM-1232: Update the default value of the METRICS_MEMORY configuration setting

    Previous versions of PMM Server used a different value for the METRICS_MEMORY configuration setting which allowed Prometheus to use up to 768MB of memory.

    PMM Server 1.2.0 used the storage.local.target-heap-size setting, its default value being 256MB. Unintentionally, this value reduced the amount of memory that Prometheus could use. As a result, the performance of Prometheus was affected.

    To improve the performance of Prometheus, the default setting of storage.local.target-heap-size has been set to 768 MB.

  • Page updated 2021-01-11

Contents

Previous topic

Percona Monitoring and Management 1.2.2

Next topic

Percona Monitoring and Management 1.2.0

Contact Us

For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.