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

Hudson commented on HDFS-14160:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #15662 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15662/])
HDFS-14160. [SBN read] ObserverReadInvocationHandler should implement (shv: rev 
c9d7737431862d0a93dac38267006d8cc218cb75)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/ObserverReadProxyProvider.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/HATestUtil.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsck.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestObserverNode.java


> ObserverReadInvocationHandler should implement RpcInvocationHandler
> -------------------------------------------------------------------
>
>                 Key: HDFS-14160
>                 URL: https://issues.apache.org/jira/browse/HDFS-14160
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>            Priority: Major
>             Fix For: HDFS-12943, 3.3.0
>
>         Attachments: HDFS-14160-HDFS-12943.001.patch, 
> HDFS-14160-HDFS-12943.002.patch
>
>
> Currently ObserverReadInvocationHandler implements InvocationHandler.
> [As 
> mentioned|https://issues.apache.org/jira/browse/HDFS-14116?focusedCommentId=16710596&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16710596]
>  in HDFS-14116 this is the cause of Fsck failing with Observer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to