[ https://issues.apache.org/jira/browse/YARN-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231380#comment-14231380 ]
Hudson commented on YARN-2905: ------------------------------ SUCCESS: Integrated in Hadoop-Yarn-trunk #761 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/761/]) YARN-2905. AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted. Contributed by Varun Saxena (jlowe: rev 0f9528b99addbb0fd9a19d84db22a8c8e934b05f) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/log/AggregatedLogsBlock.java * hadoop-yarn-project/CHANGES.txt > AggregatedLogsBlock page can infinitely loop if the aggregated log file is > corrupted > ------------------------------------------------------------------------------------ > > Key: YARN-2905 > URL: https://issues.apache.org/jira/browse/YARN-2905 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.5.0 > Reporter: Jason Lowe > Assignee: Varun Saxena > Priority: Blocker > Fix For: 2.7.0 > > Attachments: YARN-2905.patch > > > If the AggregatedLogsBlock page tries to serve up a portion of a log file > that has been corrupted (e.g.: like the case that was fixed by YARN-2724) > then it can spin forever trying to seek to the targeted log segment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)