@cwensel the @cascading 2.5 release notes claim to support YARN, but all the artifacts are for hadoop2-mr1. Is there any MR2 support?
@cwensel ok, I'd love to hear more about this setup. @squarecog any pointers?
-
-
@avibryant@cwensel I have no idea on mr1 vs mr2, but we are running cascading/scalding on MR in Yarn in production. -
@squarecog interesting. I *think* that's quite an unusual setup, and would love to hear more if you can point me to the right person. -
@avibryant we are running MR2 on yarn. I guess hadop2-mr1 is actually that? -
@squarecog MR2 on YARN makes sense. But Cascading won't run on MR2. So I'm still confused. -
@avibryant@squarecog I seems to me you're failing to take into account the possibly of dark magick playing a role here. -
@sorenmacbeth He writes stuff in Scala all the time. Of course he's factored in dark magic.@avibryant -
@meangrape@avibryant scala isn't dark magic; it is an abomination. - 1 more reply
New conversation -
-
-
@avibryant@cwensel@squarecog if you set-up an apache hadoop 2 cluster, cascading 2.5 works totally fine. No idea, what cloudera is doing. -
@fs111@avibryant I think one of you means hadoop1 vs. hadoop2 and one of you means mapred.* vs. mapreduce.* when you say MR1/MR2. -
@josh_wills@fs111@squarecog this was useful (and news to me): http://hortonworks.com/blog/running-existing-applications-on-hadoop-2-yarn/ … (mapred.* apps should be binary compat with YARN) -
@avibryant@josh_wills@fs111 oh. yeah. mr-on-yarn is usually referred to as mr2, but I think@cwensel means o.a.h.mapred vs mapreduce here -
@squarecog@avibryant@josh_wills@fs111 yep, just had the same convo and@cwensel confirmed i.e. it's o.a.h.mapred.* on YARN
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.