hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12216) Ozone: TestKeys is failing consistently
Date Fri, 18 Aug 2017 22:49:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133737#comment-16133737

Anu Engineer commented on HDFS-12216:

[~msingh] Thanks for fixing this. However I think that the log statement is wrong.

129	    log.warn("Container: {} Operation: {} Trace ID: {} Message: {} Result: {}",
130	        msg.getCreateContainer().getContainerData().getName(),
131	        msg.getCmdType().name(), msg.getTraceID(),
msg.getCreateContainer assumes that RPC call is create container when we log the failure.
If you want to log the actual operation name, you have to check the type and then get the
name of the container from the right structure. I might be mistaken about this though, can
you please verify it.

Also if the user makes a wrong call, we will log that info. But should we log that with WARN
status or INFO ? There is nothing wrong with the Server when we log this warning, it just
means that user made a call with some illegal parameters.

> Ozone: TestKeys is failing consistently
> ---------------------------------------
>                 Key: HDFS-12216
>                 URL: https://issues.apache.org/jira/browse/HDFS-12216
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Mukul Kumar Singh
>            Assignee: Mukul Kumar Singh
>             Fix For: HDFS-7240
>         Attachments: HDFS-12216-HDFS-7240.001.patch, HDFS-12216-HDFS-7240.002.patch,
HDFS-12216-HDFS-7240.003.patch, HDFS-12216-HDFS-7240.004.patch, HDFS-12216-HDFS-7240.005.patch
> TestKeys and TestKeysRatis are failing consistently as noted in test logs for HDFS-12183
> TestKeysRatis is failing because of the following error
> {code}
> 2017-07-28 23:11:28,783 [StateMachineUpdater-] ERROR impl.StateMachineUpdater
(ExitUtils.java:terminate(80)) - Terminating with exit status 2: StateMachineUpdater-
the StateMachineUpdater hits Throwable
> org.iq80.leveldb.DBException: Closed
> 	at org.fusesource.leveldbjni.internal.JniDB.put(JniDB.java:123)
> 	at org.apache.hadoop.utils.LevelDBStore.put(LevelDBStore.java:98)
> 	at org.apache.hadoop.ozone.container.common.impl.KeyManagerImpl.putKey(KeyManagerImpl.java:90)
> 	at org.apache.hadoop.ozone.container.common.impl.Dispatcher.handlePutKey(Dispatcher.java:547)
> 	at org.apache.hadoop.ozone.container.common.impl.Dispatcher.keyProcessHandler(Dispatcher.java:206)
> 	at org.apache.hadoop.ozone.container.common.impl.Dispatcher.dispatch(Dispatcher.java:110)
> 	at org.apache.hadoop.ozone.container.common.transport.server.ratis.ContainerStateMachine.dispatch(ContainerStateMachine.java:94)
> 	at org.apache.hadoop.ozone.container.common.transport.server.ratis.ContainerStateMachine.applyTransaction(ContainerStateMachine.java:81)
> 	at org.apache.ratis.server.impl.RaftServerImpl.applyLogToStateMachine(RaftServerImpl.java:913)
> 	at org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:142)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}
> where as TestKeys is failing because of
> {code}
> 2017-07-28 23:14:20,889 [Thread-486] INFO  scm.XceiverClientManager (XceiverClientManager.java:getClient(158))
- exception java.util.concurrent.ExecutionException: java.net.ConnectException: Connection
refused: /
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message