[ https://issues.apache.org/jira/browse/HDFS-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308776#comment-17308776 ]
Jason Wen commented on HDFS-15916: ---------------------------------- Yes, it makes sense for sure if we can make it work with the mentioned fix. In general I would like to see the compatibility between 3.x client to 2.x server, but I am not sure if there is any more road blocks to achieve that. If for this particular case we can make it work with few changes, it's definitely worth fixing that. > Backward compatibility - Distcp fails from Hadoop 3 to Hadoop 2 for > snapshotdiff > -------------------------------------------------------------------------------- > > Key: HDFS-15916 > URL: https://issues.apache.org/jira/browse/HDFS-15916 > Project: Hadoop HDFS > Issue Type: Bug > Components: distcp > Affects Versions: 3.2.2 > Reporter: Srinivasu Majeti > Priority: Major > > Looks like when using distcp diff options between two snapshots from a hadoop > 3 cluster to hadoop 2 cluster , we get below exception and seems to be break > backward compatibility due to new API introduction > getSnapshotDiffReportListing. > > {code:java} > hadoop distcp -diff s1 s2 -update src_cluster_path dst_cluster_path > org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RpcNoSuchMethodException): > Unknown method getSnapshotDiffReportListing called on > org.apache.hadoop.hdfs.protocol.ClientProtocol protocol > {code} > > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org