You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2021/07/21 11:40:21 UTC

[GitHub] [druid] georgezhangguo opened a new issue #11476: Overlord did not monitor the zk status change of the task, causing the task to time out and fail. In fact, the task has been completed.

georgezhangguo opened a new issue #11476:
URL: https://github.com/apache/druid/issues/11476

Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").

### Affected Version
≥ 0.17.0
The Druid version where the problem was encountered.

Overlord did not monitor the zk status change of the task, causing the task to time out and fail. In fact, the task has been completed.
In the inder storage mode, the task is executed very quickly, from the RUNNING state to the SUCCESS state soon, the overlord has not monitored the state change of the task, and is still waiting for the state of the task through zk. In fact, the task has been executed.

### Description

Please include as much detailed information about the problem as possible.
- Cluster size
- Configurations in use
- Steps to reproduce the problem
- The error message or stack traces encountered. Providing more context, such as nearby log messages or even entire logs, can be helpful.
- Any debugging that you have already done

--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org

[GitHub] [druid] georgezhangguo commented on issue #11476: Overlord did not monitor the zk status change of the task, causing the task to time out and fail. In fact, the task has been completed.

Posted by GitBox <gi...@apache.org>.

georgezhangguo commented on issue #11476:
URL: https://github.com/apache/druid/issues/11476#issuecomment-884891943


   The detailed logs are as follows:
   1. overlord.log
   
   
   2. indexer.log
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org

[GitHub] [druid] georgezhangguo removed a comment on issue #11476: Overlord did not monitor the zk status change of the task, causing the task to time out and fail. In fact, the task has been completed.

Posted by GitBox <gi...@apache.org>.

georgezhangguo removed a comment on issue #11476:
URL: https://github.com/apache/druid/issues/11476#issuecomment-884891943


   The detailed logs are as follows:
   1. overlord.log
   
   
   2. indexer.log
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org