Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5194 Robust support for alternate FsDatasetSpi implementations
  3. HDFS-7680

Support dataset-specific choice of short circuit implementation

Add voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.0.0-alpha1
    • None
    • datanode, hdfs-client
    • None

    Description

      As described in HDFS-5194, the current support for short circuit reading is tightly coupled to the default Dataset implementation. Since alternative implementations of the FsDatasetSpi may use a different short circuit pathway, there needs to be a way for the client to acquire the right kind of BlockReader.

      Reviewing some considerations:
      Today, there is only one dataset per datanode (with multiple volumes). Is that likely to change?
      Can there be multiple datanodes local to a client? (definition of "local" might depend on dataset implementation)
      Is it okay to assume that the client and datanode share configuration? More broadly, how should the client discover the appropriate short-circuit implementation?

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jpallas Joe Pallas
            jpallas Joe Pallas

            Dates

              Created:
              Updated:

              Slack

                Issue deployment