You will be scalesimilated.
Large-scale cluster management at Google with Borg
21–30 of 37 posts
Re: Large-scale cluster management at Google with Borg
#22Oh, fun, they finally published this. How many times I've had to catch myself from saying the word "Borg" I don't even know. The performance isolation is good, but I wouldn't really seek after high utilization unless compute costs are significant to your business. We've seen some crazy things where nominally non-interfering jobs cause significant performance degradation to other jobs on the same node. There's work ye…
Why is everyone acting like the name was some big secret? Everyone who has been using Mesos knows Borg, for crying out loud, big writeups were published in Wired and The Verge over 2 years ago!
Re: Large-scale cluster management at Google with Borg
#23Is this similar in concept to Oracle Grid Engine (SGE)? How is it different, superior?
SGE = Sun Grid Engine, I'm guessing?
Re: Large-scale cluster management at Google with Borg
#24Re: Large-scale cluster management at Google with Borg
#25Oh, fun, they finally published this. How many times I've had to catch myself from saying the word "Borg" I don't even know. The performance isolation is good, but I wouldn't really seek after high utilization unless compute costs are significant to your business. We've seen some crazy things where nominally non-interfering jobs cause significant performance degradation to other jobs on the same node. There's work ye…
Why is everyone acting like the name was some big secret? Everyone who has been using Mesos knows Borg, for crying out loud, big writeups were published in Wired and The Verge over 2 years ago!
It was a secret. You weren't allowed to mention borg outside Google. Note John Wilkes was generally careful about not saying the name was 'Borg' or acknowledging it as such and instead referred to 'Omega'.
Re: Large-scale cluster management at Google with Borg
#26> cc would be reachable via 50.jfoo.ubar.cc.borg.google.com. I've implemented similar at my current job, as that sort of naming is very convenient. http://www.boxever.com/using-google-apps-openid-connect-with... has a sketch of how to do this with Apache as a reverse proxy with Google Auth, though we're using a PAC file now going to a HTTPS forward proxy to avoid limitations of SSL wildcard certs.
Keep it up, Brian :-)
If that was the craziest thing I was doing, I'd be doing well :)
Re: Large-scale cluster management at Google with Borg
#27Earlier quoted context omitted.
Why is everyone acting like the name was some big secret? Everyone who has been using Mesos knows Borg, for crying out loud, big writeups were published in Wired and The Verge over 2 years ago!
It was a secret. You weren't allowed to mention borg outside Google. Note John Wilkes was generally careful about not saying the name was 'Borg' or acknowledging it as such and instead referred to 'Omega'.
Perhaps you were told it was secret. It was not secret. Here's one of the articles I was referring to. http://www.wired.com/2013/03/google-borg-twitter-mesos/ John Wilkes mentions Borg, acts coy about the name for some reason (seems like a pattern), and mentions Omega, its nascent replacement.
Re: Large-scale cluster management at Google with Borg
#28Earlier quoted context omitted.
It was a secret. You weren't allowed to mention borg outside Google. Note John Wilkes was generally careful about not saying the name was 'Borg' or acknowledging it as such and instead referred to 'Omega'.
Perhaps you were told it was secret. It was not secret. Here's one of the articles I was referring to. http://www.wired.com/2013/03/google-borg-twitter-mesos/ John Wilkes mentions Borg, acts coy about the name for some reason (seems like a pattern), and mentions Omega, its nascent replacement.
John does not mention Borg by name publicly (well, until the paper was published). That's what I meant (consistent with what I was replying to). The article you linked to confirms that.
"According to Wilkes, Google plans to publish a research paper on Borg (though he still won’t use the name). "
Wilkes won’t even call it Borg. “I prefer to call it the system that will not be named,"
(I work with John and have contributed to Borg)
Re: Large-scale cluster management at Google with Borg
#29Apache Yarn[1] looks like same thing as borg\omega. A plus point with Yarn is we can get our hands on it. [1] http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yar...
Yarn tries to do the same thing, but is quite different. It's skewed toward running short running jobs, like batch jobs, it was meant for hadoop and co after all. Borg/Omega seems more like a combination of Mesos at the scheduler layer and Marathon/Kubernetes on top. It's funny to see how many services they run on top of it though.
This is exactly right. Marathon or Kubernetes running on Mesos or Mesosphere's DCOS is functionally similar to Borg.
Re: Large-scale cluster management at Google with Borg
#30Oh, fun, they finally published this. How many times I've had to catch myself from saying the word "Borg" I don't even know. The performance isolation is good, but I wouldn't really seek after high utilization unless compute costs are significant to your business. We've seen some crazy things where nominally non-interfering jobs cause significant performance degradation to other jobs on the same node. There's work ye…
Why is everyone acting like the name was some big secret? Everyone who has been using Mesos knows Borg, for crying out loud, big writeups were published in Wired and The Verge over 2 years ago!
Whether I'm allowed to speak about a project's codename has little to do with whether it has been leaked through nonofficial channels.