[jira] [Resolved] (YARN-11187) Remove WhiteBox in yarn module.

2022-10-06 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11187.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Committed to trunk. Thank you [~slfan1989] for your contribution.

> Remove WhiteBox in yarn module.
> ---
>
> Key: YARN-11187
> URL: https://issues.apache.org/jira/browse/YARN-11187
> Project: Hadoop YARN
>  Issue Type: Improvement
>Affects Versions: 3.4.0, 3.3.5
>Reporter: fanshilun
>Assignee: fanshilun
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11301) Fix NoClassDefFoundError: org/junit/platform/launcher/core/LauncherFactory after YARN-11269

2022-09-13 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11301.
--
Fix Version/s: 3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Committed to trunk. Thank you [~slfan1989] for your fix.

> Fix NoClassDefFoundError: org/junit/platform/launcher/core/LauncherFactory 
> after YARN-11269
> ---
>
> Key: YARN-11301
> URL: https://issues.apache.org/jira/browse/YARN-11301
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: timelineserver
>Affects Versions: 3.4.0
>Reporter: fanshilun
>Assignee: fanshilun
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>
> After the Apache Hadoop YARN Timeline Plugin Storage module was upgraded from 
> junit 4 to 5, a compilation error occurred.
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:
> test (default-test) on project hadoop-yarn-server-timeline-pluginstorage: 
> Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test failed: 
> java.lang.NoClassDefFoundError: 
> org/junit/platform/launcher/core/LauncherFactory: 
> org.junit.platform.launcher.core.LauncherFactory -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException 
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11241) Add uncleaning option for local app log file with log-aggregation enabled

2022-09-12 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11241.
--
Fix Version/s: 3.4.0
   3.3.9
   Resolution: Fixed

Committed to trunk and branch-3.3. Thank you [~groot] for your contribution!

> Add uncleaning option for local app log file with log-aggregation enabled
> -
>
> Key: YARN-11241
> URL: https://issues.apache.org/jira/browse/YARN-11241
> Project: Hadoop YARN
>  Issue Type: New Feature
>  Components: log-aggregation
>Reporter: groot
>Assignee: groot
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add uncleaning option for local app log file with log-aggregation enabled
> This will be helpful for debugging purpose.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11287) Fix NoClassDefFoundError: org/junit/platform/launcher/core/LauncherFactory After YARN-10793

2022-08-30 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11287.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Committed to trunk. Thank you [~slfan1989] for reporting and fixing this issue.

> Fix NoClassDefFoundError: org/junit/platform/launcher/core/LauncherFactory 
> After YARN-10793
> ---
>
> Key: YARN-11287
> URL: https://issues.apache.org/jira/browse/YARN-11287
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: fanshilun
>Assignee: fanshilun
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>
> After executing the yarn-project global unit test, I found the following 
> error:
> {code:java}
> ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test (default-test) 
> on project hadoop-yarn-server-applicationhistoryservice: Execution 
> default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test failed: 
> java.lang.NoClassDefFoundError: 
> org/junit/platform/launcher/core/LauncherFactory: 
> org.junit.platform.launcher.core.LauncherFactory -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hadoop-yarn-server-applicationhistoryservice {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11254) hadoop-minikdc dependency duplicated in hadoop-yarn-server-nodemanager pom.xml

2022-08-20 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11254.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Committed to trunk. Thank you [~clara0]!

> hadoop-minikdc dependency duplicated in hadoop-yarn-server-nodemanager pom.xml
> --
>
> Key: YARN-11254
> URL: https://issues.apache.org/jira/browse/YARN-11254
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Reporter: Clara Fang
>Assignee: Clara Fang
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>
> The dependency hadoop-minikdc is defined twice in 
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml
> {code:xml}
> 
> org.apache.hadoop
> hadoop-minikdc
> test
> 
> 
> org.apache.hadoop
> hadoop-minikdc
> test
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11257) Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few unit test failure

2022-08-20 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11257.
--
Resolution: Duplicate

This issue has been fixed by YARN-11269. Closing.

> Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few 
> unit test failure
> ---
>
> Key: YARN-11257
> URL: https://issues.apache.org/jira/browse/YARN-11257
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: groot
>Assignee: groot
>Priority: Major
>  Labels: pull-request-available
>
> We need to add Junit 5 dependency in
> {code:java}
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
> as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and 
> we have already upgraded from Junit 4 to 5 in TimelineStoreTestUtils.
>  
> Failing UTs 
> -[https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11248) Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING

2022-08-16 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11248.
--
Fix Version/s: 3.4.0
   3.3.9
   Resolution: Fixed

Committed to trunk and branch-3.3. Thank you [~groot] for your contribution.

> Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING
> ---
>
> Key: YARN-11248
> URL: https://issues.apache.org/jira/browse/YARN-11248
> Project: Hadoop YARN
>  Issue Type: Test
>  Components: test
>Affects Versions: 3.3.3
>Reporter: groot
>Assignee: groot
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.9
>
>
> Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice

2022-08-07 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10793.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Committed to trunk. Thank you [~groot] for your contribution.

> Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
> -
>
> Key: YARN-10793
> URL: https://issues.apache.org/jira/browse/YARN-10793
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: ANANDA G B
>Assignee: groot
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11119) Backport YARN-10538 to branch-2.10

2022-06-26 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9.
--
Fix Version/s: 2.10.3
   Resolution: Fixed

Committed to branch-2.10. Thank you [~groot] for your contribution.

> Backport YARN-10538 to branch-2.10
> --
>
> Key: YARN-9
> URL: https://issues.apache.org/jira/browse/YARN-9
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.10.0
>Reporter: Ashutosh Gupta
>Assignee: Ashutosh Gupta
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.10.3
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Backport YARN-10538 to branch-2.10
>  
> Add recommissioning nodes to the list of updated nodes returned to the AM



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10303) One yarn rest api example of yarn document is error

2022-06-23 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10303.
--
Resolution: Fixed

> One yarn rest api example of yarn document is error
> ---
>
> Key: YARN-10303
> URL: https://issues.apache.org/jira/browse/YARN-10303
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.1.1, 3.2.1
>Reporter: bright.zhou
>Assignee: Ashutosh Gupta
>Priority: Minor
>  Labels: documentation, newbie, pull-request-available
> Fix For: 3.4.0
>
> Attachments: image-2020-06-02-10-27-35-020.png
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> deSelects value should be resourceRequests
> !image-2020-06-02-10-27-35-020.png!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11128) Fix comments in TestProportionalCapacityPreemptionPolicy*

2022-05-26 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11128.
--
Fix Version/s: 3.4.0
   3.3.4
   Resolution: Fixed

Committed to trunk and branch-3.3. Thanks!

> Fix comments in TestProportionalCapacityPreemptionPolicy*
> -
>
> Key: YARN-11128
> URL: https://issues.apache.org/jira/browse/YARN-11128
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacityscheduler, documentation
>Reporter: groot
>Assignee: groot
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.4
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> At various places, comment for appsConfig is 
> {{// queueName\t(priority,resource,host,expression,#repeat,reserved,pending)}}
> but should be 
> {{// 
> queueName\t(priority,resource,host,expression,#repeat,reserved,pending,user)}}
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11092) Upgrade jquery ui to 1.13.1

2022-05-16 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11092.
--
Fix Version/s: 3.4.0
   3.2.4
   3.3.4
   Resolution: Fixed

Committed to trunk, branch-3.3, and branch-3.2. Thank you [~dmmkr] for the 
report and thank you [~groot] for your contribution.

> Upgrade jquery ui to 1.13.1
> ---
>
> Key: YARN-11092
> URL: https://issues.apache.org/jira/browse/YARN-11092
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: D M Murali Krishna Reddy
>Assignee: Ashutosh Gupta
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.4
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The current jquery-ui version used(1.12.1) in the trunk has the following 
> vulnerabilities CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, so we need to 
> upgrade to at least 1.13.0.
>  
> Also currently for the UI2 we are using the shims repo which is not being 
> maintained as per the discussion 
> [https://github.com/components/jqueryui/issues/70] , so if possible we should 
> move to the main jquery repo [https://github.com/jquery/jquery-ui] 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11125) Backport YARN-6483 to branch-2.10

2022-05-13 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11125.
--
Fix Version/s: 2.10.2
   Resolution: Fixed

Merged the PR into branch-2.10. Thank you [~groot] for your contribution.

> Backport YARN-6483 to branch-2.10
> -
>
> Key: YARN-11125
> URL: https://issues.apache.org/jira/browse/YARN-11125
> Project: Hadoop YARN
>  Issue Type: Improvement
>  Components: resourcemanager
>Reporter: Ashutosh Gupta
>Assignee: Ashutosh Gupta
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.10.2
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Backport YARN-6483 to branch-2.10



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-11149) Add regression test cases for YARN-11073

2022-05-13 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-11149:


 Summary: Add regression test cases for YARN-11073
 Key: YARN-11149
 URL: https://issues.apache.org/jira/browse/YARN-11149
 Project: Hadoop YARN
  Issue Type: Test
  Components: test
Reporter: Akira Ajisaka


Add regression test cases for YARN-11073



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11073) CapacityScheduler DRF Preemption kicked in incorrectly for low-capacity queues

2022-05-13 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11073.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Merged the PR into trunk. Let's add test cases in a separate JIRA.

> CapacityScheduler DRF Preemption kicked in incorrectly for low-capacity queues
> --
>
> Key: YARN-11073
> URL: https://issues.apache.org/jira/browse/YARN-11073
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacity scheduler, scheduler preemption
>Affects Versions: 2.10.1
>Reporter: Jian Chen
>Assignee: Jian Chen
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
> Attachments: YARN-11073.tmp-1.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> When running a Hive job in a low-capacity queue on an idle cluster, 
> preemption kicked in to preempt job containers even though there's no other 
> job running and competing for resources. 
> Let's take this scenario as an example:
>  * cluster resource : 
>  ** {_}*queue_low*{_}: min_capacity 1%
>  ** queue_mid: min_capacity 19%
>  ** queue_high: min_capacity 80%
>  * CapacityScheduler with DRF
> During the fifo preemption candidates selection process, the 
> _preemptableAmountCalculator_ needs to first "{_}computeIdealAllocation{_}" 
> which depends on each queue's guaranteed/min capacity. A queue's guaranteed 
> capacity is currently calculated as 
> "Resources.multiply(totalPartitionResource, absCapacity)", so the guaranteed 
> capacity of queue_low is:
>  * {_}*queue_low*{_}:  = 
> , but since the Resource object takes only Long 
> values, these Doubles values get casted into Long, and then the final result 
> becomes **
> Because the guaranteed capacity of queue_low is 0, its normalized guaranteed 
> capacity based on active queues is also 0 based on the current algorithm in 
> "{_}resetCapacity{_}". This eventually leads to the continuous preemption of 
> job containers running in {_}*queue_low*{_}. 
> In order to work around this corner case, I made a small patch (for my own 
> use case) around "{_}resetCapacity{_}" to consider a couple new scenarios: 
>  * if the sum of absoluteCapacity/minCapacity of all active queues is zero, 
> we should normalize their guaranteed capacity evenly
> {code:java}
> 1.0f / num_of_queues{code}
>  * if the sum of pre-normalized guaranteed capacity values ({_}MB or 
> VCores{_}) of all active queues is zero, meaning we might have several queues 
> like queue_low whose capacity value got casted into 0, we should normalize 
> evenly as well like the first scenario (if they are all tiny, it really makes 
> no big difference, for example, 1% vs 1.2%).
>  * if one of the active queues has a zero pre-normalized guaranteed capacity 
> value but its absoluteCapacity/minCapacity is *not* zero, then we should 
> normalize based on the weight of their configured queue 
> absoluteCapacity/minCapacity. This is to make sure _*queue_low*_ gets a small 
> but fair normalized value when _*queue_mid*_ is also active. 
> {code:java}
> minCapacity / (sum_of_min_capacity_of_active_queues)
> {code}
>  
> This is how I currently work around this issue, it might need someone who's 
> more familiar in this component to do a systematic review of the entire 
> preemption process to fix it properly. Maybe we can always apply the 
> weight-based approach using absoluteCapacity, or rewrite the code of Resource 
> to remove the casting, or always roundUp when calculating a queue's 
> guaranteed capacity, etc.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11116) Migrate Times util from SimpleDateFormat to thread-safe DateTimeFormatter class

2022-05-02 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-6.
--
Fix Version/s: 3.4.0
   3.2.4
   3.3.4
   Resolution: Fixed

Committed to trunk, branch-3.3, and branch-3.2. Thank you [~jeagles] for your 
contribution!

> Migrate Times util from SimpleDateFormat to thread-safe DateTimeFormatter 
> class
> ---
>
> Key: YARN-6
> URL: https://issues.apache.org/jira/browse/YARN-6
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Jonathan Turner Eagles
>Assignee: Jonathan Turner Eagles
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.4
>
> Attachments: YARN-6.001.perftest.patch
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Came across a stack trace with SimpleDateFormatter in it which led me to 
> investigate current practices
>  
> {noformat}
>  6578 "IPC Server handler 29 on 8032" #797 daemon prio=5 os_prio=0 
> tid=0x7fb6527d nid=0x953b runnable [0x7fb5ba034000]
>  6579    java.lang.Thread.State: RUNNABLE
>  6580     at org.apache.hadoop.yarn.util.Times.formatISO8601(Times.java:95)
>  6581     at 
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.createAndGetApplicationReport(RMAppImpl.java:810)
>  6582     at 
> org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getApplicationReport(ClientRMService.java:396)
>  6583     at 
> org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getApplicationReport(ApplicationClientProtocolPBServiceImpl.java:224)
>  6584     at 
> org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:529)
>  6585     at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:530)
>  6586     at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:500)
>  6587     at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1069)
>  6588     at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1003)
>  6589     at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:936)
>  6590     at java.security.AccessController.doPrivileged(Native Method)
>  6591     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:2135)
>  6592     at 
> org.apache.hadoop.security.UserGroupInformation.doAsPrivileged(UserGroupInformation.java:2123)
>  6593     at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2875)
>  6594 
> {noformat}
>  
> DateTimeFormatter is thread-safe meaning no need to wrap the class in Thread 
> local as they can be reused safely across threads. In addition, the new 
> classes are slightly more performant.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10187) Removing hadoop-yarn-project/hadoop-yarn/README as it is no longer maintained.

