Actions
Bug #61733
closedavoid ballooning client_mount_timeout by 10x
% Done:
0%
Source:
Backport:
pacific,quincy,reef
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
MonClient
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v18.0.0-5016-ga49357a6c24
Released In:
v19.2.0~1985
Upkeep Timestamp:
2025-07-12T07:38:31+00:00
Description
While reducing a "waiting for config" timeout from 30 seconds to 3 and instead introducing 10 retries, https://github.com/ceph/ceph/commit/3c2b30e4c5dd2d0ea5f38feb8a05ad02bf9c3bd9 also subjected MonClient::authenticate() to these retries. However, MonClient::authenticate() is going by client_mount_timeout which defaults to 5 minutes. As a result, when the monitors are unreachable or there are other connectivity issues, we end up taking 50 minutes to return ETIMEDOUT from rados_connect().
Updated by Ilya Dryomov almost 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 52124
Updated by Radoslaw Zarzynski almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Upkeep Bot almost 3 years ago
- Copied to Backport #61755: pacific: avoid ballooning client_mount_timeout by 10x added
Updated by Upkeep Bot almost 3 years ago
- Copied to Backport #61756: reef: avoid ballooning client_mount_timeout by 10x added
Updated by Upkeep Bot almost 3 years ago
- Copied to Backport #61757: quincy: avoid ballooning client_mount_timeout by 10x added
Updated by Ilya Dryomov almost 3 years ago
Hi Radek,
This seems to have been moved to "Pending Backport" prematurely -- the PR is not merged, it only got labeled with needs-qa.
Updated by Radoslaw Zarzynski about 2 years ago
- Status changed from Pending Backport to Resolved
Updated by Upkeep Bot 8 months ago
- Merge Commit set to a49357a6c242364c2dfa18d1f7127e8fd42cabe8
- Fixed In set to v18.0.0-5016-ga49357a6c24
- Released In set to v19.2.0~1985
- Upkeep Timestamp set to 2025-07-12T07:38:31+00:00
Actions