[
https://issues.apache.org/jira/browse/MRESOLVER-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842490#comment-17842490
]
Tamas Cservenak edited comment on MRESOLVER-554 at 4/30/24 7:36 PM:
--------------------------------------------------------------------
One ask, if I may have: please pressure your artifact MRM provider, as since
"parallel upload" was introduced, both major implementations (AF and Nx3, but
not Nx2!) were reported to... well, nicely said: belly up during uploads.
Basically, report this issue and let vendors fix their products :)
was (Author: cstamas):
One ask, if I may have: please pressure your artifact MRM provider, as since
"parallel upload" was introduced, both major implementations (AF and Nx3,but
not Nx2!) were reported to... well, nicely said: belly up during uploads.
Basically, report this issue and let vendors fix their products :)
> Support configuration of upload/download threads individually
> -------------------------------------------------------------
>
> Key: MRESOLVER-554
> URL: https://issues.apache.org/jira/browse/MRESOLVER-554
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Matt Nelson
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
>
> Parallel deploys were introduced in MRESOLVER-32. The thread pool
> configuration is shared for uploads and downloads. It has been observed in
> our environment that uploads frequently error out when attempting to upload
> with the default thread pool size(5), but conversely we don't see the same
> errors for downloads.
> The proposal is to support configuration of upload/download thread pools
> individually.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
