[jira] [Commented] (TEZ-4228) TezClassLoader should be used in TezChild and for Configuration objects

["László Bodor (Jira)" <ji...@apache.org>]

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

László Bodor commented on TEZ-4228:
-----------------------------------

cc: [~harishjp], [~rbalamohan]: could you please take a look at this patch?
simple fix, which should go into 0.10.0

> TezClassLoader should be used in TezChild and for Configuration objects
> -----------------------------------------------------------------------
>
>                 Key: TEZ-4228
>                 URL: https://issues.apache.org/jira/browse/TEZ-4228
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Blocker
>              Labels: 0.10_blocker
>             Fix For: 0.10.0
>
>         Attachments: TEZ-4228.01.patch, hive_llap.log, syslog_bad.log, syslog_good.log
>
>
> While testing a 0.10.0 staging artifact, I found that there are 2 issues of TEZ-3860/TEZ-4223, which should be fixed before 0.10.0 release. The issues came up while hive precommit tests:
> http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1311/11/tests
> 1. TezClassLoader static initialization is not deterministic, or at least it seems like LogicalIOProcessorRuntimeTask.run can before it. See "tez classloader" log messages in  [^syslog_bad.log] . The changes in TezChild solved the problem as  [^syslog_good.log] 
> 2. Configuration objects have their own classloader, which should be overridden with TezClassLoader, otherwise they won't find newly added classes, issue in  [^hive_llap.log] . This one is being solved within TezUtils methods.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)