Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-14132

Filesystem discovery to stop loading implementation classes



    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.7.3
    • Fix Version/s: None
    • Component/s: fs, fs/adl, fs/azure, fs/oss, fs/s3, fs/swift
    • Labels:
    • Target Version/s:


      Integration testing of Hadoop with the HADOOP-14040 has shown up that the move to a shaded AWS JAR is slowing all hadoop client code down.

      I believe this is due to how we use service discovery to identify FS implementations: the implementation classes themselves are instantiated.
      This has known problems today with classloading, but clearly impacts performance too, especially with complex transitive dependencies unique to the loaded class.

      Proposed: have lightweight service declaration classes which implement an interface declaring

      1. schema
      2. classname of FileSystem impl
      3. classname of AbstractFS impl
      4. homepage (for third party code, support, etc)

      These are what we register and scan in the FS to look for services.

      This will leave the question about what to do for existing filesystems? I think we'll need to retain the old code for external ones, while moving the hadoop modules to the new ones


          Issue Links



              • Assignee:
                stevel@apache.org Steve Loughran
                stevel@apache.org Steve Loughran
              • Votes:
                1 Vote for this issue
                14 Start watching this issue


                • Created: