[ https://issues.apache.org/jira/browse/OOZIE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928277#comment-16928277 ]
ASF subversion and git services commented on OOZIE-3542: -------------------------------------------------------- Commit e1c865e1d898443cbc918d7deaa622ce0556e3e1 in oozie's branch refs/heads/master from Kinga Marton [ https://gitbox.apache.org/repos/asf?p=oozie.git;h=e1c865e ] OOZIE-3542 Handle better old Hdfs implementations in ECPolicyDisabler (zsombor dionusos via kmarton) > Handle better old Hdfs implementations in ECPolicyDisabler > ---------------------------------------------------------- > > Key: OOZIE-3542 > URL: https://issues.apache.org/jira/browse/OOZIE-3542 > Project: Oozie > Issue Type: Bug > Components: tools > Reporter: Zsombor Gegesy > Assignee: Zsombor Gegesy > Priority: Major > Attachments: OOZIE-3542-2.patch, OOZIE-3542-3.patch, > OOZIE-3542-4.patch > > > Currently, ECPolicyDisabler checks if the local hdfs implementation has the > necessary methods to get and set erasure coding policy. However, if the > namenode implementation is old, it could throw a > org.apache.hadoop.ipc.RemoteException with > RpcErrorCodeProto.ERROR_NO_SUCH_METHOD value in it. > In this case, ECPolicyDisabler fails, and prevents the installation to > succeed. > This case should be handled just like, when erasure coding is not supported. -- This message was sent by Atlassian Jira (v8.3.2#803003)