etty sure CDCR uses HTTP/HTTPS rather than just TCP, so also
>> check whether some proxy/load balancer between data centers is causing it
>> to be a single connection per operation. That will *kill* performance.
>> Some proxies default to HTTP/1.0 (open, send request, server send
>> respo
AM, Davis, Daniel (NIH/NLM) [C] <
> > > > daniel.da...@nih.gov> wrote:
> > > > >>>
> > > > >>> These are general guidelines, I've done loads of networking, but
> > may
> > > > be less familiar with SolrCloud and CDC
centers using ping or
> TCP
> > > ping. Throughput tests may be high, but if Solr has to wait for a
> > > response to a request before sending the next action, then just like
> any
> > > network protocol that does that, it will get slow.
> > > >>&g
st like any
> > network protocol that does that, it will get slow.
> > >>>
> > >>> I'm pretty sure CDCR uses HTTP/HTTPS rather than just TCP, so also
> > check whether some proxy/load balancer between data centers is causing it
> > to be a single
hat will *kill* performance.
> Some proxies default to HTTP/1.0 (open, send request, server send
> response, close), and that will hurt.
> >>>
> >>> Why you should listen to me even without SolrCloud knowledge -
> checkout paper "Latency performance of SOAP I
roxies default to HTTP/1.0 (open, send request, server send response,
>>> close), and that will hurt.
>>>
>>> Why you should listen to me even without SolrCloud knowledge - checkout
>>> paper "Latency performance of SOAP Implementations". Same distr
aper "Latency performance of SOAP Implementations". Same distribution of
>> skills - I knew TCP well, but Apache Axis 1.1 not so well. I still
>> improved response time of Apache Axis 1.1 by 250ms per call with 1-line of
>> code.
>>
>> -Or
ten to me even without SolrCloud knowledge - checkout
>>> paper "Latency performance of SOAP Implementations". Same distribution of
>>> skills - I knew TCP well, but Apache Axis 1.1 not so well. I still
>>> improved response time of Apache Axis 1.1 by 250ms
s [mailto:tpet...@synacor.com]
Sent: Wednesday, March 7, 2018 6:19 PM
To: solr-user@lucene.apache.org
Subject: CDCR performance issues
I'm having issues with the target collection staying up-to-date with indexing
from the source collection using CDCR.
This is what I'm getting back in
-
> From: Tom Peters [mailto:tpet...@synacor.com]
> Sent: Wednesday, March 7, 2018 6:19 PM
> To: solr-user@lucene.apache.org
> Subject: CDCR performance issues
>
> I'm having issues with the target collection staying up-to-date with indexing
> from the source collection
ednesday, March 7, 2018 6:19 PM
To: solr-user@lucene.apache.org
Subject: CDCR performance issues
I'm having issues with the target collection staying up-to-date with indexing
from the source collection using CDCR.
This is what I'm getting back in terms of OPS:
curl -s 'solr2-
So I'm continuing to look into this and not making much headway, but I have
additional questions now as well.
I restarted the nodes in the source data center to see if it would have any
impact. It appeared to initiate another bootstrap with the target. The lag and
queueSize were brought back do
I'm having issues with the target collection staying up-to-date with indexing
from the source collection using CDCR.
This is what I'm getting back in terms of OPS:
curl -s 'solr2-a:8080/solr/mycollection/cdcr?action=OPS' | jq .
{
"responseHeader": {
"status": 0,
"Q
13 matches
Mail list logo
