Hey Tim,
I can see your point, and am finding it hard to think of any compelling
arguments against the issue of fragmentation, but I do have a few thoughts.p
That said, I would strongly suggest taking ease-of-use and language
specific code structures into consideration. A huge monolithic build sy
whats the best way to update mesos master instances. eg I want to update
things in there, install new frameworks, but at the moment I am ssh'ing to
the instances and installing them one by one. that feels wrong, shouldnt it
be done in parallel to all the instances?
what do people currently do to k
You want a rolling restart i'd guess, unless you want downtime for some reason.
We use Ansible, it's pretty nice.
On 15 July 2014 10:47, Nayeem Syed wrote:
> whats the best way to update mesos master instances. eg I want to update
> things in there, install new frameworks, but at the moment I am
thanks!
do you have some examples of how you are using it with ansible? i dont have
specific preferences, whatever works really.
On Tue, Jul 15, 2014 at 2:35 PM, Dick Davies wrote:
> You want a rolling restart i'd guess, unless you want downtime for some
> reason.
>
> We use Ansible, it's pret
Tom -
I understand the desire to create bindings outside the core. The point I was
trying to make earlier around version semantics and testing was to 'Hedge' the
risk. It basically creates a contract between core & framework+bindings
writers.
No one ever intends to break compatibility, but i
Hi all,
Apologies for being super late to this thread. To answer Niklas point at
the start of the thread: Yes, I am thrilled to contribute in anyway I can.
The project is moving forward and making progress (slower than I want, but
progress regardless).
Going Native
Implementing a native client
+1 (binding)
Tested on:
- OSX Mavericks w/ clang-503.0.40 & LLVM 3.4
- Ubuntu 13.10 w/ gcc-4.8.1 (LogZooKeeperTest.WriteRead is still flaky on
that VM)
Thanks Ben!
On 14 July 2014 21:39, Benjamin Hindman wrote:
> +1, thanks Ben!
>
>
> On Mon, Jul 14, 2014 at 6:20 PM, Vinod Kone wrote:
>
>> +
On Fri, Jul 4, 2014 at 2:05 AM, Gurvinder Singh
wrote:
> ERROR storage.BlockManagerMasterActor: Got two different block manager
> registrations on 201407031041-1227224054-5050-24004-0
>
> Googling about it seems that mesos is starting slaves at the same time
> and giving them the same id. So may
On Tue, Jul 15, 2014 at 11:02 PM, Vinod Kone wrote:
>
> On Fri, Jul 4, 2014 at 2:05 AM, Gurvinder Singh <
> gurvinder.si...@uninett.no> wrote:
>
>> ERROR storage.BlockManagerMasterActor: Got two different block manager
>> registrations on 201407031041-1227224054-5050-24004-0
>>
>> Googling about
9 matches
Mail list logo
