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 it seems that mesos is starting slaves at the same time
and giving
On Tue, Jul 15, 2014 at 11:02 PM, Vinod Kone vi...@twitter.com 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
Thanks for those! I will give it a try to get some deployment through
ansible.
I was also wondering if Cloudformation might be good for this? As it clears
up the things very cleanly when you remove the formation? Though I find
their JSON file very difficult to navigate and their Update Feature
For provisioning yes , for ad-hoc maintenance tasks won't help at all.
On 16 July 2014 11:29, Nayeem Syed nay...@cronycle.com wrote:
Thanks for those! I will give it a try to get some deployment through
ansible.
I was also wondering if Cloudformation might be good for this? As it clears
up
you mean ad-hoc maintenance formations wont help?
probably should have it deployed using formations initially and use
user-data to customize the server with specific installs etc?
On Wed, Jul 16, 2014 at 12:15 PM, Dick Davies d...@hellooperator.net
wrote:
For provisioning yes , for ad-hoc
+1 (non binding)
- Tested on Mac OSX mavericks
- Tested on Ubuntu 12.04 LTS machines (spark and Hadoop run fine also)
On 15 Jul 2014, at 19:48, Niklas Nielsen nik...@mesosphere.io wrote:
+1 (binding)
Tested on:
- OSX Mavericks w/ clang-503.0.40 LLVM 3.4
- Ubuntu 13.10 w/ gcc-4.8.1
I'll set some time aside today to gather and post some logs and details about
this issue from our end.
On Wed, Jul 16, 2014 at 2:05 AM, Vinod Kone vinodk...@gmail.com wrote:
On Tue, Jul 15, 2014 at 11:02 PM, Vinod Kone vi...@twitter.com wrote:
On Fri, Jul 4, 2014 at 2:05 AM, Gurvinder Singh
I manage my Mesos clusters via CloudFormation. Upgrades are pretty
straightforward -- just apply an updated template (and/or parameters) to an
existing stack. For now, I manually terminate instances (one at a time) and
let the auto scaling groups bring up replacements with the new
configuration.
IIRC Till has not been able to address that issue yet. So I guess the
answer is no for now, unfortunately.
Niklas
On 16 July 2014 10:31, Michael Babineau michael.babin...@gmail.com wrote:
Not sure what the proper channel is for this, but any chance
What scenario did you have in mind? (Which resource do you expect to be
problematic?)
On Wed, Jul 16, 2014 at 2:27 PM, Nayeem Syed nay...@cronycle.com wrote:
Hi Michael,
I was considering also using cloud-formation for setting up Mesos
clusters. So the update is only possible for
say if i want to change things in the cluster, maybe change a SG setting,
change a ELB size, ... anything in the formation.
On Wed, Jul 16, 2014 at 10:33 PM, Michael Babineau
michael.babin...@gmail.com wrote:
What scenario did you have in mind? (Which resource do you expect to be
I think you need to handle it on a case-by-case basis. I suspect that a
stack update would still be appropriate for most cases. If you still have
concerns, you could always launch a second stack (pointing at the same ZK
location) and migrate over by scaling down the first stack.
I've had success
12 matches
Mail list logo
