https://github.com/facebookincubator/katran/commit/95e67746b4ba3c0b647ac62a7cf40079344841bf changed default max vips to 2048 (no idea why). The issue is that this value must be in sync with https://github.com/facebookincubator/katran/blob/main/katran/lib/bpf/balancer_consts.h#L51
otherwise you will have out of bound access in the userspace (because actual default build of bpf prog would have array size of 512 for vips while userspace thinks it is 2048).
There is no reason to change defaults (you can pass w/e you want during KatranLB consruction; however changing them would hurt library users (e.g. if you going to change bpf to use 2048 as well - you will change default hashing seed and users would have broken balancers if they would try to update them in prod - because 2 instances would have different output of hash function and consistency of the caching would be broken)
https://github.com/facebookincubator/katran/commit/95e67746b4ba3c0b647ac62a7cf40079344841bf changed default max vips to 2048 (no idea why). The issue is that this value must be in sync with https://github.com/facebookincubator/katran/blob/main/katran/lib/bpf/balancer_consts.h#L51 otherwise you will have out of bound access in the userspace (because actual default build of bpf prog would have array size of 512 for vips while userspace thinks it is 2048). There is no reason to change defaults (you can pass w/e you want during KatranLB consruction; however changing them would hurt library users (e.g. if you going to change bpf to use 2048 as well - you will change default hashing seed and users would have broken balancers if they would try to update them in prod - because 2 instances would have different output of hash function and consistency of the caching would be broken)
Also while i'm here - removing commented line.