[ https://issues.apache.org/jira/browse/SPARK-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267419#comment-14267419 ]
Patrick Wendell commented on SPARK-1529: ---------------------------------------- Hey Sean, >From what I remember of this, the issue is that MapR clusters are not >typically provisioned with much local disk space available, because the MapRFS >supports accessing "local" volumes in its API, unlike the HDFS API. So in >general the expectation is that large amounts of local data should be written >through MapR's API to its local filesystem. They have an NFS mount you can use >as a work around to provide POSIX API's, and I think most MapR users set this >mount up and then have Spark write shuffle data there. Option 2 which [~rkannan82] mentions is not actually feasible in Spark right now. We don't support writing shuffle data through the Hadoop API's right now and I think Cheng's patch was only a prototype of how we might do that... > Support setting spark.local.dirs to a hadoop FileSystem > -------------------------------------------------------- > > Key: SPARK-1529 > URL: https://issues.apache.org/jira/browse/SPARK-1529 > Project: Spark > Issue Type: Bug > Components: Spark Core > Reporter: Patrick Wendell > Assignee: Cheng Lian > > In some environments, like with MapR, local volumes are accessed through the > Hadoop filesystem interface. We should allow setting spark.local.dir to a > Hadoop filesystem location. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org