[jira] [Resolved] (YARN-6822) TestContainerManagerSecurity tests fail on trunk
[
https://issues.apache.org/jira/browse/YARN-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved YARN-6822.
-
Resolution: Duplicate
Fixed by YARN-6150. Please feel free to reopen this if the error is not fixed.
> TestContainerManagerSecurity tests fail on trunk
>
>
> Key: YARN-6822
> URL: https://issues.apache.org/jira/browse/YARN-6822
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
> Environment: Ubuntu 14.04
> x86, ppc64le
> $ java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sonia Garudi
>
> {code}
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager[0]
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.processWaitTimeAndRetryInfo(RetryInvocationHandler.java:130)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:107)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:348)
> at com.sun.proxy.$Proxy91.startContainers(Unknown Source)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.startContainer(TestContainerManagerSecurity.java:557)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testStartContainer(TestContainerManagerSecurity.java:478)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testNMTokens(TestContainerManagerSecurity.java:253)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager(TestContainerManagerSecurity.java:158)
> {code}
> {code}
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager[1]
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.processWaitTimeAndRetryInfo(RetryInvocationHandler.java:130)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:107)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:348)
> at com.sun.proxy.$Proxy91.startContainers(Unknown Source)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.startContainer(TestContainerManagerSecurity.java:557)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testStartContainer(TestContainerManagerSecurity.java:478)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testNMTokens(TestContainerManagerSecurity.java:253)
> at
> org.apache.hadoop.yarn.server.TestContainerManagerSecurity.testContainerManager(TestContainerManagerSecurity.java:158)
> {code}
> Logs -
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/463/testReport/org.apache.hadoop.yarn.server/TestContainerManagerSecurity/testContainerManager_0_/
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/463/testReport/org.apache.hadoop.yarn.server/TestContainerManagerSecurity/testContainerManager_1_/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6866) Minor clean-up and fixes in anticipation of merge with trunk
Subru Krishnan created YARN-6866: Summary: Minor clean-up and fixes in anticipation of merge with trunk Key: YARN-6866 URL: https://issues.apache.org/jira/browse/YARN-6866 Project: Hadoop YARN Issue Type: Sub-task Components: federation Reporter: Subru Krishnan Assignee: Botong Huang We have done e2e testing of YARN Federation sucessfully and we have minor cleans-up like pom version upgrade, redudant "." in configuration string, documentation updates etc which we want to clean up before the merge to trunk. This jira tracks the fixes we did as described above to ensure proper e2e run. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6865) FSLeafQueue.context should be final
Daniel Templeton created YARN-6865: -- Summary: FSLeafQueue.context should be final Key: YARN-6865 URL: https://issues.apache.org/jira/browse/YARN-6865 Project: Hadoop YARN Issue Type: Improvement Components: fairscheduler Affects Versions: 3.0.0-alpha4 Reporter: Daniel Templeton Assignee: Laura Torres Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re:
I have done the change. All committers, 2.8.2 release is supposed to be a stable/production release for branch-2.8. For commits to go for 2.8.2 release (only important and low risk bug fixes), please commit to trunk, branch-2, branch-2.8 and branch-2.8.2. For unimportant or high risk bug fixes/improvements, please commit to branch-2.8 (trunk/branch-2) only and mark JIRA fixed as 2.8.3. Thanks for your cooperation! Thanks, Junping From: Junping Du Sent: Monday, July 24, 2017 10:36 AM To: Brahma Reddy Battula; Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe; humbed...@apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan Nice catch, Brahma. Actually, this is not supposed to be happen as we all should know the patch should firstly get landed on branch-2.8 (as well as trunk, branch-2) before landed on branch-2.8.2. Anyway, we will always check JIRAs claim to fixed in a specific release version with commits actually landing on the releasing branch before kicking off RC. So, I am not too worry about this mistaking behaviors as it happens in every releases. If no other concerns, I will do the branch update in next 30 minutes. Thanks, Junping From: Brahma Reddy Battula Sent: Sunday, July 23, 2017 1:50 AM To: Junping Du; Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe; humbed...@apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan Just executed the "git log branch-2.8 ^branch-2.8.2" found two commits are missed (HDFS-8312 and HADOOP-13867 ) in branch-2.8.I just pushed this two commits.Hope we'll not miss any commits which present in only in branch-2.8.2. From: Junping Du Sent: Saturday, July 22, 2017 5:57 AM To: Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe; humbed...@apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan Already get back from Daniel who is from ASF INFRA team, I plan to do following operations on next Monday morning: 1. Drop current branch-2.8.2 and recut branch-2.8.2 from branch-2.8 2. Drop abandoned branch-2.8.1 and rename branch-2.8.1-private to branch-2.8.1 where we just released 2.8.1 from. I will also adjust fix version on all affected JIRA accordingly. If you have any concerns on above operations, please raise it before the end of this Sunday (7/23). Thanks, Junping From: Junping Du Sent: Friday, July 21, 2017 2:29 PM To: Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe Subject: Re: Apache Hadoop 2.8.2 Release Plan Make sense, just raise: https://issues.apache.org/jira/browse/INFRA-14669 Thanks, Junping From: Vinod Kumar Vavilapalli Sent: Friday, July 21, 2017 12:31 PM To: Junping Du Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe Subject: Re: Apache Hadoop 2.8.2 Release Plan Junping, If we are looking at a month, I’d not rebranch branch-2.8.2 right now given how these things go. We can just continue to commit on branch-2.8 for now. I also think we should just follow up with ASF INFRA and clean up the branches - Delete branch-2.8.2 so that we can recreate it afresh a little later. - branch-2.8.1 is also stale and it should be deleted. branch-2.8.1-private should be renamed to branch-2.8.1 Thanks +Vinod > On Jul 21, 2017, at 11:23 AM, Junping Du wrote: > > Thanks for suggestions, Jason and Kihwal! > +1 on releasing 2.8.2 on latest branch-2.8 too. Practically, if branch-2.8.2 > cannot be abandoned/replaced (suspect all branches are read-only now), I will > manually merge all commits that not landed on 2.8.2 yet. > > Thanks, > > Junping > > From: Jason Lowe > Sent: Friday, July 21, 2017 8:17 AM > To: Kihwal Lee; Junping Du; common-...@hadoop.apache.org; > hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; > yarn-dev@hadoop.apache.org > Subject: Re: Apache Hadoop 2.8.2 Release Plan > > +1 to base the 2.8.2 release off of the more recent activity on branch-2.8. > Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that > are in branch-2.8. There also are a lot of JIRAs that claim they are fixed > in 2.8.2 but are not in branch-2.8.2. Having the 2.8.2 release be based on > recent activity in branch-2.8 would solve both of these issues, and we'd only > need to move the handful of JIRA
[DISCUSS] Looking to a 2.9.0 release
Folks, With the release for 2.8, we would like to look ahead to 2.9 release as there are many features/improvements in branch-2 (about 1062 commits), that are in need of a release vechile. Here's our first cut of the proposal from the YARN side: 1. Scheduler improvements (decoupling allocation from node heartbeat, allocation ID, concurrency fixes, LightResource etc). 2. Timeline Service v2 3. Opportunistic containers 4. Federation We would like to hear a formal list from HDFS & Hadoop (& MapReduce if any) and will update the Roadmap wiki accordingly. Considering our familiarity with the above mentioned YARN features, we would like to volunteer as the co-RMs for 2.9.0. We want to keep the timeline at 8-12 weeks to keep the release pragmatic. Feedback? -Subru/Arun
[jira] [Created] (YARN-6864) FSPreemptionThread cleanup for readability
Daniel Templeton created YARN-6864: -- Summary: FSPreemptionThread cleanup for readability Key: YARN-6864 URL: https://issues.apache.org/jira/browse/YARN-6864 Project: Hadoop YARN Issue Type: Bug Components: fairscheduler Affects Versions: 3.0.0-alpha4 Reporter: Daniel Templeton Assignee: Daniel Templeton Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6863) Fair Scheduler preemption thread should check that a container has the needed resources before adding it to the preemption list
Daniel Templeton created YARN-6863:
--
Summary: Fair Scheduler preemption thread should check that a
container has the needed resources before adding it to the preemption list
Key: YARN-6863
URL: https://issues.apache.org/jira/browse/YARN-6863
Project: Hadoop YARN
Issue Type: Bug
Components: fairscheduler
Affects Versions: 3.0.0-alpha4
Reporter: Daniel Templeton
Priority: Minor
In {{FSPreemptionThread.identifyContainersToPreempt()}}, we add every container
we encounter to the preemption list until we meet the desired target. As we
head into resource types, that behavior will become more of a problem, but it's
technically an issue already because the fair scheduler supports requests with
0 vcores or 0 memory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 2.8.2 Release Plan
Nice catch, Brahma. Actually, this is not supposed to be happen as we all should know the patch should firstly get landed on branch-2.8 (as well as trunk, branch-2) before landed on branch-2.8.2. Anyway, we will always check JIRAs claim to fixed in a specific release version with commits actually landing on the releasing branch before kicking off RC. So, I am not too worry about this mistaking behaviors as it happens in every releases. If no other concerns, I will do the branch update in next 30 minutes. Thanks, Junping From: Brahma Reddy Battula Sent: Sunday, July 23, 2017 1:50 AM To: Junping Du; Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe; humbed...@apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan Just executed the "git log branch-2.8 ^branch-2.8.2" found two commits are missed (HDFS-8312 and HADOOP-13867 ) in branch-2.8.I just pushed this two commits.Hope we'll not miss any commits which present in only in branch-2.8.2. From: Junping Du Sent: Saturday, July 22, 2017 5:57 AM To: Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe; humbed...@apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan Already get back from Daniel who is from ASF INFRA team, I plan to do following operations on next Monday morning: 1. Drop current branch-2.8.2 and recut branch-2.8.2 from branch-2.8 2. Drop abandoned branch-2.8.1 and rename branch-2.8.1-private to branch-2.8.1 where we just released 2.8.1 from. I will also adjust fix version on all affected JIRA accordingly. If you have any concerns on above operations, please raise it before the end of this Sunday (7/23). Thanks, Junping From: Junping Du Sent: Friday, July 21, 2017 2:29 PM To: Vinod Kumar Vavilapalli Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe Subject: Re: Apache Hadoop 2.8.2 Release Plan Make sense, just raise: https://issues.apache.org/jira/browse/INFRA-14669 Thanks, Junping From: Vinod Kumar Vavilapalli Sent: Friday, July 21, 2017 12:31 PM To: Junping Du Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Jason Lowe Subject: Re: Apache Hadoop 2.8.2 Release Plan Junping, If we are looking at a month, I’d not rebranch branch-2.8.2 right now given how these things go. We can just continue to commit on branch-2.8 for now. I also think we should just follow up with ASF INFRA and clean up the branches - Delete branch-2.8.2 so that we can recreate it afresh a little later. - branch-2.8.1 is also stale and it should be deleted. branch-2.8.1-private should be renamed to branch-2.8.1 Thanks +Vinod > On Jul 21, 2017, at 11:23 AM, Junping Du wrote: > > Thanks for suggestions, Jason and Kihwal! > +1 on releasing 2.8.2 on latest branch-2.8 too. Practically, if branch-2.8.2 > cannot be abandoned/replaced (suspect all branches are read-only now), I will > manually merge all commits that not landed on 2.8.2 yet. > > Thanks, > > Junping > > From: Jason Lowe > Sent: Friday, July 21, 2017 8:17 AM > To: Kihwal Lee; Junping Du; common-...@hadoop.apache.org; > hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; > yarn-dev@hadoop.apache.org > Subject: Re: Apache Hadoop 2.8.2 Release Plan > > +1 to base the 2.8.2 release off of the more recent activity on branch-2.8. > Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that > are in branch-2.8. There also are a lot of JIRAs that claim they are fixed > in 2.8.2 but are not in branch-2.8.2. Having the 2.8.2 release be based on > recent activity in branch-2.8 would solve both of these issues, and we'd only > need to move the handful of JIRAs that have marked themselves correctly as > fixed in 2.8.3 to be fixed in 2.8.2. > > Jason > > >On Friday, July 21, 2017 10:01 AM, Kihwal Lee > wrote: > > > Thanks for driving the next 2.8 release, Junping. While I was committing a > blocker for 2.7.4, I noticed some of the jiras are back-ported to 2.7, but > missing in branch-2.8.2. Perhaps it is safer and easier to simply rebranch > 2.8.2. > Thanks,Kihwal > > On Thursday, July 20, 2017, 3:32:16 PM CDT, Junping Du > wrote: > > Hi all, >Per Vinod's previous email, we just announce Apache Hadoop 2.8.1 get > released today which is a special security release. Now, we should work > towards 2.8.2 release which aim for production deployment. The focus > obviously is to fix blocker/critical issues [2], bug-fixes and *no* features
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/474/ [Jul 24, 2017 6:09:03 AM] (sunilg) YARN-6102. RMActiveService context to be updated with new RMContext on -1 overall The following subsystems voted -1: findbugs unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: FindBugs : module:hadoop-hdfs-project/hadoop-hdfs-client Possible exposure of partially initialized object in org.apache.hadoop.hdfs.DFSClient.initThreadsNumForStripedReads(int) At DFSClient.java:object in org.apache.hadoop.hdfs.DFSClient.initThreadsNumForStripedReads(int) At DFSClient.java:[line 2888] org.apache.hadoop.hdfs.server.protocol.SlowDiskReports.equals(Object) makes inefficient use of keySet iterator instead of entrySet iterator At SlowDiskReports.java:keySet iterator instead of entrySet iterator At SlowDiskReports.java:[line 105] FindBugs : module:hadoop-hdfs-project/hadoop-hdfs Possible null pointer dereference in org.apache.hadoop.hdfs.qjournal.server.JournalNode.getJournalsStatus() due to return value of called method Dereferenced at JournalNode.java:org.apache.hadoop.hdfs.qjournal.server.JournalNode.getJournalsStatus() due to return value of called method Dereferenced at JournalNode.java:[line 302] org.apache.hadoop.hdfs.server.common.HdfsServerConstants$StartupOption.setClusterId(String) unconditionally sets the field clusterId At HdfsServerConstants.java:clusterId At HdfsServerConstants.java:[line 193] org.apache.hadoop.hdfs.server.common.HdfsServerConstants$StartupOption.setForce(int) unconditionally sets the field force At HdfsServerConstants.java:force At HdfsServerConstants.java:[line 217] org.apache.hadoop.hdfs.server.common.HdfsServerConstants$StartupOption.setForceFormat(boolean) unconditionally sets the field isForceFormat At HdfsServerConstants.java:isForceFormat At HdfsServerConstants.java:[line 229] org.apache.hadoop.hdfs.server.common.HdfsServerConstants$StartupOption.setInteractiveFormat(boolean) unconditionally sets the field isInteractiveFormat At HdfsServerConstants.java:isInteractiveFormat At HdfsServerConstants.java:[line 237] Possible null pointer dereference in org.apache.hadoop.hdfs.server.datanode.DataStorage.linkBlocksHelper(File, File, int, HardLink, boolean, File, List) due to return value of called method Dereferenced at DataStorage.java:org.apache.hadoop.hdfs.server.datanode.DataStorage.linkBlocksHelper(File, File, int, HardLink, boolean, File, List) due to return value of called method Dereferenced at DataStorage.java:[line 1339] Possible null pointer dereference in org.apache.hadoop.hdfs.server.namenode.NNStorageRetentionManager.purgeOldLegacyOIVImages(String, long) due to return value of called method Dereferenced at NNStorageRetentionManager.java:org.apache.hadoop.hdfs.server.namenode.NNStorageRetentionManager.purgeOldLegacyOIVImages(String, long) due to return value of called method Dereferenced at NNStorageRetentionManager.java:[line 258] Possible null pointer dereference in org.apache.hadoop.hdfs.server.namenode.NNUpgradeUtil$1.visitFile(Path, BasicFileAttributes) due to return value of called method Dereferenced at NNUpgradeUtil.java:org.apache.hadoop.hdfs.server.namenode.NNUpgradeUtil$1.visitFile(Path, BasicFileAttributes) due to return value of called method Dereferenced at NNUpgradeUtil.java:[line 133] Useless condition:argv.length >= 1 at this point At DFSAdmin.java:[line 2096] Useless condition:numBlocks == -1 at this point At ImageLoaderCurrent.java:[line 727] FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager Useless object stored in variable removedNullContainers of method org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.removeOrTrackCompletedContainersFromContext(List) At NodeStatusUpdaterImpl.java:removedNullContainers of method org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.removeOrTrackCompletedContainersFromContext(List) At NodeStatusUpdaterImpl.java:[line 642] org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.removeVeryOldStoppedContainersFromCache() makes inefficient use of keySet iterator instead of entrySet iterator At NodeStatusUpdaterImpl.java:keySet iterator instead of entrySet iterator At NodeStatusUpdaterImpl.java:[line 719] Hard coded reference to an absolute pathname in org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(ContainerRuntimeContext) At DockerLinuxContainerRuntime.java:absolute pathname in org.apache.hadoop.yarn.server.node
[jira] [Created] (YARN-6862) There is a bug in computing resource usage in NM.
YunFan Zhou created YARN-6862: - Summary: There is a bug in computing resource usage in NM. Key: YARN-6862 URL: https://issues.apache.org/jira/browse/YARN-6862 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Affects Versions: 2.8.2 Reporter: YunFan Zhou Fix For: 2.8.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6861) Reader API for sub application entities
Rohith Sharma K S created YARN-6861: --- Summary: Reader API for sub application entities Key: YARN-6861 URL: https://issues.apache.org/jira/browse/YARN-6861 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S Assignee: Rohith Sharma K S YARN-6733 and YARN-6734 writes data into sub application table. There should be a way to read those entities. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Resolved] (YARN-6860) TestRMRestart.testFinishedAppRemovalAfterRMRestart fails intermittently
[
https://issues.apache.org/jira/browse/YARN-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved YARN-6860.
-
Resolution: Duplicate
> TestRMRestart.testFinishedAppRemovalAfterRMRestart fails intermittently
> ---
>
> Key: YARN-6860
> URL: https://issues.apache.org/jira/browse/YARN-6860
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
> Attachments: YARN-6860.01.patch
>
>
> https://builds.apache.org/job/PreCommit-YARN-Build/16528/testReport/org.apache.hadoop.yarn.server.resourcemanager/TestRMRestart/testFinishedAppRemovalAfterRMRestart/
> {noformat}
> java.lang.AssertionError: expected null, but was: application_submission_context { application_id { id: 1 cluster_timestamp:
> 1500886835515 } application_name: "" queue: "default" priority { priority: 0
> } am_container_spec { } cancel_tokens_when_complete: true maxAppAttempts: 2
> resource { memory: 1024 virtual_cores: 1 } applicationType: "YARN"
> keep_containers_across_application_attempts: false
> attempt_failures_validity_interval: 0 am_container_resource_request {
> priority { priority: 0 } resource_name: "*" capability { memory: 1024
> virtual_cores: 1 } num_containers: 1 relax_locality: true
> node_label_expression: "" execution_type_request { execution_type: GUARANTEED
> enforce_execution_type: false } } } user: "jenkins" start_time: 1500886835535
> application_state: RMAPP_FINISHED finish_time: 1500886835559>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotNull(Assert.java:664)
> at org.junit.Assert.assertNull(Assert.java:646)
> at org.junit.Assert.assertNull(Assert.java:656)
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testFinishedAppRemovalAfterRMRestart(TestRMRestart.java:1673)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6860) TestRMRestart.testFinishedAppRemovalAfterRMRestart fails intermittently
Akira Ajisaka created YARN-6860:
---
Summary: TestRMRestart.testFinishedAppRemovalAfterRMRestart fails
intermittently
Key: YARN-6860
URL: https://issues.apache.org/jira/browse/YARN-6860
Project: Hadoop YARN
Issue Type: Bug
Components: test
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka
https://builds.apache.org/job/PreCommit-YARN-Build/16528/testReport/org.apache.hadoop.yarn.server.resourcemanager/TestRMRestart/testFinishedAppRemovalAfterRMRestart/
{noformat}
java.lang.AssertionError: expected null, but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:664)
at org.junit.Assert.assertNull(Assert.java:646)
at org.junit.Assert.assertNull(Assert.java:656)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testFinishedAppRemovalAfterRMRestart(TestRMRestart.java:1673)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6859) Add missing test scope to the zookeeper dependency in hadoop-yarn-server-resourcemanager test-jar
Akira Ajisaka created YARN-6859:
---
Summary: Add missing test scope to the zookeeper dependency in
hadoop-yarn-server-resourcemanager test-jar
Key: YARN-6859
URL: https://issues.apache.org/jira/browse/YARN-6859
Project: Hadoop YARN
Issue Type: Bug
Components: build
Reporter: Akira Ajisaka
Priority: Minor
Reported by Sean Mackrory in common-dev ML. When compiling Apache Hadoop with
{{-Dzookeeper.version=3.5.3-beta}}, the build fails by the following error:
{noformat}
[WARNING]
Dependency convergence error for org.apache.zookeeper:zookeeper:3.5.3-beta
paths to dependency are:
+-org.apache.hadoop:hadoop-yarn-server-tests:3.0.0-beta1-SNAPSHOT
+-org.apache.hadoop:hadoop-common:3.0.0-beta1-SNAPSHOT
+-org.apache.zookeeper:zookeeper:3.5.3-beta
...
and
+-org.apache.hadoop:hadoop-yarn-server-tests:3.0.0-beta1-SNAPSHOT
+-org.apache.hadoop:hadoop-yarn-server-resourcemanager:3.0.0-beta1-SNAPSHOT
+-org.apache.zookeeper:zookeeper:3.5.3-beta
and
+-org.apache.hadoop:hadoop-yarn-server-tests:3.0.0-beta1-SNAPSHOT
+-org.apache.hadoop:hadoop-yarn-server-resourcemanager:3.0.0-beta1-SNAPSHOT
+-org.apache.zookeeper:zookeeper:3.4.9
...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
