Nexus Repository - Proxy Behaviour of Uncached Components during Concurrent Access

Sonatype Nexus Repository
1

Greetings,

I’m asking this question here since I couldn’t find information in the documentation regarding this.

I’m using Nexus as an APT (Debian) proxy to cache package downloads and usually run updates/upgrades on dozens of machines at once via an Ansible playbook.

I’m wondering how in these cases Nexus handles downloads of packages that aren’t in the proxy cache and multiple clients request it at the same time, does Nexus do one upstream fetch and then serve it to all clients or do all requests get served from the upstream with no caching?

2

Within a single node of Nexus Repository Manager assuming the proxy repository has not been configured to always check the remote, there should only be one outbound request for a given resource.

With high availability each node may make a single request for the external resource. Earlier versions of Nexus tried to achieve a single outbound request across all nodes but this was disabled due to performance issues in large instances.