You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/09/02 21:36:20 UTC

[jira] [Comment Edited] (HIVE-14680) retain consistent splits /during/ (as opposed to across) LLAP failures on top of HIVE-14589

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

Sergey Shelukhin edited comment on HIVE-14680 at 9/2/16 9:36 PM:
-----------------------------------------------------------------

Tested the patch on cluster. When it doesn't hit HIVE-14608, it behaves very well... during node restarts, after node restarts, flexing the cluster down and back up, and the a higher size from down, too, cache hit ratio stays high as expected. 


was (Author: sershe):
Tested the patch on cluster. When it doesn't hit HIVE-14608, it behaves very well... during node restarts, after node restarts, flexing the cluster down and back up, and the a higher size from down, too.

> retain consistent splits /during/ (as opposed to across) LLAP failures on top of HIVE-14589
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-14680
>                 URL: https://issues.apache.org/jira/browse/HIVE-14680
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-14680.patch
>
>
> see HIVE-14589.
> Basic idea (spent about 7 minutes thinking about this based on RB comment ;)) is to return locations for all slots to HostAffinitySplitLocationProvider, the missing slots being inactive locations (based solely on the last slot actually present). For the splits mapped to these locations, fall back via different hash functions, or some sort of probing.
> This still doesn't handle all the cases, namely when the last slots are gone (consistent hashing is supposed to be good for this?); however for that we'd need more involved coordination between nodes or a central updater to indicate the number of nodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)