FAQ
SecureIO should not check owner on non-secure clusters that have no native support
----------------------------------------------------------------------------------

Key: HADOOP-7172
URL: https://issues.apache.org/jira/browse/HADOOP-7172
Project: Hadoop Common
Issue Type: Bug
Components: io, security
Affects Versions: 0.22.0
Reporter: Todd Lipcon
Priority: Critical
Fix For: 0.22.0


The SecureIOUtils.openForRead function currently uses a racy stat/open combo if security is disabled and the native libraries are not available. This ends up shelling out to "ls -ld" which is very very slow. We've seen this cause significant performance regressions on clusters that match this profile.

Since the racy permissions check doesn't buy us any security anyway, we should just fall back to a normal "open" without any stat() at all, if we can't use the native support to do it efficiently.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedMar 8, '11 at 8:17a
activeMar 8, '11 at 8:17a
posts1
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Todd Lipcon (JIRA): 1 post

People

Translate

site design / logo © 2022 Grokbase