atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-834) Handle exceptions from HiveHook executor.submit()
Date Sat, 28 May 2016 02:57:12 GMT

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

Shwetha G S commented on ATLAS-834:
-----------------------------------

+1

> Handle exceptions from HiveHook executor.submit()
> -------------------------------------------------
>
>                 Key: ATLAS-834
>                 URL: https://issues.apache.org/jira/browse/ATLAS-834
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.6-incubating, 0.7-incubating
>            Reporter: Shwetha G S
>            Assignee: Suma Shivaprasad
>            Priority: Critical
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-834.patch
>
>
> Atlas hive hook uses threadpool with fixed queue size(to restrict memory). In cases of
high load, all threads may be busy and queue may be full in which case, threadpool.submit()
fails and hive command execution fails. We should ignore this failure(will result in loss
of data for atlas, but we don't have any store forward solution) and let the hive command
execution complete.



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

Mime
View raw message