OK, thank you guys :)
Regards,
Boban
> On the other hand, the CloudSolrClient ignores errors from Solr, which makes
> it unacceptable for production use.
Did you mean "ConcurrentUpdateSolrClient"? I don't think
CloudSolrClient does this, though I've been surprised before and
possible I just missed something. Just wondering.
Jason
The update router would also need to look for failures indexing at each leader,
then re-read the cluster state to see if the leader had changed. Also re-send
any
failed updates, and so on.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 11, 2019,
Hi Boban,
First of all: I agree with Walter here. Because the bottleneck is during
indexing on the leader, a basic round robin load balancer will perform just
as well as a custom solution. With far less headache. A custom solution
will be far more work than it's worth.
But, should you really want
For the fourth time, ignore the shard leaders until you have measurements that
prove the complexity is worth it.
We can index a million documents per minute by sending batched updates to a
dumb load balancer.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blo
Like I said before, nginx is not a load balancer or at least not a clever load
balancer. It does not talk to ZK. Please give me advanced solutions.
> On 11. Feb 2019, at 18:32, Walter Underwood wrote:
>
> I haven’t used Kubernetes, but a web search for “helm nginx” seems to give
> some usef
me you are using Kubernetes because of your reference to helm, but for
> what it's worth, here's an official haproxy image -
> https://hub.docker.com/_/haproxy
>
>> -Original Message-
>> From: Boban Acimovic
>> Sent: Monday, February 11, 2019 11:58 AM
>&
This is naive load balancing because it is not aware of ZK.
> On 11. Feb 2019, at 18:05, Walter Underwood wrote:
>
> nginx
>
> http://nginx.org/en/docs/http/load_balancing.html
> https://hub.docker.com/_/nginx
>
> We run in Amazon AWS, so we use their Application Load Balaner (ALB). We do
>> -Original Message-
>> From: Boban Acimovic
>> Sent: Monday, February 11, 2019 11:58 AM
>> To: solr-user@lucene.apache.org
>> Subject: Re: Load balance writes
>>
>> Can you mention one dockerized load balancer? Or even better one
sage-
> From: Boban Acimovic
> Sent: Monday, February 11, 2019 11:58 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Load balance writes
>
> Can you mention one dockerized load balancer? Or even better one with
> Helm chart?
>
>
> Like I said, I send
nginx
http://nginx.org/en/docs/http/load_balancing.html
https://hub.docker.com/_/nginx
We run in Amazon AWS, so we use their Application Load Balaner (ALB). We do use
nginx for other things.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 11, 2
Can you mention one dockerized load balancer? Or even better one with Helm
chart?
Like I said, I send all updates at the moment just to one out of 12 nodes.
> On 11. Feb 2019, at 17:52, Walter Underwood wrote:
>
> Why would you want to write a load balancer when there are so many that are
Why would you want to write a load balancer when there are so many that are
free and very fast?
For update traffic, there is very little benefit in sending updates directly to
the shard leader. Forwarding an update to the leader is fast. Indexing is slow.
So the bottleneck is always at the lead
I would actually like to write a load balancer itself, but I want it to be able
to send the data as efficiently as possible. I know how to read ZK data, but I
don’t know how can I figure out which shard is responsible upon data that I
have in a document that I want to index.
> On 11. Feb 201
Thank you again Emir. I can make my code ZK aware, that is no problem, but I
can’t make it shard leader aware. Can you point me to a document how are Solr
shards created? I already use ZK to get stuff, but I don’ t understand how to
distinguish between shards from information I can get from a
We send all updates to the load balancer, so they’ll end up on the wrong shard,
not on the leader, etc. Indexing speed is still limited by the CPU available on
each leader. I don’t think that sending the update to the right leader makes
any improvement in throughput.
On the other hand, the Clou
Hi Boban,
Not sure if there is Solrj port to Go, but you can take that as model to build
your ZK aware client that groups and sends updates to shard leaders. I see that
there are couple of Solr Go clients, so you might first check if some already
supports it or if it makes sense that you contrib
Thank you Emir for quick reply. I use home brewed Go client and write just to
one of 12 available nodes. I believe I should find out this smart way to handle
this :)
> On 11. Feb 2019, at 15:21, Emir Arnautović
> wrote:
>
> Hi Boban,
> If you use SolrCloud Solrj client and initialise it w
Hi Boban,
If you use SolrCloud Solrj client and initialise it with ZK, it should be
aware of masters and send documents in a smart way.
HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 11 Feb 2
19 matches
Mail list logo
