hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17195) Long chain of tasks created by REPL LOAD shouldn't cause stack corruption.
Date Wed, 16 Aug 2017 17:58:00 GMT

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

Thejas M Nair commented on HIVE-17195:
--------------------------------------

+1
The cleanup of older code can be done in a follow up patch. I will create another jira for
that. Lets not get perfect come in the way of good.


> Long chain of tasks created by REPL LOAD shouldn't cause stack corruption.
> --------------------------------------------------------------------------
>
>                 Key: HIVE-17195
>                 URL: https://issues.apache.org/jira/browse/HIVE-17195
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DAG, DR, Executor, replication
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17195.01.patch, HIVE-17195.02.patch
>
>
> Currently, long chain REPL LOAD tasks lead to huge recursive calls when try to traverse
the DAG.
> For example, getMRTasks, getTezTasks, getSparkTasks and iterateTasks methods run recursively
to traverse the DAG.
> Need to modify this traversal logic to reduce stack usage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message