2022-05-02 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10187.
--
Fix Version/s: 3.2.4
   3.3.4
   Resolution: Fixed

Backported to branch-3.3 and branch-3.2.

> Removing hadoop-yarn-project/hadoop-yarn/README as it is no longer maintained.
> --
>
> Key: YARN-10187
> URL: https://issues.apache.org/jira/browse/YARN-10187
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Reporter: N Sanketh Reddy
>Assignee: Ashutosh Gupta
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.4
>
>   Original Estimate: 1h
>  Time Spent: 50m
>  Remaining Estimate: 10m
>
> hadoop-yarn-project/hadoop-yarn/README is not maintained and can be removed.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-3224) Notify AM with containers (on decommissioning node) could be preempted after timeout.

2022-05-02 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-3224.
-
  Assignee: (was: Sunil G)
Resolution: Fixed

Duplicate of YARN-6483. Closing

> Notify AM with containers (on decommissioning node) could be preempted after 
> timeout.
> -
>
> Key: YARN-3224
> URL: https://issues.apache.org/jira/browse/YARN-3224
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: graceful
>Reporter: Junping Du
>Priority: Major
> Attachments: 0001-YARN-3224.patch, 0002-YARN-3224.patch
>
>
> We should leverage YARN preemption framework to notify AM that some 
> containers will be preempted after a timeout.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11101) Fix TestYarnConfigurationFields

2022-04-06 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11101.
--
Resolution: Duplicate

> Fix TestYarnConfigurationFields
> ---
>
> Key: YARN-11101
> URL: https://issues.apache.org/jira/browse/YARN-11101
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation, newbie
>Reporter: Akira Ajisaka
>Priority: Major
>
> yarn.resourcemanager.node-labels.am.default-node-label-expression is missing 
> in yarn-default.xml.
> {noformat}
> [INFO] Running org.apache.hadoop.yarn.conf.TestYarnConfigurationFields
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.533 
> s <<< FAILURE! - in org.apache.hadoop.yarn.conf.TestYarnConfigurationFields
> [ERROR] testCompareConfigurationClassAgainstXml  Time elapsed: 0.082 s  <<< 
> FAILURE!
> java.lang.AssertionError: class org.apache.hadoop.yarn.conf.YarnConfiguration 
> has 1 variables missing in yarn-default.xml Entries:   
> yarn.resourcemanager.node-labels.am.default-node-label-expression 
> expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:89)
>   at org.junit.Assert.failNotEquals(Assert.java:835)
>   at org.junit.Assert.assertEquals(Assert.java:647)
>   at 
> org.apache.hadoop.conf.TestConfigurationFieldsBase.testCompareConfigurationClassAgainstXml(TestConfigurationFieldsBase.java:493)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-11102) Fix spotbugs error in hadoop-sls module

2022-03-27 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-11102:


 Summary: Fix spotbugs error in hadoop-sls module
 Key: YARN-11102
 URL: https://issues.apache.org/jira/browse/YARN-11102
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Akira Ajisaka


Fix the following Spotbugs error:

- org.apache.hadoop.yarn.sls.AMRunner.setInputTraces(String[]) may expose 
internal representation by storing an externally mutable object into 
AMRunner.inputTraces At AMRunner.java:by storing an externally mutable object 
into AMRunner.inputTraces At AMRunner.java:[line 267]
- Write to static field org.apache.hadoop.yarn.sls.AMRunner.REMAINING_APPS from 
instance method org.apache.hadoop.yarn.sls.AMRunner.startAM() At 
AMRunner.java:from instance method 
org.apache.hadoop.yarn.sls.AMRunner.startAM() At AMRunner.java:[line 116]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-11101) Fix TestYarnConfigurationFields

2022-03-27 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-11101:


 Summary: Fix TestYarnConfigurationFields
 Key: YARN-11101
 URL: https://issues.apache.org/jira/browse/YARN-11101
 Project: Hadoop YARN
  Issue Type: Bug
  Components: documentation
Reporter: Akira Ajisaka


yarn.resourcemanager.node-labels.am.default-node-label-expression is missing in 
yarn-default.xml.
{noformat}
[INFO] Running org.apache.hadoop.yarn.conf.TestYarnConfigurationFields
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.533 s 
<<< FAILURE! - in org.apache.hadoop.yarn.conf.TestYarnConfigurationFields
[ERROR] testCompareConfigurationClassAgainstXml  Time elapsed: 0.082 s  <<< 
FAILURE!
java.lang.AssertionError: class org.apache.hadoop.yarn.conf.YarnConfiguration 
has 1 variables missing in yarn-default.xml Entries:   
yarn.resourcemanager.node-labels.am.default-node-label-expression expected:<0> 
but was:<1>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at 
org.apache.hadoop.conf.TestConfigurationFieldsBase.testCompareConfigurationClassAgainstXml(TestConfigurationFieldsBase.java:493)
{noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11081) TestYarnConfigurationFields consistently keeps failing

2022-03-08 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11081.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Merged the PR into trunk. Thank you [~vjasani] for your contribution.

> TestYarnConfigurationFields consistently keeps failing
> --
>
> Key: YARN-11081
> URL: https://issues.apache.org/jira/browse/YARN-11081
> Project: Hadoop YARN
>  Issue Type: Test
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> TestYarnConfigurationFields consistently keeps failing with error:
> {code:java}
> Error Messageclass org.apache.hadoop.yarn.conf.YarnConfiguration has 1 
> variables missing in yarn-default.xml Entries:   
> yarn.scheduler.app-placement-allocator.class expected:<0> but 
> was:<1>Stacktracejava.lang.AssertionError: class 
> org.apache.hadoop.yarn.conf.YarnConfiguration has 1 variables missing in 
> yarn-default.xml Entries:   yarn.scheduler.app-placement-allocator.class 
> expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:89)
>   at org.junit.Assert.failNotEquals(Assert.java:835)
>   at org.junit.Assert.assertEquals(Assert.java:647)
>   at 
> org.apache.hadoop.conf.TestConfigurationFieldsBase.testCompareConfigurationClassAgainstXml(TestConfigurationFieldsBase.java:493)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498) {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11068) Update transitive log4j2 dependency to 2.17.1

2022-02-20 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11068.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

Merged the PR#3963 into trunk.

> Update transitive log4j2 dependency to 2.17.1
> -
>
> Key: YARN-11068
> URL: https://issues.apache.org/jira/browse/YARN-11068
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Wei-Chiu Chuang
>Assignee: Wei-Chiu Chuang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Similar to HADOOP-18092, we have transitive log4j2 dependency coming from 
> solr-core 8 that must be excluded.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11065) Bump follow-redirects from 1.13.3 to 1.14.7 in hadoop-yarn-ui

2022-01-20 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11065.
--
Fix Version/s: 3.4.0
   Resolution: Fixed

> Bump follow-redirects from 1.13.3 to 1.14.7 in hadoop-yarn-ui
> -
>
> Key: YARN-11065
> URL: https://issues.apache.org/jira/browse/YARN-11065
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn-ui-v2
>Reporter: Akira Ajisaka
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Upgrade follow-redirects from 1.13.3 to 1.14.7 in hadoop-yarn-ui.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-11065) Bump follow-redirects from 1.13.3 to 1.14.7 in hadoop-yarn-ui

2022-01-20 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-11065:


 Summary: Bump follow-redirects from 1.13.3 to 1.14.7 in 
hadoop-yarn-ui
 Key: YARN-11065
 URL: https://issues.apache.org/jira/browse/YARN-11065
 Project: Hadoop YARN
  Issue Type: Bug
  Components: yarn-ui-v2
Reporter: Akira Ajisaka


Upgrade follow-redirects from 1.13.3 to 1.14.7 in hadoop-yarn-ui.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11055) In cgroups-operations.c some fprintf format strings don't end with "\n"

2022-01-16 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11055.
--
Fix Version/s: 3.4.0
   3.2.4
   3.3.3
   Resolution: Fixed

Committed to trunk, branch-3.3, and branch-3.2. Thank you [~jira.shegalov] for 
your contribution.

> In cgroups-operations.c some fprintf format strings don't end with "\n" 
> 
>
> Key: YARN-11055
> URL: https://issues.apache.org/jira/browse/YARN-11055
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Affects Versions: 3.0.0, 3.1.0, 3.2.0, 3.3.0, 3.3.1
>Reporter: Gera Shegalov
>Assignee: Gera Shegalov
>Priority: Minor
>  Labels: cgroups, easyfix, pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.3
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> In cgroup-operations.c some {{{}fprintf{}}}s are missing a newline char at 
> the end leading to a hard-to-parse error message output 
> example: 
> https://github.com/apache/hadoop/blame/b225287913ac366a531eacfa0266adbdf03d883e/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/modules/cgroups/cgroups-operations.c#L130
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9967) Fix NodeManager failing to start when Hdfs Auxillary Jar is set

2021-12-23 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9967.
-
Resolution: Duplicate

Fixed by YARN-11053. Closing as duplicate.

