You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2014/09/13 00:06:33 UTC
[jira] [Commented] (TEZ-1524) getDAGStatus seems to fork out the
entire JVM on non-secure clusters
[ https://issues.apache.org/jira/browse/TEZ-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132201#comment-14132201 ]
Gopal V commented on TEZ-1524:
------------------------------
commit edb841c08de123ff2c5ace0662ae78bf3c58f2c0
Author: Gopal V <go...@apache.org>
Date: Fri Sep 12 15:04:32 2014 -0700
TEZ-1524. Resolve user group information only if ACLs are enabled (gopalv)
Thanks [~hitesh]!
> getDAGStatus seems to fork out the entire JVM on non-secure clusters
> --------------------------------------------------------------------
>
> Key: TEZ-1524
> URL: https://issues.apache.org/jira/browse/TEZ-1524
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Gopal V
> Assignee: Gopal V
> Attachments: TEZ-1524.1.patch, TEZ-1524.2.patch, TEZ-1524.3.patch
>
>
> Tracked down a consistent fork() call to
> {code}
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:505)
> at org.apache.hadoop.util.Shell.run(Shell.java:418)
> at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:650)
> at org.apache.hadoop.util.Shell.execCommand(Shell.java:739)
> at org.apache.hadoop.util.Shell.execCommand(Shell.java:722)
> at org.apache.hadoop.security.ShellBasedUnixGroupsMapping.getUnixGroups(ShellBasedUnixGroupsMapping.java:83)
> at org.apache.hadoop.security.ShellBasedUnixGroupsMapping.getGroups(ShellBasedUnixGroupsMapping.java:52)
> at org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback.getGroups(JniBasedUnixGroupsMappingWithFallback.java:50)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:139)
> at org.apache.hadoop.security.UserGroupInformation.getGroupNames(UserGroupInformation.java:1409)
> at org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.getRPCUserGroups(DAGClientAMProtocolBlockingPBServerImpl.java:75)
> at org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.getDAGStatus(DAGClientAMProtocolBlockingPBServerImpl.java:102)
> at org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolRPC$DAGClientAMProtocol$2.callBlockingMethod(DAGClientAMProtocolRPC.java:7375)
> {code}
> [~hitesh] - would it make sense to cache this at all?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)