Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

Question - running on the .net core #7

Open
joeblew99 opened this issue Apr 30, 2015 · 4 comments
Open

Question - running on the .net core #7

joeblew99 opened this issue Apr 30, 2015 · 4 comments

Comments

@joeblew99
Copy link

Now that .net core runs on Linux and plinq is included, that means that dryad could be effectively used on a massive compute cluster.

Seems like a very nice opportunity. Can anyone of the tram comment on this ?

https://github.com/dotnet/corefx

@RahulNET
Copy link

I agree with you joeblew99. I think it could be a very interesting opportunity to bring .NET into the game of Hadoop ecosystem. To be able to write YARN aware programs in PLINQ could be really powerful similar to Cascading or Cascalog. I would be very keen to contribute on this. Let me know.

@frankmcsherry
Copy link

Microsoft Research closed the lab that produced this work last September. The team members are now mostly at Google, and (I think) probably not in a position to develop or support Microsoft projects.

When we left, both Dryad and Naiad ran just fine on Yarn clusters and worked just fine with HDFS. If you have more questions, I recommend getting in touch with someone at Microsoft. I suspect Mark Staveley could give you a definitive thumbs up / thumbs down signal.

But, good to hear that you like what the lab did.

@joeblew99
Copy link
Author

Well since then things have moved on. I am developing 100% of the stack in
golang.

Its going very well. Go can run on android and ios now. On the server side
its very easy.
.the garbage collector is my main hurdle

J
On 14 May 2015 17:30, "Frank McSherry" notifications@github.com wrote:

Microsoft Research closed the lab that produced this work last September.
The team members are now mostly at Google, and (I think) probably not in a
position to develop or support Microsoft projects.

When we left, both Dryad and Naiad ran just fine on Yarn clusters and
worked just fine with HDFS. If you have more questions, I recommend getting
in touch with someone at Microsoft. I suspect Mark Staveley could give you
a definitive thumbs up / thumbs down signal.

But, good to hear that you like what the lab did.


Reply to this email directly or view it on GitHub
#7 (comment)
.

@michaelisard
Copy link
Contributor

In case anyone else is interested in returning to the codebase: as Frank says, things run pretty smoothly today on YARN, but only on Windows. The problem running on Linux is that Dryad and the YARN interop layer both include managed C++. I have not been following closely, but it used to be difficult to get managed C++ to work on Linux without some porting effort, and nobody to my knowledge has tried to do that.

I don’t think Mark Staveley is in a role to support this stuff any more, and I don’t know of anyone else at Microsoft who has picked it up. Someone could always fork the code…

From: joeblew99 [mailto:notifications@github.com]
Sent: May 14, 2015 9:58 AM
To: MicrosoftResearch/Dryad
Subject: Re: [Dryad] Question - running on the .net core (#7)

Well since then things have moved on. I am developing 100% of the stack in
golang.

Its going very well. Go can run on android and ios now. On the server side
its very easy.
.the garbage collector is my main hurdle

J
On 14 May 2015 17:30, "Frank McSherry" notifications@github.com wrote:

Microsoft Research closed the lab that produced this work last September.
The team members are now mostly at Google, and (I think) probably not in a
position to develop or support Microsoft projects.

When we left, both Dryad and Naiad ran just fine on Yarn clusters and
worked just fine with HDFS. If you have more questions, I recommend getting
in touch with someone at Microsoft. I suspect Mark Staveley could give you
a definitive thumbs up / thumbs down signal.

But, good to hear that you like what the lab did.


Reply to this email directly or view it on GitHub
#7 (comment)
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-102102340.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants