Project

General

Profile

Actions
Copy link

Bug #49894

closed

set a non-zero default value for osd_client_message_cap

Added by Neha Ojha about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Mark Nelson
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific, octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
42157
Crash signature (v1):
Crash signature (v2):

Description

The current default of 0 doesn't help and we've tried setting it to 5000 for one of our tests https://github.com/neha-ojha/ceph/blob/f02cd4d8b0c9f1566462b7b950f121a44efc1d06/qa/suites/rados/singleton/all/test_envlibrados_for_rocksdb.yaml#L8, where its seems to alleviate the problem.

Next steps before deciding the default value:

1. set it in the perf suite to measure performance impact
2. Mark to test on Officinalis to verify its impact on much faster hw

Related issues 3 (0 open — 3 closed)

Copied to RADOS - Backport #51830: pacific: set a non-zero default value for osd_client_message_capResolvedNeha OjhaActions
Copied to RADOS - Backport #51966: nautilus: set a non-zero default value for osd_client_message_capResolvedNeha OjhaActions
Copied to RADOS - Backport #51967: octopus: set a non-zero default value for osd_client_message_capResolvedNeha OjhaActions
Actions
Copy link

Also available in: Atom PDF