Folly Futures

2015-06-19 Thread Benjamin Mahler
Looks like facebook added Futures to folly: https://github.com/facebook/folly/tree/master/folly/futures Error handling is done through exceptions, and the executor is made explicit so that people can choose different execution models.

Re: Folly Futures

2015-06-19 Thread Benjamin Mahler
Blog post here: https://code.facebook.com/posts/1661982097368498 On Fri, Jun 19, 2015 at 3:15 PM, Benjamin Mahler benjamin.mah...@gmail.com wrote: Looks like facebook added Futures to folly: https://github.com/facebook/folly/tree/master/folly/futures Error handling is done through

Help required in doing Reregistration

2015-06-19 Thread Aditi Dixit
I0619 17:50:14.436782 29954 sched.cpp:448] Framework registered with 20150619-163754-16842879-5050-29356-0005 Registered with id20150619-163754-16842879-5050-29356-0005! Received offer 20150619-163754-16842879-5050-29356-O10 with mem(*):4892; disk(*):692933; ports(*):[31000-32000]; cpus(*):4 Launching

Re: Help required in doing Reregistration

2015-06-19 Thread Adam Bordelon
] Framework registered with 20150619-163754-16842879-5050-29356-0005 Registered with id20150619-163754-16842879-5050-29356-0005! Received offer 20150619-163754-16842879-5050-29356-O10 with mem(*):4892; disk(*):692933; ports(*):[31000-32000]; cpus(*):4 Launching task 0 using offer 20150619-163754

Re: Help required in doing Reregistration

2015-06-19 Thread haosdent
] No credentials provided. Attempting to register without authentication I0619 17:50:14.436782 29954 sched.cpp:448] Framework registered with 20150619-163754-16842879-5050-29356-0005 Registered with id20150619-163754-16842879-5050-29356-0005! Received offer 20150619-163754-16842879-5050-29356-O10

Re: Help required in doing Reregistration

2015-06-19 Thread Aditi Dixit
Hi, Thanks for the responses haosdent and Adam. I'm sorry if I wasn't clear enough, but yes, the patch exactly does what Adam just mentioned. We create 2 instances of the driver and in the second time, set the frameworkId in the FrameworkInfo to the id from when we register the first time, and

Re: Help required in doing Reregistration

2015-06-19 Thread haosdent
default failover_timeout is zero? On Sat, Jun 20, 2015 at 1:04 AM, Adam Bordelon a...@mesosphere.io wrote: Aha! You also need to set the FrameworkInfo.failover_timeout to a non-zero value. If it is 0, then Mesos will instantly shutdown your framework when the schedulerdriver disconnects. On

Re: Help required in doing Reregistration

2015-06-19 Thread Vinod Kone
Can you send us the gist? @vinodkone On Jun 19, 2015, at 8:49 AM, Aditi Dixit aditi96di...@gmail.com wrote: Hi, Thanks for the responses haosdent and Adam. I'm sorry if I wasn't clear enough, but yes, the patch exactly does what Adam just mentioned. We create 2 instances of the driver

Re: Help required in doing Reregistration

2015-06-19 Thread Aditi Dixit
Sure. You can find the modified test_framework.cpp here : https://gist.github.com/atidix/8ebadf460634bbd23d71 On Fri, Jun 19, 2015 at 10:01 PM, Vinod Kone vinodk...@gmail.com wrote: Can you send us the gist? @vinodkone On Jun 19, 2015, at 8:49 AM, Aditi Dixit aditi96di...@gmail.com wrote:

Re: Help required in doing Reregistration

2015-06-19 Thread Adam Bordelon
Aha! You also need to set the FrameworkInfo.failover_timeout to a non-zero value. If it is 0, then Mesos will instantly shutdown your framework when the schedulerdriver disconnects. On Fri, Jun 19, 2015 at 9:56 AM, haosdent haosd...@gmail.com wrote: From you gist, I think `reregistered` would

Re: Help required in doing Reregistration

2015-06-19 Thread haosdent
LoL. If not set, it is zero. Ignore my previous response, sorry. @Aditi On Sat, Jun 20, 2015 at 1:11 AM, haosdent haosd...@gmail.com wrote: default failover_timeout is zero? On Sat, Jun 20, 2015 at 1:04 AM, Adam Bordelon a...@mesosphere.io wrote: Aha! You also need to set the