Hello all!
I'm interested in Storm on Mesos, but my coworkers don't wanna be guinea
pigs. Is anyone using mesos/storm https://github.com/mesos/storm in
production? I see the repo is at least active. :)
--
Cory Watson
Principal Infrastructure Engineer // Keen IO
Hi All,
I'm running into a weird issue with my test mesos cluster, I have a 3
master / 3 slave HA configuration. Marathon and Chronos are working as they
should and I can deploy dockerized applications to the slave nodes without
issue using Marathon. I downloaded Spark 1.2 and built from source.
+1
so excited for the persistence primitives, awesome!
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop
definite +1, lets keep the release rhythm going!
maybe some space on the wiki for release planning / release managers would
be a step forward
On Tue, Jan 20, 2015 at 1:59 PM, Joe Stein joe.st...@stealth.ly wrote:
+1
so excited for the persistence primitives, awesome!
Hi Dave,
Sorry about the blog post, I lost track of it in the middle of other tasks.
I'm going to update the website and the blog post very soon.
Tim
On Tue, Jan 20, 2015 at 12:37 PM, Dave Lester d...@davelester.org wrote:
Thanks Niklas for kicking off this thread. +1 to you as release
+1
@vinodkone
On Jan 20, 2015, at 12:03 PM, Chris Aniszczyk z...@twitter.com wrote:
definite +1, lets keep the release rhythm going!
maybe some space on the wiki for release planning / release managers would be
a step forward
On Tue, Jan 20, 2015 at 1:59 PM, Joe Stein
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
On 20/01/2015 20:00, Manivannan wrote:
+1
On Wed, Jan 21, 2015 at 7:04 AM, Vinod Kone vinodk...@gmail.com
mailto:vinodk...@gmail.com wrote:
+1
@vinodkone
On Jan 20, 2015, at 12:03 PM, Chris Aniszczyk z...@twitter.com
On Tue, Jan 20, 2015 at 4:10 PM, Vinod Kone vinodk...@gmail.com wrote:
Thanks for the interest. The next meeting will be on 5th February, 3-5 pm
PST.
The hangout link:
https://plus.google.com/hangouts/_/twitter.com/mesos-sync
On Tue, Jan 6, 2015 at 9:13 AM, Tim St Clair tstcl...@redhat.com
+1
On Wed, Jan 21, 2015 at 7:04 AM, Vinod Kone vinodk...@gmail.com wrote:
+1
@vinodkone
On Jan 20, 2015, at 12:03 PM, Chris Aniszczyk z...@twitter.com wrote:
definite +1, lets keep the release rhythm going!
maybe some space on the wiki for release planning / release managers would
be
I want to know what the executor id will be set to prior to launching a
command when using the command executor in a custom framework. From what I
can see, if I was using a custom executor, then I could provide the
executor ID, but I don't see a way to do so when using the command executor.
See also the upcoming persistence primitives. Using persistent volumes (
MESOS-1554 https://issues.apache.org/jira/browse/MESOS-1554) and dynamic
reservations (MESOS-2018 https://issues.apache.org/jira/browse/MESOS-2018),
you can launch a task from one framework which creates a persistent volume
Found a likely problem in the fig.yml:
- MESOS_ISOLATOR=cgroups/cpu,groups/mem
That second part should be cgroups, not groups
Brenden, could you please elaborate a bit on those shortcomings :-)
On Tue, Jan 20, 2015 at 11:06 AM, Brenden Matthews bren...@diddyinc.com
wrote:
Hi Cory,
We were using the project in production at Airbnb. It may have some
shortcomings, but it does, in fact, work.
Hello all!
I'm
Thanks Niklas for kicking off this thread. +1 to you as release manager,
could you please create a JIRA ticket to track the progress so we could
subscribe?
A minor correction to your email, Mesos 0.21.1 was voted on in late
December (see http://markmail.org/message/e2iam7guxukl3r6c), however the
Hi Cory,
We were using the project in production at Airbnb. It may have some
shortcomings, but it does, in fact, work.
Hello all!
I'm interested in Storm on Mesos, but my coworkers don't wanna be guinea
pigs. Is anyone using mesos/storm https://github.com/mesos/storm in
production? I see
Hi all,
We have been releasing major versions of Mesos roughly every second month
(current average is ~66 days) and we are now 2 months after the 0.21.0
release, so I would like to propose that we start planning for 0.22.0
Not only in terms of timing, but also because we have some exciting
+1!
-John
On Tue, Jan 20, 2015 at 11:52 AM, Niklas Nielsen nik...@mesosphere.io
wrote:
Hi all,
We have been releasing major versions of Mesos roughly every second month
(current average is ~66 days) and we are now 2 months after the 0.21.0
release, so I would like to propose that we start
17 matches
Mail list logo