> Fix NodeManager failing to start when Hdfs Auxillary Jar is set
> ---
>
> Key: YARN-9967
> URL: https://issues.apache.org/jira/browse/YARN-9967
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: auxservices, nodemanager
>Affects Versions: 3.3.0
>Reporter: Prabhu Joseph
>Assignee: Tarun Parimi
>Priority: Major
>
> Loading an auxiliary jar from a Hdfs location on a node manager fails with 
> ClassNotFound Exception
> {code:java}
> 2019-11-08 03:59:49,256 INFO org.apache.hadoop.util.ApplicationClassLoader: 
> classpath: []
> 2019-11-08 03:59:49,256 INFO org.apache.hadoop.util.ApplicationClassLoader: 
> system classes: [java., javax.accessibility., javax.activation., 
> javax.activity., javax.annotation., javax.annotation.processing., 
> javax.crypto., javax.imageio., javax.jws., javax.lang.model., 
> -javax.management.j2ee., javax.management., javax.naming., javax.net., 
> javax.print., javax.rmi., javax.script., -javax.security.auth.message., 
> javax.security.auth., javax.security.cert., javax.security.sasl., 
> javax.sound., javax.sql., javax.swing., javax.tools., javax.transaction., 
> -javax.xml.registry., -javax.xml.rpc., javax.xml., org.w3c.dom., 
> org.xml.sax., org.apache.commons.logging., org.apache.log4j., 
> -org.apache.hadoop.hbase., org.apache.hadoop., core-default.xml, 
> hdfs-default.xml, mapred-default.xml, yarn-default.xml]
> 2019-11-08 03:59:49,257 INFO org.apache.hadoop.service.AbstractService: 
> Service 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices failed 
> in state INITED
> java.lang.ClassNotFoundException: org.apache.auxtest.AuxServiceFromHDFS
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:189)
>   at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:157)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxiliaryServiceWithCustomClassLoader.getInstance(AuxiliaryServiceWithCustomClassLoader.java:169)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.serviceInit(AuxServices.java:270)
>   at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
>   at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:108)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceInit(ContainerManagerImpl.java:321)
>   at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
>   at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:108)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:478)
>   at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:936)
>   at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:1016)
> {code}
> *Repro:*
> {code:java}
> 1. Prepare a custom auxiliary service jar and place it on hdfs
> [hdfs@yarndocker-1 yarn]$ cat TestShuffleHandler2.java 
> package org;
> import org.apache.hadoop.yarn.server.api.AuxiliaryService;
> import org.apache.hadoop.yarn.server.api.ApplicationInitializationContext;
> import org.apache.hadoop.yarn.server.api.ApplicationTerminationContext;
> import java.nio.ByteBuffer;
> public class TestShuffleHandler2 extends AuxiliaryService {
> public static final String MAPREDUCE_TEST_SHUFFLE_SERVICEID = 
> "test_shuffle2";
> public TestShuffleHandler2() {
>   super("testshuffle2");
> }
> @Override
> public void initializeApplication(ApplicationInitializationContext 
> context) {
> }
> @Override
> public void stopApplication(ApplicationTerminationContext context) {
> }
> @Override
> public synchronized ByteBuffer getMetaData() {
>   return ByteBuffer.allocate(0); 
> }
>   }
>   
> [hdfs@yarndocker-1 yarn]$ javac -d . -cp `hadoop classpath` 
> TestShuffleHandler2.java 
> [hdfs@yarndocker-1 yarn]$ jar cvf auxhdfs.jar org/
> [hdfs@yarndocker-1 mapreduce]$ hadoop fs 

[jira] [Resolved] (YARN-11053) AuxService should not use class name as default system classes

2021-12-23 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11053.
--
Fix Version/s: 3.4.0
   3.3.3
   Resolution: Fixed

Committed to trunk and branch-3.3.

