Re: [DISCUSS] Management server (pre-)shutdown to avoid killing jobs

Hi Marc, I like the idea, I guess a locking-service was needed in CloudStack to no only solve the issue of locking and getting rid of DB-based lock (which I suppose if we can get rid of, may help people migrate to mysql-clusters with active-active setup which cannot be used due to LOCK

Re: [DISCUSS] Management server (pre-)shutdown to avoid killing jobs

This is the best design, Marc. I also find quite ….. seeing all of those thread being managed manually in ACS. I would only look at other technologies such as Spring-integration or AKKA to create the structure for an async messaging system across nodes/JVMs (I find Kafka too damn complicated to

Re: [DISCUSS] Management server (pre-)shutdown to avoid killing jobs

It's definitively a great direction to take and much more robust. ZK would be great fit to monitor the state of management servers and agent with the help of the ephemeral nodes. On the other side, it's not encouraged to use it as a messaging queue, and kafka would be a much better fit for that

Re: [DISCUSS] Management server (pre-)shutdown to avoid killing jobs

I very much agree with Paul, we should consider moving into resilient model with least dependence I.e ha-proxy.. Send a notification to partner MS to take over the job management would be ideal. On Mon, Dec 18, 2017 at 9:28 AM Paul Angus wrote: > Hi Marc-Aurèle, > >

RE: [DISCUSS] Management server (pre-)shutdown to avoid killing jobs

Hi Marc-Aurèle, Personally, my utopia would be to be able to pass async jobs between mgmt. servers. So rather than waiting in indeterminate time for a snapshot to complete, monitoring the job is passed to another management server. I would LOVE that something like Zookeeper monitored the