[HDFS-5329] Update FSNamesystem#getListing() to handle inode path in startAfter token

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Component/s: namenode, nfs
• Hadoop Flags: Reviewed
• Assignee: Brandon Li
• Reporter: Brandon Li
• Created: 09/Oct/13 07:35
• Updated: 24/Feb/14 20:56
• Resolved: 13/Oct/13 06:29

Description

This is to support network protocols which can't use file name as the token to resume directory listing.

NFS gateway doesn't know the name of startAfter and has to use inode id instead. NFS protocol uses readdir and readdirplus to list directory content. In the response, each dirent has an 8-byte number verifier.

To list the content of large directories, NFS client sends multiple readdir or readdirplus requests to NFS gateway with one verifier(resume point) in the request. The verifier is basically of the same usage as "startAfter" in getListing. Since NFSv3 uses file handle to communicate and doesn't know the file name. NFS gateway has to use the inode id path as "startAfter" when sending getList request to NN, however NN currently expects "startAfter" to be just a file name. As a result, NFS gateway can't list the content of large directories.

Issue Links

• blocks: HDFS-5330 fix readdir and readdirplus for large directories