[pve-devel] [PATCH docs] pvecm: fix corosync link priority description

Thomas Lamprecht t.lamprecht at proxmox.com
Fri Feb 7 11:00:12 CET 2020


On 2/7/20 10:55 AM, Thomas Lamprecht wrote:
> On 2/7/20 10:37 AM, Aaron Lauterer wrote:
>> The official man page fixed this in commit 0a323ff [0] to describe the
>> actual behaviour: higher knet_link_priority number equals to higher
>> priority
> 
> higher priority is used, yes, but lower value means higher priority...

OK, scratch that, the source code checks out for real higher ^^

> 
>>
>> [0] https://github.com/corosync/corosync/commit/0a323ff2ed0f2aff9cb691072906e69cb96ed662
>>
>> Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
>> ---
>>  pvecm.adoc | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/pvecm.adoc b/pvecm.adoc
>> index 5a73c1e..72e7c02 100644
>> --- a/pvecm.adoc
>> +++ b/pvecm.adoc
>> @@ -762,10 +762,10 @@ by setting 'knet_link_priority' in the corresponding interface section in
>>  your cluster with `pvecm`:
>>  
>>  ----
>> - # pvecm create CLUSTERNAME --link0 10.10.10.1,priority=20 --link1 10.20.20.1,priority=15
>> + # pvecm create CLUSTERNAME --link0 10.10.10.1,priority=15 --link1 10.20.20.1,priority=20
>>  ----
>>  
>> -This would cause 'link1' to be used first, since it has the lower priority.
>> +This would cause 'link1' to be used first, since it has the higher priority.
>>  
>>  If no priorities are configured manually (or two links have the same priority),
>>  links will be used in order of their number, with the lower number having higher
>>
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 




More information about the pve-devel mailing list