[
https://issues.apache.org/jira/browse/YARN-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274494#comment-16274494
]
Jason Lowe commented on YARN-7595:
----------------------------------
This code pattern appears in the following places related to container launch:
* DefaultContainerExecutor.LocalWrapperScriptBuilder#writeLocalWrapperScript
* DefaultContainerExecutor.UnixLocalWrapperScriptBuilder#writeSessionScript
* ContainerLaunch#call
* JavaSandboxLinuxContainerRuntime#prepareContainer
> Container launching code suppresses close exceptions after writes
> -----------------------------------------------------------------
>
> Key: YARN-7595
> URL: https://issues.apache.org/jira/browse/YARN-7595
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Jason Lowe
>
> There are a number of places in code related to container launching where the
> following pattern is used:
> {code}
> try {
> ...write to stream outStream...
> } finally {
> IOUtils.cleanupWithLogger(LOG, outStream);
> }
> {code}
> Unfortunately this suppresses any IOException that occurs during the close()
> method on outStream. If the stream is buffered or could otherwise fail to
> finish writing the file when trying to close then this can lead to
> partial/corrupted data without throwing an I/O error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
