[ https://issues.apache.org/jira/browse/HDDS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal resolved HDDS-1244. --------------------------------- Resolution: Invalid [~msingh] helped me out. This was a side effect of running some docker disk space issue. HDDS-1243 should improve the error propagation so this is easier to debug. > ozone sh put not working in docker container > -------------------------------------------- > > Key: HDDS-1244 > URL: https://issues.apache.org/jira/browse/HDDS-1244 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Reporter: Arpit Agarwal > Priority: Blocker > Attachments: client-logs.txt > > > Steps to repro: > # Bring up docker cluster with > {code} > docker-compose up -d --scale datanode=3 > {code} > # ssh to datanode > {code} > docker-compose exec datanode /bin/bash > {code} > # Try to put a key > {code} > ozone sh volume create /vol1 > ozone sh bucket create /vol1/bucket1 > ozone sh key put /vol1/bucket1/key1 /tmp/hadoop-hadoop-datanode.pid > {code} > This gives the following error. > {code} > 2019-03-10 21:58:09 ERROR BlockOutputStream:558 - Unexpected Storage > Container Exception: > org.apache.hadoop.hdds.scm.container.common.helpers.StorageContainerException: > ContainerID 1 does not exist > at > org.apache.hadoop.hdds.scm.storage.ContainerProtocolCalls.validateContainerResponse(ContainerProtocolCalls.java:573) > at > org.apache.hadoop.hdds.scm.storage.BlockOutputStream.validateResponse(BlockOutputStream.java:556) > at > org.apache.hadoop.hdds.scm.storage.BlockOutputStream.lambda$writeChunkToContainer$5(BlockOutputStream.java:634) > at > java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > {code} > Debug client logs attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org