[
https://issues.apache.org/jira/browse/HDDS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520895#comment-16520895
]
Arpit Agarwal edited comment on HDDS-174 at 6/22/18 11:32 PM:
--------------------------------------------------------------
I made a trivial fix to get the real error code in the protobuf translator. Now
it tells me the real code message, but the detailed cause/exception is still
not printed.
{code:java}
$ ozone oz -putKey /vol1/bucket1/key1 -file foo.txt
Command Failed : Create key failed, error:KEY_ALLOCATION_ERROR
{code}
For the detailed error, we need to go to the OzoneManager logs:
{code:java}
2018-06-22 23:07:55 ERROR KeyManagerImpl:312 - Key open failed for volume:vol1
bucket:bucket1 key:key1
org.apache.hadoop.ipc.RemoteException(java.lang.NullPointerException):
Pipeline type=RATIS/replication=THREE couldn't be found for the new container.
Do you have enoug
at
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231)
at
org.apache.hadoop.hdds.scm.container.ContainerStateManager.allocateContainer(ContainerStateManager.java:292)
at
org.apache.hadoop.hdds.scm.container.ContainerMapping.allocateContainer(ContainerMapping.java:231)
at
org.apache.hadoop.hdds.scm.block.BlockManagerImpl.preAllocateContainers(BlockManagerImpl.java:162)
at
org.apache.hadoop.hdds.scm.block.BlockManagerImpl.allocateBlock(BlockManagerImpl.java:264)
at
org.apache.hadoop.hdds.scm.server.SCMBlockProtocolServer.allocateBlock(SCMBlockProtocolServer.java:143)
at
org.apache.hadoop.ozone.protocolPB.ScmBlockLocationProtocolServerSideTranslatorPB.allocateScmBlock(ScmBlockLocationProtocolServerSideTranslatorPB.java:74)
at
org.apache.hadoop.hdds.protocol.proto.ScmBlockLocationProtocolProtos$ScmBlockLocationProtocolService$2.callBlockingMethod(ScmBlockLocationProtocolProtos.java:6271)
{code}
was (Author: arpitagarwal):
I made a trivial fix to get the real error message in the protobuf translator.
Now it tells me the real error message, but the detailed cause/exception is
still not printed.
{code}
$ ozone oz -putKey /vol1/bucket1/key1 -file foo.txt
Command Failed : Create key failed, error:KEY_ALLOCATION_ERROR
{code}
For the detailed error, we need to go to the OzoneManager logs:
{code}
2018-06-22 23:07:55 ERROR KeyManagerImpl:312 - Key open failed for volume:vol1
bucket:bucket1 key:key1
org.apache.hadoop.ipc.RemoteException(java.lang.NullPointerException):
Pipeline type=RATIS/replication=THREE couldn't be found for the new container.
Do you have enoug
at
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231)
at
org.apache.hadoop.hdds.scm.container.ContainerStateManager.allocateContainer(ContainerStateManager.java:292)
at
org.apache.hadoop.hdds.scm.container.ContainerMapping.allocateContainer(ContainerMapping.java:231)
at
org.apache.hadoop.hdds.scm.block.BlockManagerImpl.preAllocateContainers(BlockManagerImpl.java:162)
at
org.apache.hadoop.hdds.scm.block.BlockManagerImpl.allocateBlock(BlockManagerImpl.java:264)
at
org.apache.hadoop.hdds.scm.server.SCMBlockProtocolServer.allocateBlock(SCMBlockProtocolServer.java:143)
at
org.apache.hadoop.ozone.protocolPB.ScmBlockLocationProtocolServerSideTranslatorPB.allocateScmBlock(ScmBlockLocationProtocolServerSideTranslatorPB.java:74)
at
org.apache.hadoop.hdds.protocol.proto.ScmBlockLocationProtocolProtos$ScmBlockLocationProtocolService$2.callBlockingMethod(ScmBlockLocationProtocolProtos.java:6271)
{code}
> Shell error messages are often cryptic
> --------------------------------------
>
> Key: HDDS-174
> URL: https://issues.apache.org/jira/browse/HDDS-174
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Arpit Agarwal
> Assignee: Nanda kumar
> Priority: Critical
> Fix For: 0.2.1
>
>
> Error messages in the Ozone shell are often too cryptic. e.g.
> {code}
> $ ozone oz -putKey /vol1/bucket1/key1 -file foo.txt
> Command Failed : Create key failed, error:INTERNAL_ERROR
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
