Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 1 Dec 2014 22:26:14 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12757820.1416951810000.52886.1417472774544@Atlassian.JIRA>
In-Reply-To: <JIRA.12757820.1416951810000@Atlassian.JIRA>
References: <JIRA.12757820.1416951810000@Atlassian.JIRA>
 <JIRA.12757820.1416951810215@arcas>
Subject: [jira] [Commented] (YARN-2905) AggregatedLogsBlock page can
 infinitely loop if the aggregated log file is corrupted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230571#comment-14230571 ] 

Jason Lowe commented on YARN-2905:
----------------------------------

+1 lgtm.  Committing this.

> 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
>         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)