I ran into an issue when tried Mesos 0.26 version and started a marathon app using URI (with maprfs path) on a mesos cluster.
The issue seems to be caused by Mesos-3602 fix, and is causing issue for maprfs (mapr filesystem) when specified maprfs path as URI on marathon. The issue is that, It is appending '/' to the URI maprfs path specified, in the beginning, and is not executed as expected. e.g. ===== * hadoop fs -copyToLocal '/maprfs:///dist/hadoop-2.7.0.myriad1.tar.gz' '/opt/mapr/slaves/67d1f64c-449b-4609-82f3-5da309f3c5c5-S9/frameworks/67d1f64c-449b-4609-82f3-5da309f3c5c5-0000/executors/myriad1.63bbb98c-c072-11e5-b686-0cc47a587d20/runs/427fe309-82c5-4f8b-9fa3-6dd39a4a5ef4/hadoop-2.7.0.myriad1.tar.gz* -copyToLocal: java.net.URISyntaxException: Expected scheme-specific part at index 7: maprfs: ===== The fix for Mesos-3602 only assumes hdfs path, and doesn't consider other cases, such as maprfs or other dfs paths. I haven't filed a JIRA yet on this issue, but would like to get some feedback on this, and expect this to be fixed for next Mesos release. Let me know if there is anything else I could provide related to the issue. -Sarjeet On Sat, Jan 23, 2016 at 12:41 AM, Timothy Chen <[email protected]> wrote: > Hi all, > > (Kapil, MPark and I) We're still having 3 blocker issues outstanding > at this moment: > > MESOS-4449: SegFault on agent during executor startup (shepherd: Joris) > MESOS-4441: Do not allocate non-revocable resources beyond quota > guarantee. (shepherd: Joris) > MESOS-4410: Introduce protobuf for quota set request. (shepherd: Joris) > > The remaining major tickets are ContainerLogger related and should be > committed today according to Ben. > > We've started to test latest master and will be looking at the test > failures to see what needs to be addressed. > > I encourage everyone to test the latest master on your platform if > possible to catch issues early, and once the Blocker issues are > resolved we'll be sending a RC to test and vote. > > Thanks, > > Tim >
