Hi!

I think it all depends, but we have at least 20ms (the maximum for the maximum) 
for the maximum multipath response time for reading, while the average maximum 
is near 3ms. The average is near 0.2ms,and the fastest response is near 0.1ms.
In case a disk has I/O errors, the numbers my go up significantly.
The basic question is: How many percent of all cases do you want to cover?

Regards,
Ulrich


>>> Brad Zynda <[email protected]> schrieb am 11.12.2017 um 18:47 in
Nachricht <[email protected]>:
> I guess to simplify this, what is the max latency of corosync multipath?
> I have seen a few articles pointing to 2ms is this still the case?
> 
> Thanks,
> Brad
> 
> On 12/04/2017 08:25 AM, Brad Zynda wrote:
>> Hello,
>> 
>> I was hoping someone could explain the use of thresholds in
>> communication between HA/Cluster members, more specifically their use of
>> ping and latency.
>> 
>> We have noticed issues with ICMP latency gathering in other services and
>> hardware and are wondering if this could be the case with the token
>> timeouts we are seeing from corosync log events.
>> 
>> We have increased the token amount from 1200 to 2000.
>> 
>> We are still seeing issues with token timeout increase warnings and
>> 
>> corosync[1256]: [TOTEM ] A processor failed, forming new configuration.
>> 
>> 
>> Could this all be related to
>> https://kb.juniper.net/InfoCenter/index?page=content&id=KB28157 
>> 
>> Now just to add some more info specific to the article we are seeing 100
>> to 1000 not just 10 (maybe downplayed via the article)
>> 
>> and if so can corosync/pacemaker be used with tcping vs ping?
>> 
>> Thanks,
>> Brad
>> 
>> _______________________________________________
>> Users mailing list: [email protected] 
>> http://lists.clusterlabs.org/mailman/listinfo/users 
>> 
>> Project Home: http://www.clusterlabs.org 
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
>> Bugs: http://bugs.clusterlabs.org 
>> 
> 
> _______________________________________________
> Users mailing list: [email protected] 
> http://lists.clusterlabs.org/mailman/listinfo/users 
> 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org


_______________________________________________
Users mailing list: [email protected]
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to