You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2018/08/08 08:43:00 UTC

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

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

Cao Manh Dat updated SOLR-12642:
--------------------------------
    Description: 
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, since for every updates, we must create different connections to replicas


  was:
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 a 



> 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
>
> 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, since for every updates, we must create different connections to replicas



--
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