[ 
https://issues.apache.org/jira/browse/HIVE-22359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039652#comment-17039652
 ] 

Gopal Vijayaraghavan commented on HIVE-22359:
---------------------------------------------

As 2 commits - the DNS issue and the task-kill issue are orthogonal (but needs 
both). One is a 300s timeout, the other is a failure to communicate.

> LLAP: when a node restarts with the exact same host/port in kubernetes it is 
> not detected as a task failure
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-22359
>                 URL: https://issues.apache.org/jira/browse/HIVE-22359
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gopal Vijayaraghavan
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-22359.1.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {code}
> │ <14>1 2019-10-16T22:16:39.233Z 
> query-coordinator-0-5.query-coordinator-0-service.compute-1569601454-l2x9.svc.cluster.local
>  query-coordinator 1 461e5ad9-f05f-11e9-85f7-06e84765763e [mdc@18060 
> class="te │
> │ zplugins.LlapTaskCommunicator" level="INFO" thread="IPC Server handler 4 on 
> 33333"] The tasks we expected to be on the node are not there: 
> attempt_1569601631911_0000_1_04_000034_0, attempt_15696016319 │
> │ 11_0000_1_04_000071_0, attempt_1569601631911_0000_1_04_000191_0, 
> attempt_1569601631911_0000_1_04_000211_0, 
> attempt_1569601631911_0000_1_04_000229_0, 
> attempt_1569601631911_0000_1_04_000231_0, attempt_1 │
> │ 569601631911_0000_1_04_000235_0, attempt_1569601631911_0000_1_04_000242_0, 
> attempt_1569601631911_0000_1_04_000160_1, 
> attempt_1569601631911_0000_1_04_000012_2, 
> attempt_1569601631911_0000_1_04_000003_2, │
> │  attempt_1569601631911_0000_1_04_000056_2, 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to