tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From László Bodor (Jira) <j...@apache.org>
Subject [jira] [Updated] (TEZ-4081) Container release idle timeout exception for equal min and max values
Date Sat, 25 Jan 2020 00:43:00 GMT

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

László Bodor updated TEZ-4081:
------------------------------
    Attachment:     (was: TEZ-4081.01.patch)

> Container release idle timeout exception for equal min and max values
> ---------------------------------------------------------------------
>
>                 Key: TEZ-4081
>                 URL: https://issues.apache.org/jira/browse/TEZ-4081
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jonathan Turner Eagles
>            Assignee: László Bodor
>            Priority: Major
>         Attachments: TEZ-4081.01.patch
>
>
> Documentation is that Max must be greater than or equal to the minimum values.
> {code}
>   /**
>    * Int value. The maximum amount of time to hold on to a container if no task can be
>    * assigned to it immediately. Only active when reuse is enabled. The value
>    * must be +ve and >=
>    * TezConfiguration#TEZ_AM_CONTAINER_IDLE_RELEASE_TIMEOUT_MIN_MILLIS.
>    * Containers will have an expire time set to a random value between
>    * TezConfiguration#TEZ_AM_CONTAINER_IDLE_RELEASE_TIMEOUT_MIN_MILLIS &&
>    * TezConfiguration#TEZ_AM_CONTAINER_IDLE_RELEASE_TIMEOUT_MAX_MILLIS. This
>    * creates a graceful reduction in the amount of idle resources held
>    */
>   @ConfigurationScope(Scope.AM)
>   @ConfigurationProperty(type="long")
>   public static final String TEZ_AM_CONTAINER_IDLE_RELEASE_TIMEOUT_MAX_MILLIS =
>       TEZ_AM_PREFIX + "container.idle.release-timeout-max.millis";
>   public static final long
>     TEZ_AM_CONTAINER_IDLE_RELEASE_TIMEOUT_MAX_MILLIS_DEFAULT = 10000l;
> {code}
> Yet equal values of min and max cause this exception.
> {code}
> Service Error: Error in TaskScheduler for handling Task De-allocation, eventType=S_TA_ENDED,
scheduler=[0:TezYarn], taskAttemptId=attempt_1564035733375_382652_1_00_000051_0, eventType=TASK_SCHEDULER_SERVICE_FATAL_ERROR,
exception=org.apache.commons.math3.exception.NumberIsTooLargeException: lower bound (60,000)
must be strictly less than upper bound (60,000)
> {code}



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

Mime
View raw message