There are several parameters to tweak on the lb that may have an impact on
your liveness detection.
1. How frequently you poll the health check url. Polling every 15s vs 60s
for example.
2. How many failures it takes to remove a node from the pool. 5 failures
at 60s intervals means that node w
Thanks Mikhail, will try these approaches.
On Thu, Jun 15, 2023 at 5:40 PM Mikhail Khludnev wrote:
> From the other POV, a node can be excluded from LB pool via balancer API
> before restart and brought back then.
>
> On Wed, Jun 14, 2023 at 6:09 PM Saksham Gupta
> wrote:
>
> > Have you configu
>From the other POV, a node can be excluded from LB pool via balancer API
before restart and brought back then.
On Wed, Jun 14, 2023 at 6:09 PM Saksham Gupta
wrote:
> Have you configured an URL for health check? Which one?
> The load balancer checks if the solr port is in use or not. If yes, the
Right, If healthcheck url is configured to ping handler, one may turn it
off from getting traffic before restart via http://.../ping?action=disable
.
see
https://solr.apache.org/docs/9_2_1/core/org/apache/solr/handler/PingRequestHandler.html
On Wed, Jun 14, 2023 at 6:09 PM Saksham Gupta
wrote:
Have you configured an URL for health check? Which one?
The load balancer checks if the solr port is in use or not. If yes, then it
continues sending the search requests.
Or you have something like rolling restart/recycle scenarios executed?
No, we don't have anything like that configured.
@ufuk W
Saksham, can you comment on
> if a certain port is up or not and based on that send the request to that
node.
Have you configured an URL for health check? Which one?
> the coordinator node goes down after a request is sent from lb.
Do you mean nodes are failing more often than healthcheck occur?
Why are they down so often? Isn’t that another problem?
—
> On 14 Jun 2023, at 08:50, Saksham Gupta
> wrote:
>
> @Ufuk We are using a load balancer to avoid a single point of failure i.e.
> if all the requests have a single coordinator node then it would be a major
> issue if this solr node go
@Ufuk We are using a load balancer to avoid a single point of failure i.e.
if all the requests have a single coordinator node then it would be a major
issue if this solr node goes down.
@Mikhail Khludnev We already have a health check configured on load
balancer, but the requests will fail if the
Well, probably it's what Solr Operator can provide on Kubernetes.
On Tue, Jun 13, 2023 at 10:47 AM ufuk yılmaz
wrote:
> Just wondered, solr cloud itself can handle node failings and load
> balancing. Why use an external cloud load balancer?
>
> —ufuk yilmaz
>
> —
>
> > On 13 Jun 2023, at 10:28,
Just wondered, solr cloud itself can handle node failings and load balancing.
Why use an external cloud load balancer?
—ufuk yilmaz
—
> On 13 Jun 2023, at 10:28, Mikhail Khludnev wrote:
>
> Hello
> You can configure healthcheck
> https://cloud.google.com/load-balancing/docs/health-check-conce
Hello
You can configure healthcheck
https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-http
with Solr's ping request handler
https://solr.apache.org/guide/solr/latest/deployment-guide/ping.html.
Also, Google cloud has sophisticated Traffic Director, which can also
Hi team,
We need help with the strategy used to request data from solr cloud.
*Current Searching Strategy:*
We are using solr cloud 8.10 having 8 nodes with data sharded on the basis
of an implicit route parameter. We send a search http request on google's
network load balancer which divides reque
12 matches
Mail list logo
