[
https://issues.apache.org/jira/browse/SAMZA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030767#comment-14030767
]
Chris Riccomini commented on SAMZA-276:
---------------------------------------
Do we need the if/fi block, or can we just always call `mkdir -p`? Seems to be
fine to call `mkdir -p` on a directory that already exists.
{noformat}
-p Create intermediate directories as required. If this option is
not specified, the full path prefix of each operand must already
exist. On the other hand, with this option specified, no error
will be reported if a directory given as an operand already
exists. Intermediate directories are created with permission
bits of rwxrwxrwx (0777) as modified by the current umask, plus
write and search permission for the owner.
{noformat}
This seems to work:
{noformat}
criccomi-mn:tmp criccomi$ ls foobarbaz
ls: foobarbaz: No such file or directory
criccomi-mn:tmp criccomi$ mkdir -p foobarbaz
criccomi-mn:tmp criccomi$ ls foobarbaz
criccomi-mn:tmp criccomi$ mkdir -p foobarbaz
{noformat}
> Set -Djava.io.tmpdir to be usercache dir in YARN
> ------------------------------------------------
>
> Key: SAMZA-276
> URL: https://issues.apache.org/jira/browse/SAMZA-276
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Yan Fang
> Fix For: 0.8.0
>
> Attachments: SAMZA-276.1.patch, SAMZA-276.patch
>
>
> I don't believe we set -Djava.io.tmpdir in any of our shell scripts right
> now. When running Samza jobs in YARN, we should set -Djava.io.tmpdir to be
> the usercache directory or ./tmp or something, not /tmp on the root mount.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