> AuxService should not use class name as default system classes
> --
>
> Key: YARN-11053
> URL: https://issues.apache.org/jira/browse/YARN-11053
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: auxservices
>Affects Versions: 3.3.1
>Reporter: Cheng Pan
>Assignee: Cheng Pan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.3
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Following Apache Spark document to configure Spark Shuffle Service as YARN 
> AuxService,
> [https://spark.apache.org/docs/3.2.0/running-on-yarn.html#running-multiple-versions-of-the-spark-shuffle-service]
>  
> {code:java}
>   
> yarn.nodemanager.aux-services
> spark_shuffle
>   
>   
> yarn.nodemanager.aux-services.spark_shuffle.classpath
> /opt/apache/spark/yarn/*
>   
>   
> 
> yarn.nodemanager.aux-services.spark_shuffle.classamp;amp;lt;/name>
> org.apache.spark.network.yarn.YarnShuffleService
>{code}
>  but failed with exception
> {code:java}
> 2021-12-02 15:34:00,886 INFO util.ApplicationClassLoader: classpath: 
> [file:/opt/apache/spark/yarn/spark-3.2.0-yarn-shuffle.jar]
> 2021-12-02 15:34:00,886 INFO util.ApplicationClassLoader: system classes: 
> [org.apache.spark.network.yarn.YarnShuffleService]
> 2021-12-02 15:34:00,887 INFO service.AbstractService: Service 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices failed 
> in state INITED
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: 
> java.lang.ClassNotFoundException: 
> org.apache.spark.network.yarn.YarnShuffleService
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.initAuxService(AuxServices.java:482)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.serviceInit(AuxServices.java:761)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:109)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceInit(ContainerManagerImpl.java:327)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:109)
> at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:494)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:962)
> at 
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:1042)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.network.yarn.YarnShuffleService
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:189)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:157)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxiliaryServiceWithCustomClassLoader.getInstance(AuxiliaryServiceWithCustomClassLoader.java:165)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.createAuxServiceFromLocalClasspath(AuxServices.java:242)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.createAuxService(AuxServices.java:271)
> at 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.initAuxService(AuxServices.java:452)
> ... 10 more
> {code}
> A workaround is adding
> {code:java}
> 
> yarn.nodemanager.aux-services.spark_shuffle.system-classes
> not.existed.class/value>
>  {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11051) FileNotFoundException: /tmp/hadoop-maprchin/nm-local-dir/filecache/970

2021-12-16 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11051.
--
Resolution: Invalid

Hadoop JIRA is not for end-user question.
BTW, I suppose you should ask the question to MapR customer support because 
your environment is MapR.

> FileNotFoundException: /tmp/hadoop-maprchin/nm-local-dir/filecache/970
> --
>
> Key: YARN-11051
> URL: https://issues.apache.org/jira/browse/YARN-11051
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: JustinWang
>Priority: Blocker
> Attachments: image-2021-12-16-20-56-09-652.png
>
>
> FileNotFoundException: 
> /tmp/hadoop-maprchin/nm-local-dir/filecache/970/infa_rpm.tar/services/shared/hadoop/MapR_6.1/lib/spark-xml_2.11-0.4.0.jar
>  (No such file or directory)
>  
> situation is : when I run BDM workflow (contains 3 mapping), I monitor the 
> cache folder and found 970 created at beginning, but be deleted before the 
> mapping which need 970, that's so weired. any possible the cache folder will 
> be truncate random during these 3 mapping run?
>  
> _2021-12-16 16:01:00.887  SEVERE: The 
> Integration Service failed to execute the mapping._
> _Caused by: java.io.FileNotFoundException: 
> /tmp/hadoop-maprchin/nm-local-dir/filecache/970/infa_rpm.tar/services/shared/hadoop/MapR_6.1/lib/spark-xml_2.11-0.4.0.jar
>  (No such file or directory)_
> !image-2021-12-16-20-56-09-652.png!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9515) Non-exclusive labels do not respect user-limit-factor/max-capacity

2021-12-09 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9515.
-
Resolution: Won't Fix

> Non-exclusive labels do not respect user-limit-factor/max-capacity
> --
>
> Key: YARN-9515
> URL: https://issues.apache.org/jira/browse/YARN-9515
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacity scheduler
>Affects Versions: 2.8.5
>Reporter: Brandon Scheller
>Priority: Major
>
> When using a cluster with non-exclusive labels. Queues will only respect 
> user-limit-factor for allocations to the default partition. Non-exclusive 
> label allocations will not consider these factors allowing the labeled 
> partitions capacity to be completely used up.
> To reproduce this, consider this example.
> Cluster contains 1 non-exclusive nodelabel: *APPMASTER*
> "test" queue has access to all labels: *
> "test" queue has capacity/max-capacity: 20
> "test" queue has user-limit-factor: 0.1
> Job is submitted to "test" queue with label: *APPMASTER* only on its 
> appMaster container request, and no-label for all other containers.
> user-limit-factor and capacity will not be respected for the job on 
> allocations to the *APPMASTER* partition causing the single job to attempt to 
> use the entire capacity of the *APPMASTER* partition through non-exclusive 
> allocations.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9063) ATS 1.5 fails to start if RollingLevelDb files are corrupt or missing

2021-12-06 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9063.
-
Fix Version/s: 3.4.0
   2.10.2
   3.2.4
   3.3.3
   Resolution: Fixed

Committed to trunk, branch-3.3, branch-3.2, and branch-2.10. Thank you 
[~tarunparimi] for your report and thanks [~groot] for your contribution.

> ATS 1.5 fails to start if RollingLevelDb files are corrupt or missing
> -
>
> Key: YARN-9063
> URL: https://issues.apache.org/jira/browse/YARN-9063
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: timelineserver, timelineservice
>Affects Versions: 2.8.0
>Reporter: Tarun Parimi
>Assignee: Ashutosh Gupta
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 2.10.2, 3.2.4, 3.3.3
>
>  Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> ATS v1.5 fails to start up if there are some missing files in 
> RollingLevelDBTimelineStore. YARN-6054 fixes this issue only for the 
> LevelDBTimelineStore. Since RollingLevelDBTimelineStore opens multiple level 
> db and rolls them, we need a separate fix for this. The error is shown below
> {code}
> 18/11/13 07:00:56 FATAL applicationhistoryservice.ApplicationHistoryServer: 
> Error starting ApplicationHistoryServer 
> org.apache.hadoop.service.ServiceStateException: 
> org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 1 
> missing files; e.g.: 
> /tmp/ats_folder/yarn/timeline/leveldb-timeline-store/owner-ldb/05.sst 
> at 
> org.apache.hadoop.service.ServiceStateException.convert(ServiceStateException.java:59)
>  
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:172) 
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
>  
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
>  
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) 
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
>  
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
>  
> Caused by: org.fusesource.leveldbjni.internal.NativeDB$DBException: 
> Corruption: 1 missing files; e.g.: 
> /tmp/ats-folder/yarn/timeline/leveldb-timeline-store/owner-ldb/05.sst 
> at org.fusesource.leveldbjni.internal.NativeDB.checkStatus(NativeDB.java:200) 
> at org.fusesource.leveldbjni.internal.NativeDB.open(NativeDB.java:218) 
> at org.fusesource.leveldbjni.JniDBFactory.open(JniDBFactory.java:168) 
> at 
> org.apache.hadoop.yarn.server.timeline.RollingLevelDBTimelineStore.serviceInit(RollingLevelDBTimelineStore.java:321)
>  
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-11007) Correct words in YARN documents

2021-11-25 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-11007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-11007.
--
Fix Version/s: 3.4.0
   3.2.4
   3.3.3
   Resolution: Fixed

Committed to trunk, branch-3.3, and branch-3.2. Thank you [~philipse] for 
cleaning up the documents!

> Correct words in YARN documents
> ---
>
> Key: YARN-11007
> URL: https://issues.apache.org/jira/browse/YARN-11007
> Project: Hadoop YARN
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.3.1
>Reporter: guo
>Assignee: guo
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.3
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10991) Fix to ignore the grouping "[]" for resourcesStr in parseResourcesString method

2021-11-24 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10991.
--
Fix Version/s: 3.4.0
   3.2.4
   3.3.3
   (was: 3.3.1)
   Resolution: Fixed

Committed to trunk, branch-3.3, and branch-3.2. Thanks [~groot] for your 
contribution. Welcome!

> Fix to ignore the grouping "[]" for resourcesStr in parseResourcesString 
> method
> ---
>
> Key: YARN-10991
> URL: https://issues.apache.org/jira/browse/YARN-10991
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: distributed-shell
>Affects Versions: 3.3.1
>Reporter: Ashutosh Gupta
>Assignee: Ashutosh Gupta
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.3
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Currently if the resourcesStr argument in parseResourcesString method 
> contains "]" at the end, its not being ignored. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10976) Fix resource leak due to Files.walk

2021-10-18 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10976.
--
Fix Version/s: 3.3.2
   3.4.0
   Resolution: Fixed

Committed to trunk and branch-3.3. Thank you [~xiaoheipangzi] for your 
contribution!

> Fix resource leak due to Files.walk
> ---
>
> Key: YARN-10976
> URL: https://issues.apache.org/jira/browse/YARN-10976
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: lujie
>Assignee: lujie
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Stream creates by File.walk should be closed, like jdk said:
>  *  The returned stream encapsulates one or more \{@link DirectoryStream}s.
>  * If timely disposal of file system resources is required, the
>  * {@code try}-with-resources construct should be used to ensure that the
>  * stream's \{@link Stream#close close} method is invoked after the stream
>  * operations are completed. Operating on a closed stream will result in an
>  * {@link java.lang.IllegalStateException}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10970) Prometheussink: Standby RM should expose prom endpoint

2021-09-29 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10970.
--
Fix Version/s: 3.3.2
   3.4.0
   Resolution: Fixed

Committed to trunk and branch-3.3.

> Prometheussink: Standby RM should expose prom endpoint
> --
>
> Key: YARN-10970
> URL: https://issues.apache.org/jira/browse/YARN-10970
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: resourcemanager
>Affects Versions: 3.4.0
>Reporter: Max  Xie
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> HADOOP-16398 exports Hadoop metrics to Prometheus. 
> However, standby RM redirects prom metrics to the Active.  We need to 
> separate out prom metrics displayed so the Standby RM can also be export 
> metrics to prometheus.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-8992) Fair scheduler can delete a dynamic queue while an application attempt is being added to the queue

2021-08-03 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-8992.
-
Fix Version/s: 3.2.3
   Resolution: Fixed

Backported to branch-3.2.

> Fair scheduler can delete a dynamic queue while an application attempt is 
> being added to the queue
> --
>
> Key: YARN-8992
> URL: https://issues.apache.org/jira/browse/YARN-8992
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: fairscheduler
>Affects Versions: 3.1.1
>Reporter: Haibo Chen
>Assignee: Wilfred Spiegelenburg
>Priority: Major
>  Labels: pull-request-available, release-blocker
> Fix For: 3.2.3, 3.3.0
>
> Attachments: YARN-8992.001.patch, YARN-8992.002.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> As discovered in YARN-8990, QueueManager can see a leaf queue being empty 
> while FSLeafQueue.addApp() is called in the middle of  
> {code:java}
> return queue.getNumRunnableApps() == 0 &&
>   leafQueue.getNumNonRunnableApps() == 0 &&
>   leafQueue.getNumAssignedApps() == 0;{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-8990) Fix fair scheduler race condition in app submit and queue cleanup

2021-08-02 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-8990.
-
Fix Version/s: 3.2.3
   Resolution: Fixed

Backported to branch-3.2.

> Fix fair scheduler race condition in app submit and queue cleanup
> -
>
> Key: YARN-8990
> URL: https://issues.apache.org/jira/browse/YARN-8990
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: fairscheduler
>Affects Versions: 3.2.0
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Blocker
>  Labels: pull-request-available, release-blocker
> Fix For: 3.2.3, 3.3.0, 3.2.0
>
> Attachments: YARN-8990.001.patch, YARN-8990.002.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> With the introduction of the dynamic queue deletion in YARN-8191 a race 
> condition was introduced that can cause a queue to be removed while an 
> application submit is in progress.
> The issue occurs in {{FairScheduler.addApplication()}} when an application is 
> submitted to a dynamic queue which is empty or the queue does not exist yet. 
> If during the processing of the application submit the 
> {{AllocationFileLoaderService}} kicks of for an update the queue clean up 
> will be run first. The application submit first creates the queue and get a 
> reference back to the queue. 
> Other checks are performed and as the last action before getting ready to 
> generate an AppAttempt the queue is updated to show the submitted application 
> ID..
> The time between the queue creation and the queue update to show the submit 
> is long enough for the queue to be removed. The application however is lost 
> and will never get any resources assigned.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10847) Build fails on MacOS 10.15

2021-07-06 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10847.
--
Resolution: Invalid

Please do not change the package name when building Apache Hadoop.

> Build fails on MacOS 10.15
> --
>
> Key: YARN-10847
> URL: https://issues.apache.org/jira/browse/YARN-10847
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Abhinav Kumar
>Priority: Major
>
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (depcheck) @ 
> hadoop-yarn-server-timelineservice-hbase-common ---
> [WARNING] 
> Dependency convergence error for commons-lang:commons-lang:2.6 paths to 
> dependency are:
> +-org.uscbrft.apache.hadoop:hadoop-yarn-server-timelineservice-hbase-common:3.2.0
>  +-org.apache.hbase:hbase-common:1.2.6
>  +-commons-lang:commons-lang:2.6
> and
> +-org.uscbrft.apache.hadoop:hadoop-yarn-server-timelineservice-hbase-common:3.2.0
>  +-org.apache.hbase:hbase-common:1.2.6
>  +-org.apache.hadoop:hadoop-common:2.5.1
>  +-commons-lang:commons-lang:2.6
> and
> +-org.uscbrft.apache.hadoop:hadoop-yarn-server-timelineservice-hbase-common:3.2.0
>  +-org.apache.hbase:hbase-common:1.2.6
>  +-org.apache.hadoop:hadoop-common:2.5.1
>  +-commons-configuration:commons-configuration:1.6
>  +-commons-lang:commons-lang:2.4
> and
> +-org.uscbrft.apache.hadoop:hadoop-yarn-server-timelineservice-hbase-common:3.2.0
>  +-org.apache.hbase:hbase-common:1.2.6
>  +-org.apache.hadoop:hadoop-mapreduce-client-core:2.5.1
>  +-org.apache.hadoop:hadoop-yarn-common:2.5.1
>  +-org.apache.hadoop:hadoop-yarn-api:2.5.1
>  +-commons-lang:commons-lang:2.6
> and
> +-org.uscbrft.apache.hadoop:hadoop-yarn-server-timelineservice-hbase-common:3.2.0
>  +-org.apache.hbase:hbase-common:1.2.6
>  +-org.apache.hadoop:hadoop-mapreduce-client-core:2.5.1
>  +-org.apache.hadoop:hadoop-yarn-common:2.5.1
>  +-commons-lang:commons-lang:2.6
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence 
> failed with message:
> Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with 
> message:
> Failed while enforcing releasability. See above detailed error message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10826) [UI2] Upgrade Node.js to at least 12.x

2021-06-21 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10826:


 Summary: [UI2] Upgrade Node.js to at least 12.x
 Key: YARN-10826
 URL: https://issues.apache.org/jira/browse/YARN-10826
 Project: Hadoop YARN
  Issue Type: Bug
  Components: yarn-ui-v2
Reporter: Akira Ajisaka


Node.js 10.x is EoL. We have to upgrade to at least 12.x.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10817) Avoid java.lang.NullPointerException when use yarn shell

2021-06-10 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10817.
--
Fix Version/s: (was: 3.2.1)
   Resolution: Duplicate

> Avoid java.lang.NullPointerException when use yarn shell
> 
>
> Key: YARN-10817
> URL: https://issues.apache.org/jira/browse/YARN-10817
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: client
>Affects Versions: 3.2.1
>Reporter: yikf
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When we use yarn queue-status, we encounter a null pointer exception, As 
> follow:
> Like this, and:
>  yarn cluster
>  yarn queue
>  yarn node
> {code:java}
> Missing argument for optionsMissing argument for options
> usage: queue 
>   -help                  Displays help for all commands. 
>   -status    List queue information about given queue.
> Exception in thread "main" java.lang.NullPointerException 
> at org.apache.hadoop.yarn.client.cli.YarnCLI.stop(YarnCLI.java:75) 
> at org.apache.hadoop.yarn.client.cli.QueueCLI.main(QueueCLI.java:51)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10803) [JDK 11] TestRMFailoverProxyProvider and TestNoHaRMFailoverProxyProvider fails by ClassCastException

2021-06-09 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10803.
--
Fix Version/s: 3.3.2
   3.4.0
   Resolution: Fixed

Committed to trunk and branch-3.3.

> [JDK 11] TestRMFailoverProxyProvider and TestNoHaRMFailoverProxyProvider 
> fails by ClassCastException
> 
>
> Key: YARN-10803
> URL: https://issues.apache.org/jira/browse/YARN-10803
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: test
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/178/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
> {quote}
> [ERROR] 
> testFailoverChange(org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider) 
> Time elapsed: 0.024 s <<< ERROR! java.lang.ClassCastException: class 
> org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider$TestProxy cannot be 
> cast to class org.apache.hadoop.yarn.client.RMProxy 
> (org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider$TestProxy and 
> org.apache.hadoop.yarn.client.RMProxy are in unnamed module of loader 'app') 
> at 
> org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider.testFailoverChange(TestRMFailoverProxyProvider.java:141)
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10808) TestHBaseTimelineStorageUtils fails by NoClassDefFoundError

2021-06-09 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10808.
--
Resolution: Duplicate

> TestHBaseTimelineStorageUtils fails by NoClassDefFoundError
> ---
>
> Key: YARN-10808
> URL: https://issues.apache.org/jira/browse/YARN-10808
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: test
>Reporter: Akira Ajisaka
>Priority: Major
>  Labels: newbie
>
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/529/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-client.txt
> {quote}
> [ERROR] 
> testWithHbaseConfAtHdfsFileSystem(org.apache.hadoop.yarn.server.timelineservice.storage.common.TestHBaseTimelineStorageUtils)
>   Time elapsed: 5.89 s  <<< ERROR!
> java.lang.NoClassDefFoundError: org/mockito/stubbing/Answer
>   at 
> org.apache.hadoop.hdfs.MiniDFSCluster.isNameNodeUp(MiniDFSCluster.java:2618)
>   at 
> org.apache.hadoop.hdfs.MiniDFSCluster.isClusterUp(MiniDFSCluster.java:2632)
>   at 
> org.apache.hadoop.hdfs.MiniDFSCluster.waitClusterUp(MiniDFSCluster.java:1498)
>   at 
> org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:977)
>   at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:576)
>   at 
> org.apache.hadoop.hdfs.MiniDFSCluster$Builder.build(MiniDFSCluster.java:518)
>   at 
> org.apache.hadoop.yarn.server.timelineservice.storage.common.TestHBaseTimelineStorageUtils.testWithHbaseConfAtHdfsFileSystem(TestHBaseTimelineStorageUtils.java:86)
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10808) TestHBaseTimelineStorageUtils fails by NoClassDefFoundError

2021-06-06 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10808:


 Summary: TestHBaseTimelineStorageUtils fails by 
NoClassDefFoundError
 Key: YARN-10808
 URL: https://issues.apache.org/jira/browse/YARN-10808
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/529/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-client.txt
{quote}
[ERROR] 
testWithHbaseConfAtHdfsFileSystem(org.apache.hadoop.yarn.server.timelineservice.storage.common.TestHBaseTimelineStorageUtils)
  Time elapsed: 5.89 s  <<< ERROR!
java.lang.NoClassDefFoundError: org/mockito/stubbing/Answer
at 
org.apache.hadoop.hdfs.MiniDFSCluster.isNameNodeUp(MiniDFSCluster.java:2618)
at 
org.apache.hadoop.hdfs.MiniDFSCluster.isClusterUp(MiniDFSCluster.java:2632)
at 
org.apache.hadoop.hdfs.MiniDFSCluster.waitClusterUp(MiniDFSCluster.java:1498)
at 
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:977)
at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:576)
at 
org.apache.hadoop.hdfs.MiniDFSCluster$Builder.build(MiniDFSCluster.java:518)
at 
org.apache.hadoop.yarn.server.timelineservice.storage.common.TestHBaseTimelineStorageUtils.testWithHbaseConfAtHdfsFileSystem(TestHBaseTimelineStorageUtils.java:86)
{quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10803) [JDK 11] TestRMFailoverProxyProvider and TestNoHaRMFailoverProxyProvider fails by ClassCastException

2021-06-03 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10803:


 Summary: [JDK 11] TestRMFailoverProxyProvider and 
TestNoHaRMFailoverProxyProvider fails by ClassCastException
 Key: YARN-10803
 URL: https://issues.apache.org/jira/browse/YARN-10803
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/178/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
{quote}
[ERROR] 
testFailoverChange(org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider) 
Time elapsed: 0.024 s <<< ERROR! java.lang.ClassCastException: class 
org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider$TestProxy cannot be 
cast to class org.apache.hadoop.yarn.client.RMProxy 
(org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider$TestProxy and 
org.apache.hadoop.yarn.client.RMProxy are in unnamed module of loader 'app') at 
org.apache.hadoop.yarn.client.TestRMFailoverProxyProvider.testFailoverChange(TestRMFailoverProxyProvider.java:141)
{quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10788) TestCsiClient fails

2021-05-26 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10788:


 Summary: TestCsiClient fails
 Key: YARN-10788
 URL: https://issues.apache.org/jira/browse/YARN-10788
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


TestCsiClient fails to bind to unix domain socket.
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/518/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-csi.txt
{noformat}
[INFO] Running org.apache.hadoop.yarn.csi.client.TestCsiClient
[ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.67 s 
<<< FAILURE! - in org.apache.hadoop.yarn.csi.client.TestCsiClient
[ERROR] testIdentityService(org.apache.hadoop.yarn.csi.client.TestCsiClient)  
Time elapsed: 0.457 s  <<< ERROR!
java.io.IOException: Failed to bind
at io.grpc.netty.NettyServer.start(NettyServer.java:257)
at io.grpc.internal.ServerImpl.start(ServerImpl.java:184)
at io.grpc.internal.ServerImpl.start(ServerImpl.java:90)
at 
org.apache.hadoop.yarn.csi.client.FakeCsiDriver.start(FakeCsiDriver.java:56)
at 
org.apache.hadoop.yarn.csi.client.TestCsiClient.testIdentityService(TestCsiClient.java:72)
 {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10770) container-executor permission is wrong in SecureContainer.md

2021-05-17 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10770:


 Summary: container-executor permission is wrong in 
SecureContainer.md
 Key: YARN-10770
 URL: https://issues.apache.org/jira/browse/YARN-10770
 Project: Hadoop YARN
  Issue Type: Bug
  Components: documentation
Reporter: Akira Ajisaka


{noformat}
  The `container-executor` program must be owned by `root` and have the 
permission set `---sr-s---`.
{noformat}
It should be 6050 {noformat}---Sr-s---{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10757) jsonschema2pojo-maven-plugin version is not defined

2021-04-27 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10757:


 Summary: jsonschema2pojo-maven-plugin version is not defined
 Key: YARN-10757
 URL: https://issues.apache.org/jira/browse/YARN-10757
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build
Reporter: Akira Ajisaka


The below maven plugin version is not defined.
{noformat}
$ mvn install  
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.hadoop:hadoop-yarn-server-resourcemanager:jar:3.4.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.jsonschema2pojo:jsonschema2pojo-maven-plugin is missing. @ line 448, column 
15
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10752) Shaded guava not found when compiling with profile hbase2.0

2021-04-26 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10752.
--
Fix Version/s: 3.3.1
 Hadoop Flags: Reviewed
   Resolution: Fixed

Merged the PR.

> Shaded guava not found when compiling with profile hbase2.0
> ---
>
> Key: YARN-10752
> URL: https://issues.apache.org/jira/browse/YARN-10752
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: timelineserver
>Affects Versions: 3.3.1
>Reporter: Wei-Chiu Chuang
>Assignee: Wei-Chiu Chuang
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 3.3.1
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When preparing for Hadoop 3.3.1 release, I found the build breaks when 
> compiling with profile hbase2.0 because the shaded guava classes in the 
> hadoop-thirdparty jars were not found.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10694) Fix spotbugs warning in CapacitySchedulerConfiguration.java

2021-03-15 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10694.
--
Resolution: Duplicate

Closing as dup. Thank you [~zhuqi] for the information.

> Fix spotbugs warning in CapacitySchedulerConfiguration.java
> ---
>
> Key: YARN-10694
> URL: https://issues.apache.org/jira/browse/YARN-10694
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacity scheduler
>Reporter: Akira Ajisaka
>Priority: Major
>  Labels: newbie
>
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/447/artifact/out/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-warnings.html
>   
> Bug type DM_BOXED_PRIMITIVE_FOR_PARSING (click for details)
> In class 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration
> In method 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.extractFloatValueFromWeightConfig(String)
> Called method Float.floatValue()
> Should call Float.parseFloat(String) instead
> At CapacitySchedulerConfiguration.java:[line 778]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10694) Fix spotbugs warning in CapacitySchedulerConfiguration.java

2021-03-15 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10694:


 Summary: Fix spotbugs warning in 
CapacitySchedulerConfiguration.java
 Key: YARN-10694
 URL: https://issues.apache.org/jira/browse/YARN-10694
 Project: Hadoop YARN
  Issue Type: Bug
  Components: capacity scheduler
Reporter: Akira Ajisaka


https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/447/artifact/out/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-warnings.html

Bug type DM_BOXED_PRIMITIVE_FOR_PARSING (click for details)
In class 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration
In method 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.extractFloatValueFromWeightConfig(String)
Called method Float.floatValue()
Should call Float.parseFloat(String) instead
At CapacitySchedulerConfiguration.java:[line 778]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10662) [JDK 11] TestTimelineReaderWebServicesHBaseStorage fails

2021-03-01 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10662:


 Summary: [JDK 11] TestTimelineReaderWebServicesHBaseStorage fails
 Key: YARN-10662
 URL: https://issues.apache.org/jira/browse/YARN-10662
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


[https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/131/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase-tests.txt]
{noformat}
[INFO] Running 
org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.515 s 
<<< FAILURE! - in 
org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
[ERROR] 
org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
  Time elapsed: 1.514 s  <<< ERROR!
java.lang.ExceptionInInitializerError
at 
org.apache.hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage.setupBeforeClass(TestTimelineReaderWebServicesHBaseStorage.java:84)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Caused by: java.lang.RuntimeException: java.io.IOException: Can not attach to 
current VM
at 
mockit.internal.startup.AgentLoader.attachToRunningVM(AgentLoader.java:150)
at mockit.internal.startup.AgentLoader.loadAgent(AgentLoader.java:60)
at 
mockit.internal.startup.Startup.verifyInitialization(Startup.java:169)
at mockit.MockUp.(MockUp.java:94)
... 19 more
Caused by: java.io.IOException: Can not attach to current VM
at 
jdk.attach/sun.tools.attach.HotSpotVirtualMachine.(HotSpotVirtualMachine.java:75)
at 
jdk.attach/sun.tools.attach.VirtualMachineImpl.(VirtualMachineImpl.java:56)
at 
jdk.attach/sun.tools.attach.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:58)
at 
jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:207)
at 
mockit.internal.startup.AgentLoader.attachToRunningVM(AgentLoader.java:144)
... 22 more


[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Errors: 
[ERROR]   TestTimelineReaderWebServicesHBaseStorage.setupBeforeClass:84 
ExceptionInInitializer
[INFO] 
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10656) Parsing error in CapacityScheduler.md

2021-02-26 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10656:


 Summary: Parsing error in CapacityScheduler.md
 Key: YARN-10656
 URL: https://issues.apache.org/jira/browse/YARN-10656
 Project: Hadoop YARN
  Issue Type: Bug
  Components: documentation
Reporter: Akira Ajisaka


mvn site failed: 
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/429/artifact/out/patch-mvnsite-root.txt
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project 
hadoop-yarn-site: Error parsing 
'/home/jenkins/jenkins-home/workspace/hadoop-qbt-trunk-java8-linux-x86_64/sourcedir/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md':
 line [-1] Error parsing the model: Unable to execute macro in the document: 
toc -> [Help 1]
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10560) Upgrade node.js to 10.23.1 in Web UI v2

2021-01-05 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10560.
--
Fix Version/s: 3.3.1
   3.4.0
   Resolution: Fixed

Committed to trunk and branch-3.3.

> Upgrade node.js to 10.23.1 in Web UI v2
> ---
>
> Key: YARN-10560
> URL: https://issues.apache.org/jira/browse/YARN-10560
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: webapp, yarn-ui-v2
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.1
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Node 10.x before 10.23.1 are vulnerable: 
> https://groups.google.com/g/nodejs-sec/c/kyzmwvQdUfs/m/7mjPCzY2BAAJ?pli=1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10560) Upgrade node.js to 10.23.1

2021-01-05 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10560:


 Summary: Upgrade node.js to 10.23.1
 Key: YARN-10560
 URL: https://issues.apache.org/jira/browse/YARN-10560
 Project: Hadoop YARN
  Issue Type: Bug
  Components: webapp
Reporter: Akira Ajisaka


Node 10.x before 10.23.1 are vulnerable: 
https://groups.google.com/g/nodejs-sec/c/kyzmwvQdUfs/m/7mjPCzY2BAAJ?pli=1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10491) Fix deprecation warnings in SLSWebApp.java

2020-12-08 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10491.
--
Fix Version/s: 3.2.3
   3.1.5
   3.3.1
   3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Committed to trunk, branch-3.3, branch-3.2, and branch-3.1. Thank you [~akumar] 
for your contribution.

> Fix deprecation warnings in SLSWebApp.java
> --
>
> Key: YARN-10491
> URL: https://issues.apache.org/jira/browse/YARN-10491
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: build
>Reporter: Akira Ajisaka
>Assignee: Ankit Kumar
>Priority: Minor
>  Labels: newbie, pull-request-available
> Fix For: 3.4.0, 3.3.1, 3.1.5, 3.2.3
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> {code}
>   simulateInfoTemplate = IOUtils.toString(
>   cl.getResourceAsStream("html/simulate.info.html.template"));
>   simulateTemplate = IOUtils.toString(
>   cl.getResourceAsStream("html/simulate.html.template"));
>   trackTemplate = IOUtils.toString(
>   cl.getResourceAsStream("html/track.html.template"));
> {code}
> {{IOUtils.toString(InputStream, Charset)}} should be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10511) Update yarn.nodemanager.env-whitelist value in docs

2020-12-03 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10511.
--
Fix Version/s: 3.2.3
   3.1.5
   3.3.1
   3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Merged the PR into trunk, branch-3.3, branch-3.2, and branch-3.1. Thank you 
[~ascarpino] for your contribution!

> Update yarn.nodemanager.env-whitelist value in docs
> ---
>
> Key: YARN-10511
> URL: https://issues.apache.org/jira/browse/YARN-10511
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Reporter: Andrea Scarpino
>Assignee: Andrea Scarpino
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.1, 3.1.5, 3.2.3
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The [Hadoop Cluster 
> Setup|https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/ClusterSetup.html]
>  documentation page references an old value for the 
> {{yarn.nodemanager.env-whitelist}} variable because the value referenced in 
> that page has been changed since YARN-6694.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10498) Fix Yarn CapacityScheduler Markdown document

2020-11-29 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10498.
--
Fix Version/s: 3.2.3
   2.10.2
   3.1.5
   3.3.1
   3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Merged the PR into all the active branches.

> Fix Yarn CapacityScheduler Markdown document
> 
>
> Key: YARN-10498
> URL: https://issues.apache.org/jira/browse/YARN-10498
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Reporter: zhaoshengjie
>Assignee: zhaoshengjie
>Priority: Trivial
>  Labels: newbie
> Fix For: 3.4.0, 3.3.1, 3.1.5, 2.10.2, 3.2.3
>
> Attachments: 20201123095314.png
>
>
> The markdown document (CapacityScheduler.md) has spelling mistake.failuers 
> should be failures.
> !20201123095314.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10488) Several typos in package: org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair

2020-11-24 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10488.
--
Fix Version/s: 3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Committed to trunk.

> Several typos in package: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair
> --
>
> Key: YARN-10488
> URL: https://issues.apache.org/jira/browse/YARN-10488
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Szilard Nemeth
>Assignee: Ankit Kumar
>Priority: Minor
>  Labels: newbie, newbie++
> Fix For: 3.4.0
>
>
> 1. Typo in field name: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.VisitedResourceRequestTracker.TrackerPerPriorityResource#racksVisted
> 2. Typo in method: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.QueueManager#setChildResourceLimits
> There's a comment: "... max reource ...", typo in the word 'resource'.
> 3. Typo in javadoc of method: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt#reserve
> "bookeeping" -> "bookkeeping"
> 4. There's a local variable in this method: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt#updateAMDiagnosticMsg,
>  
> called diagnosticMessageBldr. It's an abbreviation, but could be changed to 
> something more meaningful.
> 5. Typo in javadoc of method: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.MaxRunningAppsEnforcer#updateRunnabilityOnReload
> "reinitilized" --> "reinitialized"
> 6. And last but not least, a funny typo in the method name of: 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.policies.DominantResourceFairnessPolicy.DominantResourceFairnessComparator#compareAttribrutes



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10500) TestDelegationTokenRenewer fails intermittently

2020-11-24 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10500:


 Summary: TestDelegationTokenRenewer fails intermittently
 Key: YARN-10500
 URL: https://issues.apache.org/jira/browse/YARN-10500
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


TestDelegationTokenRenewer sometimes timeouts.
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/334/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
{noformat}
[INFO] Running 
org.apache.hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer
[ERROR] Tests run: 23, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 83.675 
s <<< FAILURE! - in 
org.apache.hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer
[ERROR] 
testTokenThreadTimeout(org.apache.hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer)
  Time elapsed: 30.065 s  <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3 
milliseconds
at java.lang.Thread.sleep(Native Method)
at 
org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:394)
at 
org.apache.hadoop.yarn.server.resourcemanager.security.TestDelegationTokenRenewer.testTokenThreadTimeout(TestDelegationTokenRenewer.java:1769)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10499) TestRouterWebServicesREST fails

2020-11-24 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10499:


 Summary: TestRouterWebServicesREST fails
 Key: YARN-10499
 URL: https://issues.apache.org/jira/browse/YARN-10499
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


[https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2488/1/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn.txt]
{noformat}
[ERROR] Failures: 
[ERROR]   TestRouterWebServicesREST.testAppAttemptXML:720->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppPriorityXML:796->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppQueueXML:846->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppStateXML:744->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppTimeoutXML:920->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppTimeoutsXML:896->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testAppXML:696->performGetCalls:274 
expected:<200> but was:<204>
[ERROR]   TestRouterWebServicesREST.testUpdateAppPriorityXML:832 expected:<200> 
but was:<500>
[ERROR]   TestRouterWebServicesREST.testUpdateAppQueueXML:882 expected:<200> 
but was:<500>
[ERROR]   TestRouterWebServicesREST.testUpdateAppStateXML:782 expected:<202> 
but was:<500>
[ERROR] Errors: 
[ERROR]   
TestRouterWebServicesREST.testGetAppAttemptXML:1292->getAppAttempt:1464 » 
ClientHandler
[ERROR]   
TestRouterWebServicesREST.testGetAppsMultiThread:1337->testGetContainersXML:1317->getAppAttempt:1464
 » ClientHandler
[ERROR]   
TestRouterWebServicesREST.testGetContainersXML:1317->getAppAttempt:1464 » 
ClientHandler {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10491) Fix deprecation warnings in SLSWebApp.java

2020-11-16 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10491:


 Summary: Fix deprecation warnings in SLSWebApp.java
 Key: YARN-10491
 URL: https://issues.apache.org/jira/browse/YARN-10491
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build
Reporter: Akira Ajisaka


{code}
  simulateInfoTemplate = IOUtils.toString(
  cl.getResourceAsStream("html/simulate.info.html.template"));
  simulateTemplate = IOUtils.toString(
  cl.getResourceAsStream("html/simulate.html.template"));
  trackTemplate = IOUtils.toString(
  cl.getResourceAsStream("html/track.html.template"));
{code}
{{IOUtils.toString(InputStream, Charset)}} should be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10474) [JDK 12] TestAsyncDispatcher fails

2020-10-27 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10474:


 Summary: [JDK 12] TestAsyncDispatcher fails
 Key: YARN-10474
 URL: https://issues.apache.org/jira/browse/YARN-10474
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


Similar to HDFS-15580. Updating a final variable via reflection is not allowed 
in Java 12+.
{noformat}
[INFO] Running org.apache.hadoop.yarn.event.TestAsyncDispatcher
[ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.953 s 
<<< FAILURE! - in org.apache.hadoop.yarn.event.TestAsyncDispatcher
[ERROR] 
testPrintDispatcherEventDetails(org.apache.hadoop.yarn.event.TestAsyncDispatcher)
  Time elapsed: 0.114 s  <<< ERROR!
java.lang.NoSuchFieldException: modifiers
at java.base/java.lang.Class.getDeclaredField(Class.java:2569)
at 
org.apache.hadoop.yarn.event.TestAsyncDispatcher.testPrintDispatcherEventDetails(TestAsyncDispatcher.java:152)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:832)
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10419) Javadoc error in hadoop-yarn-server-common module

2020-09-01 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10419:


 Summary: Javadoc error in hadoop-yarn-server-common module
 Key: YARN-10419
 URL: https://issues.apache.org/jira/browse/YARN-10419
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build, documentation
Reporter: Akira Ajisaka


{noformat}
$ mvn clean process-sources javadoc:javadoc-no-fork -pl 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
(snip)
[ERROR] 
/Users/aajisaka/git/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/webapp/dao/RemoteLogPathEntry.java:23:
 error: unknown tag: ROOT_PATH
[ERROR]  *   /%USER/
[ERROR]  ^
[ERROR] 
/Users/aajisaka/git/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/webapp/dao/RemoteLogPathEntry.java:23:
 error: unknown tag: SUFFIX
[ERROR]  *   /%USER/
{noformat}
Full log: https://gist.github.com/aajisaka/46fde3cbd9211fc09ee4040b85251e9c



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10383) YarnCommands.md is inconsistent with the source code

2020-08-03 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10383.
--
Fix Version/s: 3.4.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

> YarnCommands.md is inconsistent with the source code
> 
>
> Key: YARN-10383
> URL: https://issues.apache.org/jira/browse/YARN-10383
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Reporter: zhaoshengjie
>Priority: Minor
> Fix For: 3.4.0
>
> Attachments: 01.png, 02.png
>
>
> The markdown document (YarnCommands.md) is inconsistent with the source code
> !01.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10350) TestUserGroupMappingPlacementRule fails

2020-07-13 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10350:


 Summary: TestUserGroupMappingPlacementRule fails
 Key: YARN-10350
 URL: https://issues.apache.org/jira/browse/YARN-10350
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Akira Ajisaka


TestUserGroupMappingPlacementRule fails on trunk:
{noformat}
[INFO] Running 
org.apache.hadoop.yarn.server.resourcemanager.placement.TestUserGroupMappingPlacementRule
[ERROR] Tests run: 31, Failures: 1, Errors: 2, Skipped: 0, Time elapsed: 2.662 
s <<< FAILURE! - in 
org.apache.hadoop.yarn.server.resourcemanager.placement.TestUserGroupMappingPlacementRule
[ERROR] 
testResolvedQueueIsNotManaged(org.apache.hadoop.yarn.server.resourcemanager.placement.TestUserGroupMappingPlacementRule)
  Time elapsed: 0.03 s  <<< ERROR!
java.lang.Exception: Unexpected exception, 
expected but 
was
at 
org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Caused by: java.lang.AssertionError: Queue expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at 
org.apache.hadoop.yarn.server.resourcemanager.placement.TestUserGroupMappingPlacementRule.verifyQueueMapping(TestUserGroupMappingPlacementRule.java:236)
at 
org.apache.hadoop.yarn.server.resourcemanager.placement.TestUserGroupMappingPlacementRule.testResolvedQueueIsNotManaged(TestUserGroupMappingPlacementRule.java:516)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:19)
... 18 more
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10344) Sync netty-* versions in hadoop-yarn-csi

2020-07-07 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10344:


 Summary: Sync netty-* versions in hadoop-yarn-csi
 Key: YARN-10344
 URL: https://issues.apache.org/jira/browse/YARN-10344
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build
Reporter: Akira Ajisaka


netty-all is now 4.1.50.Final but the other netty libraries are 4.1.42.Final:
{noformat}
[INFO] --- maven-dependency-plugin:3.0.2:tree (default-cli) @ hadoop-yarn-csi 
---
[INFO] org.apache.hadoop:hadoop-yarn-csi:jar:3.3.0
[INFO] +- com.google.guava:guava:jar:20.0:compile
[INFO] +- com.google.protobuf:protobuf-java:jar:3.6.1:compile
[INFO] +- io.netty:netty-all:jar:4.1.50.Final:compile
[INFO] +- io.grpc:grpc-core:jar:1.26.0:compile
[INFO] |  +- io.grpc:grpc-api:jar:1.26.0:compile (version selected from 
constraint [1.26.0,1.26.0])
[INFO] |  |  +- io.grpc:grpc-context:jar:1.26.0:compile
[INFO] |  |  +- com.google.errorprone:error_prone_annotations:jar:2.3.3:compile
[INFO] |  |  \- org.codehaus.mojo:animal-sniffer-annotations:jar:1.17:compile
[INFO] |  +- com.google.code.gson:gson:jar:2.2.4:compile
[INFO] |  +- com.google.android:annotations:jar:4.1.1.4:compile
[INFO] |  +- io.perfmark:perfmark-api:jar:0.19.0:compile
[INFO] |  +- io.opencensus:opencensus-api:jar:0.24.0:compile
[INFO] |  \- io.opencensus:opencensus-contrib-grpc-metrics:jar:0.24.0:compile
[INFO] +- io.grpc:grpc-protobuf:jar:1.26.0:compile
[INFO] |  +- com.google.api.grpc:proto-google-common-protos:jar:1.12.0:compile
[INFO] |  \- io.grpc:grpc-protobuf-lite:jar:1.26.0:compile
[INFO] +- io.grpc:grpc-stub:jar:1.26.0:compile
[INFO] +- io.grpc:grpc-netty:jar:1.26.0:compile
[INFO] |  +- io.netty:netty-codec-http2:jar:4.1.42.Final:compile (version 
selected from constraint [4.1.42.Final,4.1.42.Final])
[INFO] |  |  +- io.netty:netty-common:jar:4.1.42.Final:compile
[INFO] |  |  +- io.netty:netty-buffer:jar:4.1.42.Final:compile
[INFO] |  |  +- io.netty:netty-transport:jar:4.1.42.Final:compile
[INFO] |  |  |  \- io.netty:netty-resolver:jar:4.1.42.Final:compile
[INFO] |  |  +- io.netty:netty-codec:jar:4.1.42.Final:compile
[INFO] |  |  +- io.netty:netty-handler:jar:4.1.42.Final:compile
[INFO] |  |  \- io.netty:netty-codec-http:jar:4.1.42.Final:compile
[INFO] |  \- io.netty:netty-handler-proxy:jar:4.1.42.Final:compile
[INFO] | \- io.netty:netty-codec-socks:jar:4.1.42.Final:compile
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10331) Upgrade nodejs to 10.x or upper

2020-06-28 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10331:


 Summary: Upgrade nodejs to 10.x or upper
 Key: YARN-10331
 URL: https://issues.apache.org/jira/browse/YARN-10331
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build, yarn-ui-v2
Reporter: Akira Ajisaka


YARN-10036 upgrade Node.js to 8.17.0, but Node.js 8.x is already EoL.
https://nodejs.org/en/about/releases/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10223) Duplicate jersey-test-framework-core dependency in yarn-server-common

2020-04-03 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10223:


 Summary: Duplicate jersey-test-framework-core dependency in 
yarn-server-common
 Key: YARN-10223
 URL: https://issues.apache.org/jira/browse/YARN-10223
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build
Reporter: Akira Ajisaka


The following warning appears in maven log.
{noformat}
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: com.sun.jersey.jersey-test-framework:jersey-test-framework-core:jar 
-> version (?) vs 1.19 @ line 148, column 17
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10156) Fix typo 'complaint' which means quite different in Federation.md

2020-02-26 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10156.
--
Fix Version/s: 2.10.1
   3.1.4
   3.2.2
   2.9.3
   3.3.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Committed this to all the active branches. Thanks [~Elixir Kook] for the 
contribution!

> Fix typo 'complaint' which means quite different in Federation.md
> -
>
> Key: YARN-10156
> URL: https://issues.apache.org/jira/browse/YARN-10156
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation, federation
>Reporter: Sungpeo Kook
>Assignee: Sungpeo Kook
>Priority: Major
> Fix For: 3.3.0, 2.9.3, 3.2.2, 3.1.4, 2.10.1
>
>
> [https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/Federation.html#Running_Applications_across_Sub-Clusters]
> There is a typo in Fedration.md that could be confusing.
> {quote}{{`be complaint to`}} should be {{`be compliant with`}} on the context.
> {quote}
> I think that it need to be corrected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10152) Fix findbugs warnings in hadoop-yarn-applications-mawo-core module

2020-02-18 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10152:


 Summary: Fix findbugs warnings in 
hadoop-yarn-applications-mawo-core module
 Key: YARN-10152
 URL: https://issues.apache.org/jira/browse/YARN-10152
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Akira Ajisaka


{noformat}
    FindBugs :

       
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-mawo/hadoop-yarn-applications-mawo-core
       Class org.apache.hadoop.applications.mawo.server.common.TaskStatus 
implements Cloneable but does not define or use clone method At 
TaskStatus.java:does not define or use clone method At TaskStatus.java:[lines 
39-346]
       Equals method for 
org.apache.hadoop.applications.mawo.server.worker.WorkerId assumes the argument 
is of type WorkerId At WorkerId.java:the argument is of type WorkerId At 
WorkerId.java:[line 114]
       
org.apache.hadoop.applications.mawo.server.worker.WorkerId.equals(Object) does 
not check for null argument At WorkerId.java:null argument At 
WorkerId.java:[lines 114-115] {noformat}
Detail: 
[https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1414/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-applications_hadoop-yarn-applications-mawo_hadoop-yarn-applications-mawo-core-warnings.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-6506) Fix the code vulnerability of org.apache.hadoop.yarn.sls.SLSRunner.simulateInfoMap

2020-02-18 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-6506.
-
Resolution: Cannot Reproduce

Now there are no findbugs warnings in the module. Closing.

> Fix the code vulnerability of 
> org.apache.hadoop.yarn.sls.SLSRunner.simulateInfoMap
> --
>
> Key: YARN-6506
> URL: https://issues.apache.org/jira/browse/YARN-6506
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: scheduler-load-simulator
>Reporter: Yufei Gu
>Priority: Major
>
> It is reported by findbugs in YARN-6423.
> MS_MUTABLE_COLLECTION: Field is a mutable collection
> A mutable collection instance is assigned to a final static field, thus can 
> be changed by malicious code or by accident from another package. Consider 
> wrapping this field into Collections.unmodifiableSet/List/Map/etc. to avoid 
> this vulnerability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9981) Fix findbugs warning in timelineservice

2020-02-18 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9981.
-
Target Version/s:   (was: 3.3.0)
  Resolution: Cannot Reproduce

Now there are no warnings in the module. Closing.

> Fix findbugs warning in timelineservice
> ---
>
> Key: YARN-9981
> URL: https://issues.apache.org/jira/browse/YARN-9981
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: timelineservice
>Affects Versions: 3.3.0
>Reporter: Adam Antal
>Priority: Minor
>
> Findbugs are complaining about this:
> {noformat}
> module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client
>Boxed value is unboxed and then immediately reboxed in 
> org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result,
>  byte[], byte[], KeyConverter, ValueConverter, boolean) At 
> ColumnRWHelper.java:then immediately reboxed in 
> org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result,
>  byte[], byte[], KeyConverter, ValueConverter, boolean) At 
> ColumnRWHelper.java:[line 335]
> {noformat}
> Let's fix it!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-7576) Findbug warning for Resource exposing internal representation

2020-02-18 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-7576.
-
  Assignee: (was: Wangda Tan)
Resolution: Duplicate

Yes, we can close this.

> Findbug warning for Resource exposing internal representation
> -
>
> Key: YARN-7576
> URL: https://issues.apache.org/jira/browse/YARN-7576
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: api
>Affects Versions: 3.0.0
>Reporter: Jason Darrell Lowe
>Priority: Major
> Attachments: YARN-7576.001.patch
>
>
> Precommit builds are complaining about a findbugs warning:
> {noformat}
> EIorg.apache.hadoop.yarn.api.records.Resource.getResources() may expose 
> internal representation by returning Resource.resources
>   
> Bug type EI_EXPOSE_REP (click for details)
> In class org.apache.hadoop.yarn.api.records.Resource
> In method org.apache.hadoop.yarn.api.records.Resource.getResources()
> Field org.apache.hadoop.yarn.api.records.Resource.resources
> At Resource.java:[line 213]
> Returning a reference to a mutable object value stored in one of the object's 
> fields exposes the internal representation of the object.  If instances are 
> accessed by untrusted code, and unchecked changes to the mutable object would 
> compromise security or other important properties, you will need to do 
> something different. Returning a new copy of the object is better approach in 
> many situations.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9742) [JDK11] TestTimelineWebServicesWithSSL.testPutEntities fails

2020-01-16 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9742.
-
Resolution: Cannot Reproduce

> [JDK11] TestTimelineWebServicesWithSSL.testPutEntities fails
> 
>
> Key: YARN-9742
> URL: https://issues.apache.org/jira/browse/YARN-9742
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: timelineservice
>Affects Versions: 3.2.0
>Reporter: Adam Antal
>Priority: Major
>
> Tested on openjdk-11.0.2 on a Mac.
> Stack trace:
> {noformat}
> [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 8.206 
> s <<< FAILURE! - in 
> org.apache.hadoop.yarn.server.timeline.webapp.TestTimelineWebServicesWithSSL
> [ERROR] 
> testPutEntities(org.apache.hadoop.yarn.server.timeline.webapp.TestTimelineWebServicesWithSSL)
>   Time elapsed: 0.366 s  <<< ERROR!
> com.sun.jersey.api.client.ClientHandlerException: java.io.IOException: HTTPS 
> hostname wrong:  should be <0.0.0.0>
>   at 
> com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:155)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineConnector$TimelineJerseyRetryFilter$1.run(TimelineConnector.java:392)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineConnector$TimelineClientConnectionRetry.retryOn(TimelineConnector.java:335)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineConnector$TimelineJerseyRetryFilter.handle(TimelineConnector.java:405)
>   at com.sun.jersey.api.client.Client.handle(Client.java:652)
>   at com.sun.jersey.api.client.WebResource.handle(WebResource.java:682)
>   at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
>   at 
> com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:570)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineWriter.doPostingObject(TimelineWriter.java:152)
>   at 
> org.apache.hadoop.yarn.server.timeline.webapp.TestTimelineWebServicesWithSSL$TestTimelineClient$1.doPostingObject(TestTimelineWebServicesWithSSL.java:139)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineWriter$1.run(TimelineWriter.java:115)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineWriter$1.run(TimelineWriter.java:112)
>   at java.base/java.security.AccessController.doPrivileged(Native Method)
>   at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1891)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineWriter.doPosting(TimelineWriter.java:112)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineWriter.putEntities(TimelineWriter.java:92)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.putEntities(TimelineClientImpl.java:178)
>   at 
> org.apache.hadoop.yarn.server.timeline.webapp.TestTimelineWebServicesWithSSL.testPutEntities(TestTimelineWebServicesWithSSL.java:110)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
>   at 
> 

[jira] [Created] (YARN-10071) Sync Mockito version with other modules

2020-01-07 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10071:


 Summary: Sync Mockito version with other modules
 Key: YARN-10071
 URL: https://issues.apache.org/jira/browse/YARN-10071
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: build, test
Reporter: Akira Ajisaka


YARN-8551 introduced Mockito 1.x dependency, update.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-10057) Upgrade the dependencies managed by yarnpkg

2019-12-24 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-10057.
--
Fix Version/s: 3.3.0
   Resolution: Fixed

Merged the PR into trunk.

> Upgrade the dependencies managed by yarnpkg
> ---
>
> Key: YARN-10057
> URL: https://issues.apache.org/jira/browse/YARN-10057
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: build, yarn-ui-v2
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Fix For: 3.3.0
>
>
> Run "yarn upgrade" to update the dependencies managed by yarnpkg.
> Dependabot automatically created the following pull requests and this issue 
> is to close them.
> * https://github.com/apache/hadoop/pull/1741
> * https://github.com/apache/hadoop/pull/1742
> * https://github.com/apache/hadoop/pull/1743
> * https://github.com/apache/hadoop/pull/1744



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10057) Upgrade dependencies in yarnpkg

2019-12-23 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10057:


 Summary: Upgrade dependencies in yarnpkg
 Key: YARN-10057
 URL: https://issues.apache.org/jira/browse/YARN-10057
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build, yarn-ui-v2
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka


Run "yarn upgrade" to update the dependencies managed by yarnpkg.
Dependabot created the following pull requests and this issue is to close them.

* https://github.com/apache/hadoop/pull/1741
* https://github.com/apache/hadoop/pull/1742
* https://github.com/apache/hadoop/pull/1743
* https://github.com/apache/hadoop/pull/1744



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10055) bower install fails

2019-12-22 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10055:


 Summary: bower install fails
 Key: YARN-10055
 URL: https://issues.apache.org/jira/browse/YARN-10055
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build, yarn-ui-v2
Reporter: Akira Ajisaka


bower install is failing.
{noformat}
bower ENOTFOUND Package abdmob/x2js=abdmob/x2js not found
{noformat}
I ran the following commands:
{noformat}
$ ./start-build.env.sh
$ cd hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp
$ bower install
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10054) Upgrade yarn to the latest version in Dockerfile

2019-12-22 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10054:


 Summary: Upgrade yarn to the latest version in Dockerfile
 Key: YARN-10054
 URL: https://issues.apache.org/jira/browse/YARN-10054
 Project: Hadoop YARN
  Issue Type: Bug
  Components: build, yarn-ui-v2
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka


YARN-10036 wrongly installed yarn 1.12.1. Upgrade to 1.21.1.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10037) Upgrade build tools for YARN Web UI v2

2019-12-16 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10037:


 Summary: Upgrade build tools for YARN Web UI v2
 Key: YARN-10037
 URL: https://issues.apache.org/jira/browse/YARN-10037
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: build, security, yarn-ui-v2
Reporter: Akira Ajisaka


The versions of the build tools are too old and have some vulnerabilities. 
Update.
* node: 5.12.0 (latest: 12.13.1 LTS)
* yarn: 0.21.3 (latest: 1.12.1)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-10036) Install yarn and bower in Dockerfile

2019-12-16 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-10036:


 Summary: Install yarn and bower in Dockerfile
 Key: YARN-10036
 URL: https://issues.apache.org/jira/browse/YARN-10036
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: buid, yarn-ui-v2
 Environment: Now node.js is installed in Dockerfile but yarn (yarnpkg) 
and bower are not installed.
Reporter: Akira Ajisaka






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9987) Upgrade bower to 1.8.8

2019-12-09 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9987.
-
Resolution: Done

The PR has been merged.

> Upgrade bower to 1.8.8
> --
>
> Key: YARN-9987
> URL: https://issues.apache.org/jira/browse/YARN-9987
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn-ui-v2
>Reporter: Akira Ajisaka
>Priority: Major
>
> Merge https://github.com/apache/hadoop/pull/1683 to fix some vulnerabilities.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9958) Remove the invalid lock in ContainerExecutor

2019-12-03 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9958.
-
Fix Version/s: 3.3.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

Committed to trunk. Thanks [~jiwq] for the contribution and thanks [~Tao Yang] 
for the review.

> Remove the invalid lock in ContainerExecutor
> 
>
> Key: YARN-9958
> URL: https://issues.apache.org/jira/browse/YARN-9958
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Wanqiang Ji
>Assignee: Wanqiang Ji
>Priority: Major
> Fix For: 3.3.0
>
>
> ContainerExecutor has ReadLock and WriteLock. These used to call get/put 
> method of ConcurrentMap. Due to the ConcurrentMap providing thread safety and 
> atomicity guarantees, so we can remove the lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9987) Upgrade bower to 1.8.8

2019-11-18 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-9987:
---

 Summary: Upgrade bower to 1.8.8
 Key: YARN-9987
 URL: https://issues.apache.org/jira/browse/YARN-9987
 Project: Hadoop YARN
  Issue Type: Bug
  Components: yarn-ui-v2
Reporter: Akira Ajisaka


Merge https://github.com/apache/hadoop/pull/1683 to fix some vulnerabilities.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9835) 官网代码片段错误

2019-09-17 Thread Akira Ajisaka (Jira)


 [ 
https://issues.apache.org/jira/browse/YARN-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9835.
-
Resolution: Duplicate

> 官网代码片段错误
> 
>
> Key: YARN-9835
> URL: https://issues.apache.org/jira/browse/YARN-9835
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.1.2
>Reporter: lijianfeng
>Priority: Major
> Attachments: image-2019-09-14-14-11-59-342.png
>
>
> 官网说明错误
>  
> !image-2019-09-14-14-11-59-342.png!
> 正确的应该是下面的
> 
> 
> mapreduce.framework.name
> yarn
> 
> 
> mapreduce.application.classpath
> 
> $HADOOP_MAPRED_HOME/share/hadoop/mapreduce/*:$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*
> 
> 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9812) mvn javadoc:javadoc fails in hadoop-sls

2019-09-04 Thread Akira Ajisaka (Jira)
Akira Ajisaka created YARN-9812:
---

 Summary: mvn javadoc:javadoc fails in hadoop-sls
 Key: YARN-9812
 URL: https://issues.apache.org/jira/browse/YARN-9812
 Project: Hadoop YARN
  Issue Type: Bug
  Components: documentation
Reporter: Akira Ajisaka


{noformat}
[ERROR] 
hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/appmaster/DAGAMSimulator.java:57:
 error: bad use of '>'
[ERROR]  * pending -> requests which are NOT yet sent to RM.
[ERROR] ^
[ERROR] 
hadoop-mirror/hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/appmaster/DAGAMSimulator.java:58:
 error: bad use of '>'
[ERROR]  * scheduled -> requests which are sent to RM but not yet assigned.
[ERROR]   ^
[ERROR] 
hadoop-mirror/hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/appmaster/DAGAMSimulator.java:59:
 error: bad use of '>'
[ERROR]  * assigned -> requests which are assigned to a container.
[ERROR]  ^
[ERROR] 
hadoop-mirror/hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/appmaster/DAGAMSimulator.java:60:
 error: bad use of '>'
[ERROR]  * completed -> request corresponding to which container has completed.
[ERROR]   ^
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-6003) yarn-ui build failure caused by debug 2.4.0

2019-08-13 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-6003.
-
Resolution: Not A Problem

Now this issue is not a problem. Closing.

> yarn-ui build failure caused by debug 2.4.0
> ---
>
> Key: YARN-6003
> URL: https://issues.apache.org/jira/browse/YARN-6003
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: build, yarn-ui-v2
>Reporter: Akira Ajisaka
>Priority: Minor
>
> The recent build failure: 
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/255/artifact/out/patch-compile-root.txt
> {noformat}
> /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/debug/debug.js:126
>   debug.color = selectColor(namespae);
> ^
> ReferenceError: namespae is not defined
> at createDebug 
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/debug/debug.js:126:29)
> at Object. 
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/ember-cli/lib/models/project.js:16:43)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object. 
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/ember-cli/lib/cli/index.js:4:21)
> at Module._compile (module.js:456:26)
> {noformat}
> build@2.4.0 is broken. https://github.com/visionmedia/debug/issues/347
> Maybe we need to set the version to 2.4.1 explicitly.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-6260) Findbugs warning in YARN-5355 branch

2019-05-27 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-6260.
-
Resolution: Invalid

The warning no longer exists. Closing.

> Findbugs warning in YARN-5355 branch
> 
>
> Key: YARN-6260
> URL: https://issues.apache.org/jira/browse/YARN-6260
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Varun Saxena
>Priority: Minor
>
> {noformat}
> Bug type SE_BAD_FIELD 
> In class 
> org.apache.hadoop.yarn.server.timelineservice.storage.entity.EntityColumnPrefix
> Field 
> org.apache.hadoop.yarn.server.timelineservice.storage.entity.EntityColumnPrefix.column
> Actual type 
> org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnHelper
> In EntityColumnPrefix.java
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9555) Yarn Docs : single cluster yarn setup - Step 1 configure parameters - multiple roots

2019-05-15 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9555.
-
Resolution: Duplicate

Closing this as duplicate.

> Yarn Docs : single cluster yarn setup - Step 1 configure parameters - 
> multiple roots
> 
>
> Key: YARN-9555
> URL: https://issues.apache.org/jira/browse/YARN-9555
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn
>Affects Versions: 3.0.2
>Reporter: Vishva
>Priority: Minor
>
> Step 1 for 
> [https://hadoop.apache.org/docs/r3.2.0/hadoop-project-dist/hadoop-common/SingleCluster.html#YARN_on_Single_Node]
>  
> Configure parameters as follows:
> {{etc/hadoop/mapred-site.xml}}:
>  
> 
> 
> mapreduce.framework.name
> yarn
> 
> 
> 
> 
> mapreduce.application.classpath
> 
> $HADOOP_MAPRED_HOME/share/hadoop/mapreduce/*:$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*
> 
> 
> but setting this will throw an error when running yarn : 
> {color:#6a9955}2019-05-14{color} {color:#6a9955}16:32:05,815{color} 
> {color:#ce9178}ERROR{color} 
> {color:#569cd6}org.apache.hadoop.conf.Configuration{color}{color:#d4d4d4}: 
> error parsing conf {color}{color:#569cd6}mapred-site.xml{color}
> {color:#ce9178}com.ctc.wstx.exc.WstxParsingException{color}{color:#d4d4d4}: 
> Illegal to have multiple roots (start tag in epilog?).{color}This should be 
> modified to 
> {code:java}
>  
>  
> mapreduce.framework.name 
> yarn 
>  
>  
> mapreduce.application.classpath 
> $HADOOP_MAPRED_HOME/share/hadoop/mapreduce/*:$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*
>  
>  
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9484) Fix SLF4j logging API in AbstractManagedParentQueue#removeChildQueue

2019-04-15 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9484.
-
Resolution: Duplicate

This issue was fixed by YARN-9349. Closing.

> Fix SLF4j logging API in AbstractManagedParentQueue#removeChildQueue
> 
>
> Key: YARN-9484
> URL: https://issues.apache.org/jira/browse/YARN-9484
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacity scheduler
>Affects Versions: 3.2.0
>Reporter: hunshenshi
>Priority: Major
>
> {code:java}
> if (LOG.isDebugEnabled()) {
>   LOG.debug("Removed child queue: {}" + cs.getQueueName());
> }
> {code}
> The '+' should be ','
> {code:java}
> if (LOG.isDebugEnabled()) {
>   LOG.debug("Removed child queue: {}", cs.getQueueName());
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9433) Remove unused constants from RMAuditLogger

2019-04-10 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9433.
-
   Resolution: Fixed
 Hadoop Flags: Reviewed
Fix Version/s: 3.3.0

Committed this to trunk. Thanks [~troclosan] for the contribution!

> Remove unused constants from RMAuditLogger
> --
>
> Key: YARN-9433
> URL: https://issues.apache.org/jira/browse/YARN-9433
> Project: Hadoop YARN
>  Issue Type: Task
>  Components: yarn
>Affects Versions: 3.2.0
>Reporter: Adam Antal
>Priority: Minor
>  Labels: newbie
> Fix For: 3.3.0
>
>
> There are some unused constants in RMAuditLogger that the IntelliJ warns you 
> about.
> Currently what I'm seeing is that the following {{public static final 
> String}} constants are unused:
>  * AM_ALLOCATE
>  * CHANGE_CONTAINER_RESOURCE
>  * CREATE_NEW_RESERVATION_REQUEST
> Probably they are no longer needed. This task aims to remove those unused 
> constants.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-6712) Moving logging APIs over to slf4j in hadoop-yarn

2019-03-22 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-6712.
-
Resolution: Done

All the sub-tasks are resolved. Closing.
Thank you all who contributed to this big task!

> Moving logging APIs over to slf4j in hadoop-yarn
> 
>
> Key: YARN-6712
> URL: https://issues.apache.org/jira/browse/YARN-6712
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Akira Ajisaka
>Priority: Major
> Attachments: YARN-6712.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9308) fairscheduler-statedump.log gets generated regardless of service again after the merge of HDFS-7240

2019-02-14 Thread Akira Ajisaka (JIRA)
Akira Ajisaka created YARN-9308:
---

 Summary: fairscheduler-statedump.log gets generated regardless of 
service again after the merge of HDFS-7240
 Key: YARN-9308
 URL: https://issues.apache.org/jira/browse/YARN-9308
 Project: Hadoop YARN
  Issue Type: Bug
  Components: fairscheduler, scheduler
Affects Versions: 3.2.0
Reporter: Akira Ajisaka


After the merge of HDFS-7240, YARN-6453 occurred again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9065) App's diags is too long,written zk error

2019-02-03 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9065.
-
Resolution: Duplicate

> App's diags is too long,written zk error
> 
>
> Key: YARN-9065
> URL: https://issues.apache.org/jira/browse/YARN-9065
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: applications, resourcemanager
>Affects Versions: 2.8.3, 2.7.7
>Reporter: hunshenshi
>Priority: Major
> Attachments: YARN-9065.patch
>
>
> When use ZKRMStateStore to store app info, App's diags is too long, written 
> zk error.
> The zk error log:
> {code:java}
> 2018-11-27 15:54:30,208 [myid:1] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@373] - Exception 
> causing close of session 0x36753e37803 due to java.io.IOException: Len 
> error 8603591
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9279) Remove the old hamlet package

2019-02-03 Thread Akira Ajisaka (JIRA)
Akira Ajisaka created YARN-9279:
---

 Summary: Remove the old hamlet package
 Key: YARN-9279
 URL: https://issues.apache.org/jira/browse/YARN-9279
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Akira Ajisaka


The old hamlet package was deprecated in HADOOP-11875. Let's remove this to 
improve the maintenability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9183) TestAMRMTokens fails

2019-01-07 Thread Akira Ajisaka (JIRA)
Akira Ajisaka created YARN-9183:
---

 Summary: TestAMRMTokens fails
 Key: YARN-9183
 URL: https://issues.apache.org/jira/browse/YARN-9183
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Akira Ajisaka


TestAMRMTokens.testMasterKeyRollOver and TestAMRMTokens.testTokenExpiry is 
failing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9179) TestAMRMClient crashes

2019-01-07 Thread Akira Ajisaka (JIRA)
Akira Ajisaka created YARN-9179:
---

 Summary: TestAMRMClient crashes
 Key: YARN-9179
 URL: https://issues.apache.org/jira/browse/YARN-9179
 Project: Hadoop YARN
  Issue Type: Bug
  Components: test
Reporter: Akira Ajisaka


{noformat}
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 255
[ERROR] Crashed tests:
[ERROR] org.apache.hadoop.yarn.client.api.impl.TestAMRMClient
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$600(ForkStarter.java:116)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:445)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:421)
[ERROR] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[ERROR] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[ERROR] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[ERROR] at java.lang.Thread.run(Thread.java:748)
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-7456) TestAMRMClient.testAMRMClientWithContainerResourceChange[0] failed

2018-12-30 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-7456.
-
Resolution: Duplicate

Duplicate of YARN-6272. Closing.

> TestAMRMClient.testAMRMClientWithContainerResourceChange[0] failed
> --
>
> Key: YARN-7456
> URL: https://issues.apache.org/jira/browse/YARN-7456
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: resourcemanager
>Affects Versions: 3.0.0-beta1
>Reporter: Haibo Chen
>Assignee: Szilard Nemeth
>Priority: Major
> Attachments: std.out
>
>
> *Error Message*
> expected:<1> but was:<0>
> *Stacktrace*
> java.lang.AssertionError: expected:<1> but was:<0>
>   at 
> org.apache.hadoop.yarn.client.api.impl.TestAMRMClient.doContainerResourceChange(TestAMRMClient.java:1150)
>   at 
> org.apache.hadoop.yarn.client.api.impl.TestAMRMClient.testAMRMClientWithContainerResourceChange(TestAMRMClient.java:1025)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Resolved] (YARN-9062) TestAMRMClient.testAMRMClientWithContainerResourceChange Test fails randomly

2018-12-30 Thread Akira Ajisaka (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka resolved YARN-9062.
-
Resolution: Duplicate

Duplicate of YARN-6272. Closing this.

> TestAMRMClient.testAMRMClientWithContainerResourceChange Test fails randomly
> 
>
> Key: YARN-9062
> URL: https://issues.apache.org/jira/browse/YARN-9062
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: client
>Reporter: Anuruddh Nayak
>Assignee: Abhishek Modi
>Priority: Major
>
> [ERROR] 
> testAMRMClientWithContainerResourceChange[1](org.apache.hadoop.yarn.client.api.impl.TestAMRMClient)
>  Time elapsed: 9.01 s <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<0>
>  at org.junit.Assert.fail(Assert.java:88)
>  at org.junit.Assert.failNotEquals(Assert.java:834)
>  at org.junit.Assert.assertEquals(Assert.java:645)
>  at org.junit.Assert.assertEquals(Assert.java:631)
>  at 
> org.apache.hadoop.yarn.client.api.impl.TestAMRMClient.doContainerResourceChange(TestAMRMClient.java:1019)
>  at 
> org.apache.hadoop.yarn.client.api.impl.TestAMRMClient.testAMRMClientWithContainerResourceChange(TestAMRMClient.java:894)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:497)
>  at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>  at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
>  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-9154) Fix itemization in YARN service quickstart document

2018-12-19 Thread Akira Ajisaka (JIRA)
Akira Ajisaka created YARN-9154:
---

 Summary: Fix itemization in YARN service quickstart document
 Key: YARN-9154
 URL: https://issues.apache.org/jira/browse/YARN-9154
 Project: Hadoop YARN
  Issue Type: Bug
  Components: documentation
Reporter: Akira Ajisaka


{noformat:title=QuickStart.md}
Params:
- SERVICE_NAME: The name of the service. Note that this needs to be unique 
across running services for the current user.
- PATH_TO_SERVICE_DEF: The path to the service definition file in JSON format.
{noformat}
should be
{noformat}
Params:

- SERVICE_NAME: The name of the service. Note that this needs to be unique 
across running services for the current user.
- PATH_TO_SERVICE_DEF: The path to the service definition file in JSON format.
{noformat}
to render correctly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



  1   2   >