On 07/12/2017 06:05 PM, Alexandre DERUMIER wrote:
forgot to said, it's with proxmox 4, corosync 2.4.2-2~pve4+1
cpu are CPU E5-2687W v3 @ 3.10GHz
And what switches do you employ there? You said something about modern
low latency ASIC switches.
But yes, quite interesting that this can be
forgot to said, it's with proxmox 4, corosync 2.4.2-2~pve4+1
cpu are CPU E5-2687W v3 @ 3.10GHz
- Mail original -
De: "dietmar"
À: "aderumier"
Cc: "proxmoxve" , "pve-devel"
Envoyé: Mercredi
> >>how many running VMs/Containers?
>
> on 20 cluster nodes, around 1000 vm
>
> on a 10 cluster nodes, 800vm + 800ct
>
> on a 9 cluster nodes, 400vm
Interesting. So far I did not know anybody using that with more than 6 nodes ...
___
pve-user
>>how many running VMs/Containers?
on 20 cluster nodes, around 1000 vm
on a 10 cluster nodes, 800vm + 800ct
on a 9 cluster nodes, 400vm
- Mail original -
De: "dietmar"
À: "aderumier" , "pve-devel"
Cc:
# cat /etc/pve/replication.cfg
local: 105-0
target ns302695
rate 10
schedule */2:00
local: 103-0
target ns3511723
rate 11
schedule */20
local: 109-0
target ns3511723
rate 10
local: 102-0
target ns302695
rate 10
schedule 22:30
local: 107-0
hi,
i reply here, to avoid confusion in the other thread
can you post the content of the two files:
/etc/pve/replication.cfg
/var/lib/pve-manager/pve-replication-state.json (of the source node)
?
___
pve-user mailing list
pve-user@pve.proxmox.com
Another strange thing is that the failing jobs are running out of schedule.
Jul 12 12:00:03 ns pvesr[12049]: total estimated size is 119M
Jul 12 12:00:03 ns pvesr[12049]: TIMESENT SNAPSHOT
Jul 12 12:00:04 ns pvesr[12049]: 12:00:04 9.18M
> just for the record,
>
> I have migrate all my clusters with unicast, also big clusters with 16-20
> nodes, and It's working fine.
>
>
> "pvedaemon: ipcc_send_rec failed: Transport endpoint is not connected " seem
> to be gone.
>
> don't see any error on the cluster.
>
> traffic is around
Hi Alexander,
Nice, thanks for sharing, it will definitely help in some cases.
Regards,
Dimitris Beletsiotis
On Wed, Jul 12, 2017, 10:15 Alexandre DERUMIER wrote:
> Hi,
>
> just for the record,
>
> I have migrate all my clusters with unicast, also big clusters with 16-20
Hi,
just for the record,
I have migrate all my clusters with unicast, also big clusters with 16-20
nodes, and It's working fine.
"pvedaemon: ipcc_send_rec failed: Transport endpoint is not connected " seem to
be gone.
don't see any error on the cluster.
traffic is around 3-4mbit/s on each
10 matches
Mail list logo