Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-4859

[PMM 2.0] The server crashes frequently on kubernetes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Incomplete
    • Affects Version/s: 2.0.0
    • Fix Version/s: None
    • Component/s: PMM Server
    • Labels:
    • Environment:

      Kubernetes on-premises (v1.13.7)

      Running on GKE

      Description

      Hi guys,

       

      Our pmm server crashes frequently with the following error

      2019-10-17 14:25:05,871 INFO success: prometheus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-10-17 16:26:01,059 INFO reaped unknown pid 698
      2019-10-18 00:01:01,613 INFO reaped unknown pid 1977
      2019-10-18 01:01:01,657 INFO reaped unknown pid 2116
      2019-10-18 02:01:01,760 INFO reaped unknown pid 2255
      2019-10-18 03:13:01,835 INFO reaped unknown pid 2395
      ...

       

      Kind of related to another issue : https://jira.percona.com/projects/PMM/issues/PMM-4787

       

      We also noticed that the server uses a huge amount of resources. There seem to be a memory leak somewhere.

      Do you have guidelines for a production ready PMM instance ?

       

      Thank you

       

       

        Smart Checklist

          Attachments

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              smana Smaine Kahlouch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: