Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Feb 2017 18:35:41 +0000 (UTC)
From: "Wei-Chiu Chuang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13020487.1479124141000.102104.1487270141652@Atlassian.JIRA>
In-Reply-To: <JIRA.13020487.1479124141000@Atlassian.JIRA>
References: <JIRA.13020487.1479124141000@Atlassian.JIRA> <JIRA.13020487.1479124141829@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-13817) Add a finite shell command
 timeout to ShellBasedUnixGroupsMapping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Feb 2017 18:35:49 -0000


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

Wei-Chiu Chuang commented on HADOOP-13817:
------------------------------------------

Okay I did a quick review and there were only two nits after Xiaoyu's numerous reviews.
By the way, Yetus does not support precommit check if the patch is a github pull request, right? I am not sure how to make that happen... Maybe attach a patch into this jira would trigger that.

> Add a finite shell command timeout to ShellBasedUnixGroupsMapping
> -----------------------------------------------------------------
>
>                 Key: HADOOP-13817
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13817
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>
> The ShellBasedUnixGroupsMapping run various {{id}} commands via the ShellCommandExecutor modules without a timeout set (its set to 0, which implies infinite).
> If this command hangs for a long time on the OS end due to an unresponsive groups backend or other reasons, it also blocks the handlers that use it on the NameNode (or other services that use this class). That inadvertently causes odd timeout troubles on the client end where its forced to retry (only to likely run into such hangs again with every attempt until at least one command returns).
> It would be helpful to have a finite command timeout after which we may give up on the command and return the result equivalent of no groups found.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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