Job Fails Even with Small Batches
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- backend-api-design, networking
Research direction
Start by reviewing the linked discussions for issues #439, #440, and #414, then compare their proposed causes with the reported logger evidence: one-at-a-time posts under 105 KiB. The issue does not name files or tests; done would require identifying the cause of the RemoteDisconnected error and defining which connection, timeout, batching, or retry behavior needs changing.
Written by the indexing model from the issue text.
Description
I've been running an algorithm for the last couple weeks and keep getting a 'RemoteDisconnected' error. The linked issue claims that the main cause of the issue is the large batch size. Through the logger I've confirmed that my posts are only 1 at a time, and the total size is less than 105KB (~1KiB). After reading through the other issues linked I'm unsure if they would help either, nor exactly how to implement them.
Is the connection error simply something that must be solved by fast, stable internet?
Original Issue:
Verified fix:
- decrease default batch size to 10 (~5 MiB for 10 full Advantage-size problems)
- ideally, limit batch size by payload bytes (default to 5 MiB)
- decouple connect from read timeout (#440), and increase the default read timeout to 600 s
- implement retry strategy from #414
Originally posted by @randomir in https://github.com/dwavesystems/dwave-cloud-client/issues/439#issuecomment-720752001
- Dominant language
- Python
- Stars
- 63
- Forks
- 44
- Avg merge
- 6h 55m
- Merged PRs (30d)
- 2
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.
More from dwavesystems/dwave-cloud-client
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
dwavesystems/dwave-cloud-client#748 · 1 reaction ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dwavesystems/dwave-cloud-client#738 · 1 comment ·
All issues in dwavesystems/dwave-cloud-client
Similar issues
-
bug priority:low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
CyberAgent/psd2svg#436 ·
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#122386 · 1 comment ·
-
ai-generated
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/production-stack#1105 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100