his?
>
> 发件人: Nicolas Vazquez<mailto:nicolas.vazq...@shapeblue.com>
> 发送时间: 2019年6月23日 23:31
> 收件人: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>;
> users<mailto:us...@cloudstack.apache.org>
> 抄送: dev@cloudstack.apache.org<mailto:dev@cloudstack
he.org>
抄送: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
主题: Re: KVM HA fails under multiple management services
As Andrija mentioned that is expected behavior as the global setting is
'static'. It is also expected that your agents connect to the next management
server on t
domingo, 23 de junio 11:03
Asunto: Re: KVM HA fails under multiple management services
Para: users
Cc: dev@cloudstack.apache.org
Li,
based on the Global Setting description for those 2, I would say that is
the expected behaviour.
i.e. change Indirect.agent.lb.check.interval to some other value,
Li,
based on the Global Setting description for those 2, I would say that is
the expected behaviour.
i.e. change Indirect.agent.lb.check.interval to some other value, since 0
means "don't check, don't reconnect" per what I read.
Also, you might want to change from Indirect.agent.lb.algorithm=sta
Hello everyone
I recently tested the multiple management services, based on agent lb HOST HA
(KVM). It was found that in extreme cases, HA would fail; the details are as
follows:
Two management nodes, M1 (172.17.1.141) and M2 (172.17.1.142), share an
external database cluster
Three KVM nodes,
