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

Hudson commented on NUTCH-2896:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch ยป Nutch-trunk #81 (See 
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/81/])
NUTCH-2896 Protocol-okhttp: make connection pool configurable (snagel: 
[https://github.com/apache/nutch/commit/af44bcb6f28c8825641b9ff18a516aad8d79de61])
* (edit) conf/nutch-default.xml
* (edit) 
src/plugin/protocol-okhttp/src/java/org/apache/nutch/protocol/okhttp/OkHttp.java
* (edit) 
src/plugin/protocol-okhttp/src/java/org/apache/nutch/protocol/okhttp/OkHttpResponse.java
NUTCH-2896 Protocol-okhttp: make connection pool configurable (snagel: 
[https://github.com/apache/nutch/commit/467e59105152e34a80462bccc10e73e299010d59])
* (edit) 
src/plugin/protocol-okhttp/src/java/org/apache/nutch/protocol/okhttp/OkHttp.java


> Protocol-okhttp: make connection pool configurable
> --------------------------------------------------
>
>                 Key: NUTCH-2896
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2896
>             Project: Nutch
>          Issue Type: Improvement
>          Components: plugin, protocol
>    Affects Versions: 1.18
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Major
>             Fix For: 1.19
>
>
> [OkHttp's 
> ConnectionPool|https://square.github.io/okhttp/3.x/okhttp/okhttp3/ConnectionPool.html]
>  "holds up to 5 idle connections which will be evicted after 5 minutes of 
> inactivity."  A pool of this size is suitable for site crawls but not for 
> larger crawls over many different sites / hosts.
> Note: in the current version (4.9.1) the connection pool is implemented as a 
> [linked 
> queue|https://github.com/square/okhttp/blob/parent-4.9.1/okhttp/src/main/kotlin/okhttp3/internal/connection/RealConnectionPool.kt#L83].
>   In order to scale beyond pool sizes exceeding 1000 we need to use a set of 
> clients each with its own connection pool.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to