[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Fix Version/s: 2.10.0 > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Fix For: 2.10.0, 2.8.4, 3.2.0, 3.1.1, 2.9.2, 3.0.3 > > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated HADOOP-15390: --- Fix Version/s: 2.8.4 > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Fix For: 2.8.4, 3.2.0, 3.1.1, 2.9.2, 3.0.3 > > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated HADOOP-15390: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.0.3 2.9.2 3.1.1 3.2.0 Status: Resolved (was: Patch Available) Thanks [~xiaochen]. Committed to trunk, branch-3.1, branch-3.0, and branch-2.9! > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Fix For: 3.2.0, 3.1.1, 2.9.2, 3.0.3 > > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Affects Version/s: 2.8.0 > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Target Version/s: 2.8.4 (was: 3.1.1) > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated HADOOP-15390: - Priority: Critical (was: Major) Target Version/s: 3.1.1 Can you please add which patch originally caused this and which versions are affected. Tentatively putting target-version as 3.1.1 till then. > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Critical > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Attachment: HADOOP-15390.02.patch > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Major > Attachments: HADOOP-15390.01.patch, HADOOP-15390.02.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Status: Patch Available (was: Open) > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Major > Attachments: HADOOP-15390.01.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15390) Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens
[ https://issues.apache.org/jira/browse/HADOOP-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HADOOP-15390: --- Attachment: HADOOP-15390.01.patch > Yarn RM logs flooded by DelegationTokenRenewer trying to renew KMS tokens > - > > Key: HADOOP-15390 > URL: https://issues.apache.org/jira/browse/HADOOP-15390 > Project: Hadoop Common > Issue Type: Bug >Reporter: Xiao Chen >Assignee: Xiao Chen >Priority: Major > Attachments: HADOOP-15390.01.patch > > > When looking at a recent issue with [~rkanter] and [~yufeigu], we found that > the RM log in a cluster was flooded by KMS token renewal errors below: > {noformat} > $ tail -9 hadoop-cmf-yarn-RESOURCEMANAGER.log > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > ... > 2018-04-11 11:34:09,367 WARN > org.apache.hadoop.crypto.key.kms.KMSClientProvider$KMSTokenRenewer: > keyProvider null cannot renew dt. > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renewed delegation-token= [Kind: kms-dt, Service: KMSIP:16000, Ident: > (kms-dt owner=user, renewer=yarn, realUser=, issueDate=1522192283334, > maxDate=1522797083334, sequenceNumber=15108613, masterKeyId=2674);exp=0; > apps=[]], for [] > 2018-04-11 11:34:09,367 INFO > org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer: > Renew Kind: kms-dt, Service: KMSIP:16000, Ident: (kms-dt owner=user, > renewer=yarn, realUser=, issueDate=1522192283334, maxDate=1522797083334, > sequenceNumber=15108613, masterKeyId=2674);exp=0; apps=[] in -1523446449367 > ms, appId = [] > {noformat} > Further inspection shows the KMS IP is from another cluster. The RM is before > HADOOP-14445, so needs to read from config. The config rightfully doesn't > have the other cluster's KMS configured. > Although HADOOP-14445 will make this a non-issue by creating the provider > from token service, we should fix 2 things here: > - KMS token renewer should throw instead of return 0. Returning 0 when not > able to renew shall be considered a bug in the renewer. > - Yarn RM's {{DelegationTokenRenewer}} service should validate the return and > not go into this busy loop. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org