search

prestodb / presto

The official home of the Presto distributed SQL query engine for big data
http://prestodb.io
Apache License 2.0
16.06k stars 5.38k forks source link

REMOTE_TASK_MISMATCH on a simple query #5570

Closed tesseract2048 closed 4 years ago

tesseract2048 commented 8 years ago

I've encountered this issue during tests on 0.149:

SQL:

SELECT table_name FROM information_schema.tables WHERE table_schema = 'default'

Error Information Error Type INTERNAL_ERROR Error Code REMOTE_TASK_MISMATCH (65544) Stack Trace 

com.facebook.presto.spi.PrestoException: Could not communicate with the remote task. The node may have crashed or be under too much load. This is probably a transient issue, so please retry your query in a few minutes.
    at com.facebook.presto.server.remotetask.ContinuousTaskStatusFetcher.updateTaskStatus(ContinuousTaskStatusFetcher.java:234)
    at com.facebook.presto.server.remotetask.ContinuousTaskStatusFetcher.success(ContinuousTaskStatusFetcher.java:168)
    at com.facebook.presto.server.remotetask.ContinuousTaskStatusFetcher.success(ContinuousTaskStatusFetcher.java:52)
    at com.facebook.presto.server.remotetask.SimpleHttpResponseHandler.onSuccess(SimpleHttpResponseHandler.java:49)
    at com.facebook.presto.server.remotetask.SimpleHttpResponseHandler.onSuccess(SimpleHttpResponseHandler.java:27)
    at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
    at io.airlift.concurrent.BoundedExecutor.drainQueue(BoundedExecutor.java:77)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

Any idea? Thanks.

delbao commented 6 years ago

+1 same here

ayush-chauhan commented 6 years ago

Have you found the solution or any workaround for this error?

dain commented 6 years ago

REMOTE_TASK_MISMATCH means the process restarted. The other errors are general communication errors that typically mean the machine had a very long GC or was generally unreachable for a long time.

dain commented 6 years ago

BTW, make sure you are running a recent release.

stale[bot] commented 4 years ago

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.