[ https://issues.apache.org/jira/browse/YARN-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184092#comment-16184092 ]
Sunil G commented on YARN-7244: ------------------------------- bq.the aux service doesn't even have to manage the directories itself if all it cares about is finding a place to write or read Yes. Thats perfectly fine. Thank you very much for clarifying. One more thought here, currently ShuffleHandler creates *LocalDirAllocator* and use that to get the better dirs to operate on. LocalDirHandlerService is not used by ShuffleHandler to now. I think we might not need LocalDirHandlerService , rather a new api as you mentioned in LocalDirAllocator named *getLocalDirsForRead* could enough to get valid dirs as it pulls all configured NM_LOCAL_DIRS and validates same. > ShuffleHandler is not aware of disks that are added > --------------------------------------------------- > > Key: YARN-7244 > URL: https://issues.apache.org/jira/browse/YARN-7244 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Kuhu Shukla > Assignee: Kuhu Shukla > Attachments: YARN-7244.001.patch, YARN-7244.002.patch > > > The ShuffleHandler permanently remembers the list of "good" disks on NM > startup. If disks later are added to the node then map tasks will start using > them but the ShuffleHandler will not be aware of them. The end result is that > the data cannot be shuffled from the node leading to fetch failures and > re-runs of the map tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org