lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <>
Subject [jira] [Updated] (SOLR-12642) SolrCmdDistributor should send updates in batch when use Http2SolrClient?
Date Fri, 07 Sep 2018 02:51:00 GMT


Cao Manh Dat updated SOLR-12642:
    Attachment: master-branch.log

> SolrCmdDistributor should send updates in batch when use Http2SolrClient?
> -------------------------------------------------------------------------
>                 Key: SOLR-12642
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Cao Manh Dat
>            Priority: Major
>         Attachments: http2-branch.log, master-branch.log
> In the past, batch updates are sent in a single stream from the leader, the replica will
create a single thread to parse all the updates. For the simplicity of {{SOLR-12605}}, the
leader is now sending individual updates to replicas, therefore they are now parsing updates
in different threads which increase the usage of memory and CPU.
> In the past, this is an unacceptable approach, because, for every update, we must create
different connections to replicas. But with the support of HTTP/2, all updates will be sent
in a single connection from leader to a replica. Therefore the cost is not as high as it used
to be.
> On the other hand, sending individual updates will improve the indexing performance and
better error-handling for failures of a single update in a batch.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message