You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jason Dere (JIRA)" <ji...@apache.org> on 2017/05/18 01:55:05 UTC

[jira] [Updated] (HIVE-13673) LLAP: handle case where no service instance is found on the host specified in the input split

     [ https://issues.apache.org/jira/browse/HIVE-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dere updated HIVE-13673:
------------------------------
    Status: Patch Available  (was: Open)

> LLAP: handle case where no service instance is found on the host specified in the input split
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13673
>                 URL: https://issues.apache.org/jira/browse/HIVE-13673
>             Project: Hive
>          Issue Type: Sub-task
>          Components: llap
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-13673.1.patch
>
>
> From [~sseth] on review of HIVE-13620, in regards to LlapBaseInputFormat.getServiceInstance() and how to handle the case of no LLAP service instance for the host specified in the LLAP input split:
> {quote}
> This should really be a jira and TODO (post merge to master) - to either 1) go to an alternate random address from the available llap instances, or 2) have additional locations provided by HS2.
> I'd lean towards 1. It's absolutely possible for an llap instance to go down, or the node to go down, which would end up causing failures.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)