Draft: <fix>[zbs]: ZSTAC-86782 backport MDS failover#4578
Conversation
When anti-split-brain check selects a disconnected MDS node, the HTTP call now times out after 30s instead of 5+ minutes, and automatically retries the next available MDS via tryNext mechanism. Resolves: ZSTAC-80595 Change-Id: I1be80f1b70cad1606eb38d1f0078c8f2781e6941
Catch sync REST failures in the ZBS MDS HTTP caller so getActiveClients can try the next connected MDS when the selected MDS is unreachable. Add a regression test for the volume clients path where the first MDS throws an operation failure and the second returns active clients. Resolves: ZSTAC-80595 Change-Id: Id891693b033ac3d4588243d2dd25750f63110db6
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Warning
|
Summary
Backport the complete ZSTAC-80595 fix for CBD/ZBS volume-clients anti-split-brain checks. When the selected MDS is unreachable, the request now uses the existing next-MDS path instead of ending before failover can run.
Source provenance
3b5bda3b76aef968a911d18e35b3b30bd0cab803: use the synchronous MDS caller with a 30-second timeout and enabletryNext.1f65e4e5a8a547176cab7c8ed029e3288765d9f6: convert synchronous REST failures into failed agent responses and add the regression case.Changes
/zbs/primarystorage/volume/clientstimeout at 30 seconds and enable next-MDS handling.ZbsPrimaryStorageCaseregression scenario; the only cherry-pick conflict was target-branch import context.Testing
git diff --check upstream/5.4.12..HEADplugin/zbspackageZbsPrimaryStorageCaseResolves: ZSTAC-86782
sync from gitlab !10547