Github user pankajarora12 commented on the pull request:
https://github.com/apache/spark/pull/4770#issuecomment-76057426
Also using multiple disks for each executor provides speed but failure of
any of the disk will fail all executors of that node.
on other hand using one disk per executor and having as many disks
available as there are executors will provide fault tolerant against disk
failures.
I think quite debatable.
On Thu, Feb 26, 2015 at 2:30 AM, Pankaj Arora <[email protected]>
wrote:
> I thought about that case too. Since we will be having many executors on
> one node. So yarn will use different local dir for launching each executor
> and that will use up other disks too.
>
> On Thu, Feb 26, 2015 at 1:39 AM, Marcelo Vanzin <[email protected]>
> wrote:
>
>> There is also a second thing that is broken by this patch:
>> YARN_LOCAL_DIRS can actually be multiple directories, as the name
>> implies. The BlockManager uses that to distribute shuffle files across
>> multiple disks, to speed things up. After this change, everything will
end
>> up on the same disk.
>>
>> â
>> Reply to this email directly or view it on GitHub
>> <https://github.com/apache/spark/pull/4770#issuecomment-76045346>.
>>
>
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
