On 5/16/2016 10:28 PM, Jeff Wartes wrote:
> One thing that still feels a bit odd though is that the health check query
> was referencing a collection that no longer existed in the cluster. So it
> seems like it was downloading the state for ALL non-hosted collections, not a
> requested one.
>
>
bq: One thing that still feels a bit odd though is that the health
check query was referencing a collection that no longer existed in the
cluster. So it seems like it was downloading the state for ALL
non-hosted collections, not a requested one.
This is a bit odd, I don't know whether there's
Ah, I tracked this down to an haproxy that was set up on a load server during
development and still running. It was configured with a health check every 10
seconds, so that’s pretty clearly the cause. Thanks for the pointer.
One thing that still feels a bit odd though is that the health check
With the per-collection state.json, if "something" goes to a node that doesn't
host a replica for a node, it downloads the state for the "other"
collection then
throws it away.
In this case, "something" is apparently asking the nodes hosting collectionA to
do "something" with collections B and/or
I have a solr 5.4 cluster with three collections, A, B, C.
Nodes either host replicas for collection A, or B and C. Collections B and C
are not currently used - no inserts or queries. Collection A is getting
significant query traffic, but no insert traffic, and queries are only directed
to
