Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Detect failed node for communication error
See original GitHub issueWhen a node failed during the query execution, often TOO_MANY_REQUEST_FAILED (on coordinator) or PAGE_TRANSPORT_TIMEOUT (on worker) are thrown.
Once the coordinator see such errors, it should consult FailureDetector, and if the targeting node is a known failed node, we should thrown an NODE_FAILED_DURING_QUERY_EXECUTION (name TBD) error instead. This could help diagnose whether a query failure is an Presto software issue, or an hardware issue.
We need to rewrite the failure reason for these two types of exceptions.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I believe @electrum wanted something like
HOST_UNREACHABLE.This issue has been automatically marked as stale because it has not had any activity in the last 2 years. If you feel that this issue is important, just comment and the stale tag will be removed; otherwise it will be closed in 7 days. This is an attempt to ensure that our open issues remain valuable and relevant so that we can keep track of what needs to be done and prioritize the right things.