You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jonathan Turner Eagles (Jira)" <ji...@apache.org> on 2020/07/16 15:36:00 UTC

[jira] [Commented] (TEZ-4186) Limits: Fix init order regression from TEZ-4155

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

Jonathan Turner Eagles commented on TEZ-4186:
---------------------------------------------

Cherry-picked to branch-0.9. Committers don't forget branch-0.9 is an actively supported line in Tez. Had a user report counter limits can be changed through configuration from the default (TEZ-4155) in a 0.9.x based release. Trying to verify this jira fixes the issue or not.

> Limits: Fix init order regression from TEZ-4155
> -----------------------------------------------
>
>                 Key: TEZ-4186
>                 URL: https://issues.apache.org/jira/browse/TEZ-4186
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.10.1
>            Reporter: Gopal Vijayaraghavan
>            Assignee: Gopal Vijayaraghavan
>            Priority: Major
>             Fix For: 0.10.0, 0.9.3
>
>         Attachments: TEZ-4186.1.patch, TEZ-4186.2.patch
>
>
> After TEZ-4155, the AM is not able to configure Limits parameters correctly, due to the following interaction.
> {code}
>   static {
>     init(new TezConfiguration());
>   }
> {code}
> prevents setConfiguration from doing anything
> {code}
>   public synchronized static void setConfiguration(Configuration conf) {
>     if (Limits.conf == null && conf != null) {
>       init(conf);
>     }
>   }
> {code}
> since the Limits.conf is never null.



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