[jira] [Updated] (YARN-8210) AMRMClient logging on every heartbeat to track updation of AM RM token causes too many log lines to be generated in AM logs
[ https://issues.apache.org/jira/browse/YARN-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-8210: Fix Version/s: (was: 2.10.2) 2.10.1 > AMRMClient logging on every heartbeat to track updation of AM RM token causes > too many log lines to be generated in AM logs > --- > > Key: YARN-8210 > URL: https://issues.apache.org/jira/browse/YARN-8210 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0, 3.0.0-alpha1 >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Major > Fix For: 3.2.0, 3.1.1, 3.0.3, 2.10.1 > > Attachments: YARN-8210.1.patch > > > YARN-4682 added logs to track when AM RM token is updated for debuggability > purposes. However this is printed on every heartbeat and could cause the AM > logs to be flooded with this whenever RM's Master key is rolled over > especially if its a long running AM. Hence proposing to remove this log line. > As explained in > https://issues.apache.org/jira/browse/YARN-3104?focusedCommentId=14298692&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14298692 > , the AM-RM connection is not re-established so the updated token in the > client's UGI is never re-sent to the RPC server andRM continues to send the > token each heartbeat since it cannot be sure whether the client really has > the new token. Hence the log lines are printed on every heartbeat. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8210) AMRMClient logging on every heartbeat to track updation of AM RM token causes too many log lines to be generated in AM logs
[ https://issues.apache.org/jira/browse/YARN-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-8210: Fix Version/s: 2.10.2 Pushed to branch-2.10. > AMRMClient logging on every heartbeat to track updation of AM RM token causes > too many log lines to be generated in AM logs > --- > > Key: YARN-8210 > URL: https://issues.apache.org/jira/browse/YARN-8210 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0, 3.0.0-alpha1 >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Major > Fix For: 3.2.0, 3.1.1, 3.0.3, 2.10.2 > > Attachments: YARN-8210.1.patch > > > YARN-4682 added logs to track when AM RM token is updated for debuggability > purposes. However this is printed on every heartbeat and could cause the AM > logs to be flooded with this whenever RM's Master key is rolled over > especially if its a long running AM. Hence proposing to remove this log line. > As explained in > https://issues.apache.org/jira/browse/YARN-3104?focusedCommentId=14298692&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14298692 > , the AM-RM connection is not re-established so the updated token in the > client's UGI is never re-sent to the RPC server andRM continues to send the > token each heartbeat since it cannot be sure whether the client really has > the new token. Hence the log lines are printed on every heartbeat. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8210) AMRMClient logging on every heartbeat to track updation of AM RM token causes too many log lines to be generated in AM logs
[ https://issues.apache.org/jira/browse/YARN-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-8210: --- Attachment: YARN-8210.1.patch > AMRMClient logging on every heartbeat to track updation of AM RM token causes > too many log lines to be generated in AM logs > --- > > Key: YARN-8210 > URL: https://issues.apache.org/jira/browse/YARN-8210 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0, 3.0.0-alpha1 >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Major > Attachments: YARN-8210.1.patch > > > YARN-4682 added logs to track when AM RM token is updated for debuggability > purposes. However this is printed on every heartbeat and could cause the AM > logs to be flooded with this whenever RM's Master key is rolled over > especially if its a long running AM. Hence proposing to remove this log line. > As explained in > https://issues.apache.org/jira/browse/YARN-3104?focusedCommentId=14298692&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14298692 > , the AM-RM connection is not re-established so the updated token in the > client's UGI is never re-sent to the RPC server andRM continues to send the > token each heartbeat since it cannot be sure whether the client really has > the new token. Hence the log lines are printed on every heartbeat. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8210) AMRMClient logging on every heartbeat to track updation of AM RM token causes too many log lines to be generated in AM logs
[ https://issues.apache.org/jira/browse/YARN-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-8210: --- Description: YARN-4682 added logs to track when AM RM token is updated for debuggability purposes. However this is printed on every heartbeat and could cause the AM logs to be flooded with this whenever RM's Master key is rolled over especially if its a long running AM. Hence proposing to remove this log line. As explained in https://issues.apache.org/jira/browse/YARN-3104?focusedCommentId=14298692&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14298692 , the AM-RM connection is not re-established so the updated token in the client's UGI is never re-sent to the RPC server andRM continues to send the token each heartbeat since it cannot be sure whether the client really has the new token. Hence the log lines are printed on every heartbeat. (was: YARN-4682 added logs to track when AM RM token is updated for debuggability purposes. However this is printed on every heartbeat and could cause the AM logs to be flooded with this whenever RM's Master key is rolled over especially if its a long running AM. Hence proposing to remove this log line) > AMRMClient logging on every heartbeat to track updation of AM RM token causes > too many log lines to be generated in AM logs > --- > > Key: YARN-8210 > URL: https://issues.apache.org/jira/browse/YARN-8210 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0, 3.0.0-alpha1 >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad >Priority: Major > > YARN-4682 added logs to track when AM RM token is updated for debuggability > purposes. However this is printed on every heartbeat and could cause the AM > logs to be flooded with this whenever RM's Master key is rolled over > especially if its a long running AM. Hence proposing to remove this log line. > As explained in > https://issues.apache.org/jira/browse/YARN-3104?focusedCommentId=14298692&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14298692 > , the AM-RM connection is not re-established so the updated token in the > client's UGI is never re-sent to the RPC server andRM continues to send the > token each heartbeat since it cannot be sure whether the client really has > the new token. Hence the log lines are printed on every heartbeat. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
