`shards.preference` only affects the backend routing of requests to
individual cores/shards. These backend requests should have an additional
`distrib=false` param, and are the requests that are generally the most
resource-intensive, in that they do the initial per-shard domain-narrowing.
I'm fair
Hello,
I've been trying out the shards.preference=replica.type:PULL as a parameter
appended onto queries, as well as trying out including it in the search request
handler. For context, we have a collection that is 2 shards, 2 TLOGs per shard,
and n number of PULLs (can change depending on if w
