[
https://issues.apache.org/jira/browse/YARN-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385897#comment-14385897
]
Advertising
Hadoop QA commented on YARN-2444:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708055/YARN-2444-001.patch
against trunk revision 3d9132d.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/7142//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7142//console
This message is automatically generated.
> Primary filters added after first submission not indexed, cause exceptions in
> logs.
> -----------------------------------------------------------------------------------
>
> Key: YARN-2444
> URL: https://issues.apache.org/jira/browse/YARN-2444
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 2.5.0
> Reporter: Marcelo Vanzin
> Attachments: YARN-2444-001.patch, ats.java,
> org.apache.hadoop.yarn.server.timeline.TestTimelineClientPut-output.txt
>
>
> See attached code for an example. The code creates an entity with a primary
> filter, submits it to the ATS. After that, a new primary filter value is
> added and the entity is resubmitted. At that point two things can be seen:
> - Searching for the new primary filter value does not return the entity
> - The following exception shows up in the logs:
> {noformat}
> 14/08/22 11:33:42 ERROR webapp.TimelineWebServices: Error when verifying
> access for user dr.who (auth:SIMPLE) on the events of the timeline entity {
> id: testid-48625678-9cbb-4e71-87de-93c50be51d1a, type: test }
> org.apache.hadoop.yarn.exceptions.YarnException: Owner information of the
> timeline entity { id: testid-48625678-9cbb-4e71-87de-93c50be51d1a, type: test
> } is corrupted.
> at
> org.apache.hadoop.yarn.server.timeline.security.TimelineACLsManager.checkAccess(TimelineACLsManager.java:67)
> at
> org.apache.hadoop.yarn.server.timeline.webapp.TimelineWebServices.getEntities(TimelineWebServices.java:172)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
