drive read latency is greater than 100s when leader handle fetch data request
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29
- Forks
- 30
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
This happened when testing 16M blob r/w, details in issue60
Leader (sm-long-running2-3) metrics:
HS side: https://console.sherlock.io/d/b43364d3-4b8c-476b-a7e8-73219b91f82e/nuobject-storage-manager?orgId=1&var-namespace=sdsapp&var-subcluster=nuobject2-sh-3&var-pg=$__all&var-sm=$__all&from=2025-06-13T12:10:00.000Z&to=2025-06-13T12:50:39.000Z&timezone=browser
Node side (disk is sdd):
https://console.sherlock.io/d/nLt4mwcVz/node-status-dashboard-tess?orgId=1&from=2025-06-13T12:10:00.000Z&to=2025-06-13T12:50:39.000Z&timezone=browser&var-node=tess-node-ltl7f-tess30.stratus.lvs.ebay.com&var-Filters=
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked issue60 document and the provided leader and node metrics, then investigate the 16M blob read/write scenario described in the report. Done means identifying the cause of read latency exceeding 100 seconds and confirming the behavior is corrected with a comparable test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100