[jira] [Updated] (SOLR-12642) SolrCmdDistributor should send updates in batch when use Http2SolrClient?

["Cao Manh Dat (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

> SolrCmdDistributor should send updates in batch when use Http2SolrClient?
> -------------------------------------------------------------------------
>
>                 Key: SOLR-12642
>                 URL: https://issues.apache.org/jira/browse/SOLR-12642
>             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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org