Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-12859

Docker-nexus3 - RAM issue

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Docker-Nexus
    • Labels:
      None

      Description

      Hi,

      when uploading extremely huge (8+GB) docker image layers on a container with less RAM than the blob size, then the Java process appears to buffer all incoming data in RAM and subsequently break when the memory exhausts (only the upload fails, the container itself continues running as soon as the HTTP buffer is evicted from memory):

      2017-02-22 10:03:01,772+0000 WARN [qtp1126292720-510] xxx org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: PATCH /v2/xxxxxxxx/blobs/uploads/4ee41xxxxxxxxxc33ccd73
      java.nio.channels.ClosedChannelException: null

      Having to provision the equivalent amount of RAM that is expected for the maximum layer size is just horribly inefficient and expensive, please fix this.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jhesse Jeffry Hesse
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title