[
https://issues.apache.org/jira/browse/OOZIE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042256#comment-15042256
]
Robert Kanter commented on OOZIE-2402:
--------------------------------------
Thanks for making the changes. Though it looks like my #4 comment was missed:
{quote}
It would be nice if checkCopyResults could print out the exception for each
failure, instead of just one. Otherwise, if there are multiple problems, the
user will have to keep trying after resolving each issue.
{quote}
Can you do that too? I think if you might just have to remove the {{break;}}
statements.
> oozie-setup.sh sharelib create takes a long time on large clusters
> ------------------------------------------------------------------
>
> Key: OOZIE-2402
> URL: https://issues.apache.org/jira/browse/OOZIE-2402
> Project: Oozie
> Issue Type: Improvement
> Components: tools
> Affects Versions: 4.2.0
> Reporter: Illya Yalovyy
> Assignee: Illya Yalovyy
> Attachments: OOZIE-2402-1.patch, OOZIE-2402-2.patch,
> OOZIE-2402-3.patch
>
>
> When cluster has 256+ nodes it can take up to 5 minutes to create a sharelib.
> Copy the tarball itself takes only around 10 seconds. It seems like
> performance could be improved by loading files concurrently in many threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
