You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (Jira)" <ji...@apache.org> on 2022/08/15 14:39:00 UTC
[jira] [Assigned] (NUTCH-2896) Protocol-okhttp: make connection pool configurable
[ https://issues.apache.org/jira/browse/NUTCH-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Nagel reassigned NUTCH-2896:
--------------------------------------
Assignee: Sebastian Nagel
> 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)