Project

General

Profile

Bug #51271

mgr/volumes: use a dedicated libcephfs handle for subvolume API calls

Added by Venky Shankar over 2 years ago. Updated 7 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Performance/Resource Usage
Target version:
% Done:

100%

Source:
Tags:
backport_processed
Backport:
pacific,octopus
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

So as to improve cache efficiency of volumes plugin by avoiding purge queue threads using this handle.


Related issues

Related to CephFS - Bug #51256: pybind/mgr/volumes: purge queue seems to block operating on cephfs connection required by dispatch thread Resolved
Copied to CephFS - Backport #51544: pacific: mgr/volumes: use a dedicated libcephfs handle for subvolume API calls Resolved
Copied to CephFS - Backport #51545: octopus: mgr/volumes: use a dedicated libcephfs handle for subvolume API calls Rejected

History

#1 Updated by Venky Shankar over 2 years ago

  • Related to Bug #51256: pybind/mgr/volumes: purge queue seems to block operating on cephfs connection required by dispatch thread added

#2 Updated by Venky Shankar over 2 years ago

I'm testing the changes. Will push a PR once ready.

#3 Updated by Venky Shankar over 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 41966

#4 Updated by Patrick Donnelly over 2 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport changed from nautilus,octopus,pacific to pacific,octopus

#5 Updated by Backport Bot over 2 years ago

  • Copied to Backport #51544: pacific: mgr/volumes: use a dedicated libcephfs handle for subvolume API calls added

#6 Updated by Backport Bot over 2 years ago

  • Copied to Backport #51545: octopus: mgr/volumes: use a dedicated libcephfs handle for subvolume API calls added

#7 Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed

#8 Updated by Konstantin Shalygin 7 months ago

  • Status changed from Pending Backport to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF