Support adaptive replica selection and preference #89453
Labels
:Distributed/Network
Http and internode communication implementations
>enhancement
Team:Distributed
Meta label for distributed team
Description
Currently if the preference is set during a search operation it disables adaptive replica selection for that query. This is understandable, as the two mechanisms are different and conflicting approaches for replica selection.
In some cases it would be ideal though if there was a hybrid schema that allowed to reap the benefit of both, and specifically improving caching hit ratios (by using a custom string preference to steer similar requests to the same nodes) while avoiding hotspots (by using adaptive replica selection to spread the load only in case it becomes excessive on any individual node).
The ideal solution would steer requests for the same preference string to the minimum number of replicas required to prevent any individual node from becoming overloaded.
So e.g.
The text was updated successfully, but these errors were encountered: