hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bibin A Chundatt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15523) Shell command timeout given is in seconds whereas it is taken as millisec while scheduling
Date Fri, 08 Jun 2018 04:23:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505686#comment-16505686

Bibin A Chundatt commented on HADOOP-15523:


Please do handle the following as part for the patch 

# javadoc update for Shell#getTimeoutInterval
     * Returns the timeout value set for the executor's sub-commands.
     * @return The timeout value in seconds
    public long getTimeoutInterval() {
      return timeOutInterval;
# Add/Update the testcase added as part of HADOOP-13817 too.

> Shell command timeout given is in seconds whereas it is taken as millisec while scheduling
> ------------------------------------------------------------------------------------------
>                 Key: HADOOP-15523
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15523
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Bilwa S T
>            Assignee: Bilwa S T
>            Priority: Major
> ShellBasedUnixGroupsMapping has a property {{hadoop.security.groups.shell.command.timeout}} to
control how long to wait for the fetch groups command which can be configured in seconds.
but while scheduling the time taken is millisecs. so currently if u give value as 60s, it
is taken as 60ms.
> {code:java}
> timeout = conf.getTimeDuration(
> CommonConfigurationKeys.
> CommonConfigurationKeys.
> TimeUnit.SECONDS);{code}
> Time unit given is in seconds but it should be millisecs

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message