Project

General

Profile

Feature #38549

multisite: add perf counters for data sync

Added by Casey Bodley about 2 years ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
multisite
Backport:
luminous mimic nautilus
Reviewed:
Affected Versions:
Pull request ID:

Description

perf counters should measure the bandwidth used for object replication, and the frequency and average latency of requests for replication logs

this information can be used to construct an aggregate view of replication bandwidth, for comparison against the rate of ingest on other zones. it can also tell you whether aggregate bandwidth improves as you add replication gateways

the average latency of log requests can indicate heavy load on remote sync endpoints, and measure the benefit from additional endpoints


Related issues

Copied to rgw - Backport #38916: mimic: multisite: add perf counters for data sync Rejected
Copied to rgw - Backport #38917: luminous: multisite: add perf counters for data sync Rejected
Copied to rgw - Backport #38918: nautilus: multisite: add perf counters for data sync Resolved

History

#1 Updated by Casey Bodley about 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 26722

#2 Updated by Casey Bodley about 2 years ago

  • Status changed from Fix Under Review to Resolved

#3 Updated by Casey Bodley about 2 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to luminous mimic nautilus

#4 Updated by Nathan Cutler about 2 years ago

  • Copied to Backport #38916: mimic: multisite: add perf counters for data sync added

#5 Updated by Nathan Cutler about 2 years ago

  • Copied to Backport #38917: luminous: multisite: add perf counters for data sync added

#6 Updated by Nathan Cutler about 2 years ago

  • Copied to Backport #38918: nautilus: multisite: add perf counters for data sync added

#7 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF