You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2016/05/27 18:50:13 UTC

[jira] [Updated] (ATLAS-834) Handle exceptions from HiveHook executor.submit()

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

Shwetha G S updated ATLAS-834:
------------------------------
    Assignee: Suma Shivaprasad

> Handle exceptions from HiveHook executor.submit()
> -------------------------------------------------
>
>                 Key: ATLAS-834
>                 URL: https://issues.apache.org/jira/browse/ATLAS-834
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Suma Shivaprasad
>            Priority: Critical
>             Fix For: 0.7-incubating
>
>
> 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)