[jira] [Commented] (SOLR-12293) Updates need to use their own connection pool to maintain connection reuse and prevent spurious recoveries.

["Mark Miller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-12293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462026#comment-16462026 ] 

Mark Miller commented on SOLR-12293:
------------------------------------

Hmm, we probably don't need the new executor as well.

> Updates need to use their own connection pool to maintain connection reuse and prevent spurious recoveries.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-12293
>                 URL: https://issues.apache.org/jira/browse/SOLR-12293
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Major
>         Attachments: SOLR-12293.patch
>
>
> Currently the pool is shared too broadly - for example during replication we don't guarantee we read the full streams when downloading index files and we don't necessarily want to, emptying the stream for a huge file due to error or abort is too expensive. We can't have these connections pollute the update connection pool.



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