[ https://issues.apache.org/jira/browse/HADOOP-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809019#comment-17809019 ]
Shilun Fan edited comment on HADOOP-18636 at 1/21/24 3:38 PM: -------------------------------------------------------------- -3.3.6 release has been fixed, fix version removed 3.4.0.- was (Author: slfan1989): 3.3.6 release has been fixed, fix version removed 3.4.0. > LocalDirAllocator cannot recover from directory tree deletion during the life > of a filesystem client > ---------------------------------------------------------------------------------------------------- > > Key: HADOOP-18636 > URL: https://issues.apache.org/jira/browse/HADOOP-18636 > Project: Hadoop Common > Issue Type: Bug > Components: fs, fs/azure, fs/s3 > Affects Versions: 3.3.4 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Labels: pull-request-available > Fix For: 3.4.0, 3.3.6 > > > The s3a and abfs clients use LocalDirAllocator for allocating files in local > (temporary) storage for buffering blocks to write, and, for the s3a staging > committer, files being staged. > When initialized (or when the configuration key value is updated) > LocalDirAllocator enumerates all directories in the list and calls > {{mkdirs()}} to create them. > when you ask actually for a file, it will look for the parent dir, and will > again call {{mkdirs()}}. > But before it does that, it looks to see if the dir has any space...if not it > is excluded from the list of directories with room for data. > And guess what: directories which don't exist report as having no space. So > they get excluded -the recreation code doesn't get a chance to run. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org