Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 9 Jul 2016 20:56:11 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12759910.1417819944000.68118.1468097771873@Atlassian.JIRA>
In-Reply-To: <JIRA.12759910.1417819944000@Atlassian.JIRA>
References: <JIRA.12759910.1417819944000@Atlassian.JIRA> <JIRA.12759910.1417819944885@arcas>
Subject: [jira] [Commented] (YARN-2928) YARN Timeline Service: Next
 generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 09 Jul 2016 20:56:18 -0000


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

Sangjin Lee commented on YARN-2928:
-----------------------------------

More analysis:
(1) mvninstall failure (hadoop-mapreduce-client-app)
I cannot reproduce this locally. It looks as though the hadoop-mapreduce-client-app build picked up an older version of hadoop-mapreduce-client-core that does not have this new code. It appears somehow jenkins is picking up wrong jars.

(2) javac errors
Both are from files and code that we did not touch.

(3) javadoc
Fixed.

(4) checkstyle
Fixed 3 more. The remaining checkstyle violations are not related to code changes by us, not practical to fix as part of this (e.g. adding javadoc to a large number of existing classes), or else. I think we have fixed it as much as possible without burdening this JIRA more with a lot of unrelated changes.

(5) unit test failures
- TestGangliaMetrics: known issue (HADOOP-12588)
- TestZKFailoverController: appears that it encountered "connection refused" errors (environment?)
- TestYarnClient: known issue (YARN-4202, YARN-4954)
- TestLogsCLI: known issue (YARN-5313)
- TestContainerManagerSecurity: known issue (YARN-4342)
- TestMiniYarnClusterNodeUtilization: known issue (YARN-4453)

That leaves {{TestMRTimelineEventHandling#testMRNewTimelineServiceEventHandling}}. This is a new test we added. I tried to reproduce this locally, but it is not reproducible on mine (tried a number of times). I'm not exactly sure how this could fail other than it failed to create the directory. The desired directory is correct. I'm going to see if this failure persists with the next run.

> YARN Timeline Service: Next generation
> --------------------------------------
>
>                 Key: YARN-2928
>                 URL: https://issues.apache.org/jira/browse/YARN-2928
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Critical
>         Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf, ATSv2BackendHBaseSchemaproposal.pdf, Data model proposal v1.pdf, The YARN Timeline Service v.2 Documentation.pdf, Timeline Service Next Gen - Planning - ppt.pptx, TimelineServiceStoragePerformanceTestSummaryYARN-2928.pdf, YARN-2928.01.patch, YARN-2928.02.patch, YARN-2928.03.patch, timeline_service_v2_next_milestones.pdf
>
>
> We have the application timeline server implemented in yarn per YARN-1530 and YARN-321. Although it is a great feature, we have recognized several critical issues and features that need to be addressed.
> This JIRA proposes the design and implementation changes to address those. This is phase 1 of this effort.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org