You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Zsombor Gegesy (Jira)" <ji...@apache.org> on 2019/10/14 12:24:00 UTC

[jira] [Updated] (OOZIE-3542) Handle better old Hdfs implementations in ECPolicyDisabler

     [ https://issues.apache.org/jira/browse/OOZIE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zsombor Gegesy updated OOZIE-3542:
----------------------------------
    Attachment: OOZIE-3542-amend-02.patch

> 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
>             Fix For: 5.2.0
>
>         Attachments: OOZIE-3542-2.patch, OOZIE-3542-3.patch, OOZIE-3542-4.patch, OOZIE-3542-amend-01.patch, OOZIE-3542-amend-02.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.4#803005)