Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-1419

WAL replay is more resource intensive than normal use

XMLWordPrintable

      WAL replay is currently extremely memory intensive, much more so than when the process stopped. This has repeatedly caused incidents. Ideally WAL replay is mostly CPU and disk IO bound.

      DoD: WAL replay does not take more memory than it did before stopping.

              Unassigned Unassigned
              fbranczy@redhat.com Frederic Branczyk (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: