Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-7172

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 0.22.0
    • Fix Version/s: 0.22.0, 0.23.0
    • Component/s: io, security
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      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.

        Attachments

        1. hadoop-7172.txt
          3 kB
          Todd Lipcon
        2. hadoop-7172.txt
          3 kB
          Todd Lipcon
        3. hadoop-7172.txt
          2 kB
          Todd Lipcon

          Issue Links

            Activity

              People

              • Assignee:
                tlipcon Todd Lipcon
                Reporter:
                tlipcon Todd Lipcon
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: