[ https://issues.apache.org/jira/browse/HADOOP-14521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050827#comment-16050827 ]
Rushabh S Shah commented on HADOOP-14521: ----------------------------------------- Test failures are not relevant. {noformat} Running org.apache.hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem Tests run: 70, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 9.571 sec - in org.apache.hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem Running org.apache.hadoop.security.TestRaceWhenRelogin Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.127 sec - in org.apache.hadoop.security.TestRaceWhenRelogin Results : Tests run: 71, Failures: 0, Errors: 0, Skipped: 1 {noformat} {noformat} Running org.apache.hadoop.hdfs.server.balancer.TestBalancer Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 370.577 sec - in org.apache.hadoop.hdfs.server.balancer.TestBalancer Running org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.397 sec - in org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting Running org.apache.hadoop.hdfs.TestDFSStripedOutputStreamWithFailureWithRandomECPolicy Tests run: 14, Failures: 0, Errors: 0, Skipped: 10, Time elapsed: 69.502 sec - in org.apache.hadoop.hdfs.TestDFSStripedOutputStreamWithFailureWithRandomECPolicy Results : Tests run: 53, Failures: 0, Errors: 0, Skipped: 10 {noformat} Failure of TestAclsEndToEnd getting tracked via HDFS-11944 [~xiaochen]: Mind reviewing the latest patch. Hopefully the last patch. > KMS client needs retry logic > ---------------------------- > > Key: HADOOP-14521 > URL: https://issues.apache.org/jira/browse/HADOOP-14521 > Project: Hadoop Common > Issue Type: Improvement > Affects Versions: 2.6.0 > Reporter: Rushabh S Shah > Assignee: Rushabh S Shah > Attachments: HDFS-11804-trunk-1.patch, HDFS-11804-trunk-2.patch, > HDFS-11804-trunk-3.patch, HDFS-11804-trunk-4.patch, HDFS-11804-trunk-5.patch, > HDFS-11804-trunk-6.patch, HDFS-11804-trunk-7.patch, HDFS-11804-trunk-8.patch, > HDFS-11804-trunk.patch > > > The kms client appears to have no retry logic – at all. It's completely > decoupled from the ipc retry logic. This has major impacts if the KMS is > unreachable for any reason, including but not limited to network connection > issues, timeouts, the +restart during an upgrade+. > This has some major ramifications: > # Jobs may fail to submit, although oozie resubmit logic should mask it > # Non-oozie launchers may experience higher rates if they do not already have > retry logic. > # Tasks reading EZ files will fail, probably be masked by framework reattempts > # EZ file creation fails after creating a 0-length file – client receives > EDEK in the create response, then fails when decrypting the EDEK > # Bulk hadoop fs copies, and maybe distcp, will prematurely fail -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org