Bug 1571877

Summary: [RFE] Additional support for Dynamic Parameter Injection
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED DEFERRED QA Contact: Manohar Murthy <mmurthy>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.0CC: ceph-eng-bugs, gsitlani, kperks, lithomas, nojha, pdhiran, vereddy, vumrao
Target Milestone: ---Keywords: FutureFeature
Target Release: 5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-21 21:32:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1725227    

Description Mike Hackett 2018-04-25 15:04:06 UTC
Description of problem:

There is a need for improvement through new features to make troubleshooting easier through the dynamic injection of parameters to modify the behavior of the software to provide the user with a quicker way to react in order to stabilize a cluster. 

The parameters that should be dynamically accessible include, but are not limited to:

Pool migration scenario - To make troubleshooting much easier, being able to inject some timeout values. For example, the following settings are not injectable, which made it very difficult to get out of a cascading failure with a pool migration at a customer site:

osd_op_thread_timeout=2000
filestore_op_thread_timeout=2000
osd_recovery_max_omap_entries_per_chunk = 1024

Cluster tuning/stabilizing - after or during a hardware failure or a pool migration:

All scrubbing parameters
All recovery and backfill parameters

Having to set these commands and restarting thousands of OSD's is not practical and dynamic injection is required.

Version-Release number of selected component (if applicable):
3.0

Comment 5 Giridhar Ramaraju 2019-08-05 13:10:12 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Giridhar Ramaraju 2019-08-05 13:11:18 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 9 Josh Durgin 2019-09-27 22:49:42 UTC
*** Bug 1586204 has been marked as a duplicate of this bug. ***

Comment 10 Yaniv Kaul 2020-12-09 13:25:13 UTC
Moving to 5.1, although it's not clear to me if we have concrete work here that we are committed to implement.