Project

General

Profile

Actions

Feature #46892

closed

pybind/mgr/volumes: Make number of cloner threads configurable

Added by Kotresh Hiremath Ravishankar over 3 years ago. Updated about 3 years ago.

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

0%

Source:
Development
Tags:
Backport:
octopus,nautilus
Reviewed:
Affected Versions:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:

Description

The number of cloner threads is set to 4 and can't be configured.
This is bottle neck if the system resource is capable of handling
more number parallel clones. Hence provide an option to configure
the number of cloner threads.


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #47823: nautilus: pybind/mgr/volumes: Make number of cloner threads configurableResolvedKotresh Hiremath RavishankarActions
Copied to CephFS - Backport #47824: octopus: pybind/mgr/volumes: Make number of cloner threads configurableResolvedWei-Chung ChengActions
Actions #1

Updated by Kotresh Hiremath Ravishankar over 3 years ago

  • Category set to Performance/Resource Usage
  • Status changed from New to Fix Under Review
  • Assignee set to Kotresh Hiremath Ravishankar
Actions #2

Updated by Kotresh Hiremath Ravishankar over 3 years ago

  • Pull request ID set to 36554
Actions #3

Updated by Patrick Donnelly over 3 years ago

  • Target version set to v16.0.0
  • Source set to Development
  • Backport set to octopus,nautilus
Actions #4

Updated by Patrick Donnelly over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47823: nautilus: pybind/mgr/volumes: Make number of cloner threads configurable added
Actions #6

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47824: octopus: pybind/mgr/volumes: Make number of cloner threads configurable added
Actions #7

Updated by Nathan Cutler about 3 years 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".

Actions

Also available in: Atom PDF