[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch retrigger > FairScheduler Reserving a node for a container sho

[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch > FairScheduler Reserving a node for a container should

[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.005.patch Fixed whitespace > FairScheduler Reserving a node for a contai

[jira] [Commented] (YARN-4032) Corrupted state from a previous version can still cause RM to fail with NPE due to same reasons as YARN-2834

[ https://issues.apache.org/jira/browse/YARN-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723953#comment-14723953 ] Anubhav Dhoot commented on YARN-4032: - If fail-fast is false we would still nee

[jira] [Commented] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725729#comment-14725729 ] Anubhav Dhoot commented on YARN-3920: - [~asuresh] appreciate your re

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725830#comment-14725830 ] Anubhav Dhoot commented on YARN-4024: - LGTM. Thanks for removing those sleep &g

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.007.patch Attached patch makes a couple of changes. Instead of adding a new

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.008.patch Addressed test failures caused because of missing appattempt data in

[jira] [Commented] (YARN-4087) Set YARN_FAIL_FAST to be false by default

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729422#comment-14729422 ] Anubhav Dhoot commented on YARN-4087: - In general if we are not failing the daemo

[jira] [Created] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

Anubhav Dhoot created YARN-4115: --- Summary: Reduce loglevel of ContainerManagementProtocolProxy to Debug Key: YARN-4115 URL: https://issues.apache.org/jira/browse/YARN-4115 Project: Hadoop YARN

[jira] [Updated] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

[ https://issues.apache.org/jira/browse/YARN-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4115: Attachment: YARN-4115.001.patch Change the default log level to Debug > Reduce loglevel

[jira] [Commented] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731244#comment-14731244 ] Anubhav Dhoot commented on YARN-3676: - Thanks [~asuresh] for working on this. I

[jira] [Updated] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3985: Component/s: (was: fairscheduler) (was: capacityscheduler) > M

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739614#comment-14739614 ] Anubhav Dhoot commented on YARN-2005: - Hi [~kasha] thanks for your comments. 2.4

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739618#comment-14739618 ] Anubhav Dhoot commented on YARN-2005: - [~He Tianyi] yes we are using

[jira] [Created] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

Anubhav Dhoot created YARN-4143: --- Summary: Optimize the check for AMContainer allocation needed by blacklisting and ContainerType Key: YARN-4143 URL: https://issues.apache.org/jira/browse/YARN-4143

[jira] [Assigned] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-4143: --- Assignee: Anubhav Dhoot > Optimize the check for AMContainer allocation needed

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739700#comment-14739700 ] Anubhav Dhoot commented on YARN-2005: - [~sunilg] thats a good suggestion. Add

[jira] [Created] (YARN-4144) Add NM that causes LaunchFailedTransition to blacklist

Anubhav Dhoot created YARN-4144: --- Summary: Add NM that causes LaunchFailedTransition to blacklist Key: YARN-4144 URL: https://issues.apache.org/jira/browse/YARN-4144 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739708#comment-14739708 ] Anubhav Dhoot commented on YARN-2005: - Added YARN-4144 to add the node that ca

[jira] [Created] (YARN-4145) Make RMHATestBase abstract so its not run when running all tests under that namespace

Anubhav Dhoot created YARN-4145: --- Summary: Make RMHATestBase abstract so its not run when running all tests under that namespace Key: YARN-4145 URL: https://issues.apache.org/jira/browse/YARN-4145

[jira] [Updated] (YARN-4145) Make RMHATestBase abstract so its not run when running all tests under that namespace

[ https://issues.apache.org/jira/browse/YARN-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4145: Description: Make it abstract to avoid running it as a test (was: Trivial patch to make it abstract

[jira] [Updated] (YARN-4145) Make RMHATestBase abstract so its not run when running all tests under that namespace

[ https://issues.apache.org/jira/browse/YARN-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4145: Attachment: YARN-4145.001.patch > Make RMHATestBase abstract so its not run when running all te

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.009.patch Addressed feedback > Blacklisting support for scheduling

[jira] [Updated] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3985: Attachment: YARN-3985.001.patch Added a patch that calls into state store and unit test that

[jira] [Commented] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739939#comment-14739939 ] Anubhav Dhoot commented on YARN-3985: - Since updateReservation does an add and re

[jira] [Assigned] (YARN-3273) Improve web UI to facilitate scheduling analysis and debugging

[ https://issues.apache.org/jira/browse/YARN-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3273: --- Assignee: Anubhav Dhoot (was: Rohith Sharma K S) > Improve web UI to facilitate schedul

[jira] [Updated] (YARN-3273) Improve web UI to facilitate scheduling analysis and debugging

[ https://issues.apache.org/jira/browse/YARN-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3273: Assignee: Rohith Sharma K S (was: Anubhav Dhoot) > Improve web UI to facilitate scheduling analy

[jira] [Commented] (YARN-4145) Make RMHATestBase abstract so its not run when running all tests under that namespace

[ https://issues.apache.org/jira/browse/YARN-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741309#comment-14741309 ] Anubhav Dhoot commented on YARN-4145: - The timed out tests are not related to

[jira] [Commented] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

[ https://issues.apache.org/jira/browse/YARN-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741314#comment-14741314 ] Anubhav Dhoot commented on YARN-4115: - The test failure looks unrelated. >

[jira] [Created] (YARN-4150) Failure in TestNMClient because nodereports were not available

Anubhav Dhoot created YARN-4150: --- Summary: Failure in TestNMClient because nodereports were not available Key: YARN-4150 URL: https://issues.apache.org/jira/browse/YARN-4150 Project: Hadoop YARN

[jira] [Commented] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

[ https://issues.apache.org/jira/browse/YARN-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741334#comment-14741334 ] Anubhav Dhoot commented on YARN-4115: - The test passes for me locally. Opened

[jira] [Updated] (YARN-4150) Failure in TestNMClient because nodereports were not available

[ https://issues.apache.org/jira/browse/YARN-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4150: Description: Saw a failure in a test run https://builds.apache.org/job/PreCommit-YARN-Build/9010

[jira] [Commented] (YARN-4150) Failure in TestNMClient because nodereports were not available

[ https://issues.apache.org/jira/browse/YARN-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741338#comment-14741338 ] Anubhav Dhoot commented on YARN-4150: - This is most likely due to the test reading

[jira] [Updated] (YARN-4150) Failure in TestNMClient because nodereports were not available

[ https://issues.apache.org/jira/browse/YARN-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4150: Attachment: YARN-4150.001.patch Simple fix to wait for nodemanagers to be up before trying to get

[jira] [Commented] (YARN-3784) Indicate preemption timout along with the list of containers to AM (preemption message)

[ https://issues.apache.org/jira/browse/YARN-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744006#comment-14744006 ] Anubhav Dhoot commented on YARN-3784: - Hi [~sunilg] this does not include support

[jira] [Created] (YARN-4156) testAMBlacklistPreventsRestartOnSameNode assumes CapacityScheduler

Anubhav Dhoot created YARN-4156: --- Summary: testAMBlacklistPreventsRestartOnSameNode assumes CapacityScheduler Key: YARN-4156 URL: https://issues.apache.org/jira/browse/YARN-4156 Project: Hadoop YARN

[jira] [Updated] (YARN-4156) testAMBlacklistPreventsRestartOnSameNode assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4156: Attachment: YARN-4156.001.patch Uploading patch that configures the scheduler to be

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745775#comment-14745775 ] Anubhav Dhoot commented on YARN-4135: - The patch looks fine except for missing sp

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager

[ https://issues.apache.org/jira/browse/YARN-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745782#comment-14745782 ] Anubhav Dhoot commented on YARN-4130: - LGTM the failures look unrelated > Du

[jira] [Commented] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745893#comment-14745893 ] Anubhav Dhoot commented on YARN-3985: - failures are due to rebase with YARN-3656.

[jira] [Updated] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3985: Attachment: YARN-3985.002.patch Updated patch to modify new tests to add valid ReservationDefinition

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.006.patch Fixed using constant CpuTimeTracker.UNAVAILABLE instead of hard

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.007.patch Fixed javadoc > Metrics for container's actual C

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353272#comment-14353272 ] Anubhav Dhoot commented on YARN-3304: - The intention of setting -1 as was for

[jira] [Moved] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot moved MAPREDUCE-6272 to YARN-3331: Key: YARN-3331 (was: MAPREDUCE-6272) Project: Hadoop YARN

[jira] [Updated] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3331: Component/s: nodemanager > NodeManager should use directory other than tmp for extracting

[jira] [Commented] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1437#comment-1437 ] Anubhav Dhoot commented on YARN-3331: - As per http://grepcode.com/file/r

[jira] [Updated] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3331: Attachment: YARN-3331.001.patch One way to add the variable. [~aw] appreciate your review for the

[jira] [Created] (YARN-3351) AppMaster tracking URL is broken in HA

Anubhav Dhoot created YARN-3351: --- Summary: AppMaster tracking URL is broken in HA Key: YARN-3351 URL: https://issues.apache.org/jira/browse/YARN-3351 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3351) AppMaster tracking URL is broken in HA

[ https://issues.apache.org/jira/browse/YARN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3351: Description: After YARN-2713, the AppMaster link is broken in HA. To repro a) setup RM HA and

[jira] [Commented] (YARN-3351) AppMaster tracking URL is broken in HA

[ https://issues.apache.org/jira/browse/YARN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363284#comment-14363284 ] Anubhav Dhoot commented on YARN-3351: - The issue is the AM tracking link cod

[jira] [Updated] (YARN-3351) AppMaster tracking URL is broken in HA

[ https://issues.apache.org/jira/browse/YARN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3351: Attachment: YARN-3351.001.patch Made the remote RM web url construction (used by NM) independent of

[jira] [Updated] (YARN-3351) AppMaster tracking URL is broken in HA

[ https://issues.apache.org/jira/browse/YARN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3351: Attachment: YARN-3351.002.patch Addressed comments 1 and 3. For 2, i meant any ipaddress, made it

[jira] [Updated] (YARN-3351) AppMaster tracking URL is broken in HA

[ https://issues.apache.org/jira/browse/YARN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3351: Attachment: YARN-3351.003.patch Fix stupid error in order of arguments to assert > AppMas

[jira] [Updated] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3331: Attachment: YARN-3331.002.patch Addressed feedback. Thanks [~aw] for the very specific feedback

[jira] [Commented] (YARN-2581) NMs need to find a way to get LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370279#comment-14370279 ] Anubhav Dhoot commented on YARN-2581: - This is a breaking change and should have

[jira] [Created] (YARN-3392) Change NodeManager metrics to not populate resource usage metrics if they are unavailable

Anubhav Dhoot created YARN-3392: --- Summary: Change NodeManager metrics to not populate resource usage metrics if they are unavailable Key: YARN-3392 URL: https://issues.apache.org/jira/browse/YARN-3392

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376695#comment-14376695 ] Anubhav Dhoot commented on YARN-3304: - Hi [~djp] [~vinodkv], If we use a defaul

[jira] [Assigned] (YARN-2605) [RM HA] Rest api endpoints doing redirect incorrectly

[ https://issues.apache.org/jira/browse/YARN-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2605: --- Assignee: Anubhav Dhoot > [RM HA] Rest api endpoints doing redirect incorrec

[jira] [Updated] (YARN-3392) Change NodeManager metrics to not populate resource usage metrics if they are unavailable

[ https://issues.apache.org/jira/browse/YARN-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3392: Attachment: YARN-3392.prelim.patch Demonstrates how returning negative value to show unavailable

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378303#comment-14378303 ] Anubhav Dhoot commented on YARN-3304: - I have a patch available now for YARN-3392

[jira] [Commented] (YARN-3331) NodeManager should use directory other than tmp for extracting and loading leveldbjni

[ https://issues.apache.org/jira/browse/YARN-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378556#comment-14378556 ] Anubhav Dhoot commented on YARN-3331: - I am not sure which value in core-site w

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381605#comment-14381605 ] Anubhav Dhoot commented on YARN-2893: - The AMLauncher changes look like a possible

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383616#comment-14383616 ] Anubhav Dhoot commented on YARN-3304: - Overall the API looks usable and will fix

[jira] [Updated] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

[ https://issues.apache.org/jira/browse/YARN-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3258: Attachment: YARN-3528.002.patch Addressed feedback > FairScheduler: Need to add more logging

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385064#comment-14385064 ] Anubhav Dhoot commented on YARN-3304: - ProcfsProcessTree#getCumulativeCpuTim

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385352#comment-14385352 ] Anubhav Dhoot commented on YARN-3304: - The renames look good. A couple of comm

[jira] [Updated] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

[ https://issues.apache.org/jira/browse/YARN-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3258: Attachment: YARN-3528.002.patch The failures are all due to webserver unable to start

[jira] [Created] (YARN-3424) Reduce log for ContainerMonitorImpl resoure monitoring from info to debug

Anubhav Dhoot created YARN-3424: --- Summary: Reduce log for ContainerMonitorImpl resoure monitoring from info to debug Key: YARN-3424 URL: https://issues.apache.org/jira/browse/YARN-3424 Project: Hadoop

[jira] [Updated] (YARN-3424) Reduce log for ContainerMonitorImpl resoure monitoring from info to debug

[ https://issues.apache.org/jira/browse/YARN-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3424: Description: Today we log the memory usage of process at info level which spams the log with

[jira] [Updated] (YARN-3424) Reduce log for ContainerMonitorImpl resoure monitoring from info to debug

[ https://issues.apache.org/jira/browse/YARN-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3424: Attachment: YARN-3424.001.patch > Reduce log for ContainerMonitorImpl resoure monitoring from i

[jira] [Commented] (YARN-3424) Change logs for ContainerMonitorImpl's resourse monitoring from info to debug

[ https://issues.apache.org/jira/browse/YARN-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391248#comment-14391248 ] Anubhav Dhoot commented on YARN-3424: - Thanks [~ozawa] for the quick review and co

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495466#comment-14495466 ] Anubhav Dhoot commented on YARN-3485: - Looks like a good change. This makes

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505744#comment-14505744 ] Anubhav Dhoot commented on YARN-3363: - The duration do not seem to belong

[jira] [Created] (YARN-3533) Test: Fix launchAM in MockRM to wait for attempt to be scheduled

Anubhav Dhoot created YARN-3533: --- Summary: Test: Fix launchAM in MockRM to wait for attempt to be scheduled Key: YARN-3533 URL: https://issues.apache.org/jira/browse/YARN-3533 Project: Hadoop YARN

[jira] [Updated] (YARN-3533) Test: Fix launchAM in MockRM to wait for attempt to be scheduled

[ https://issues.apache.org/jira/browse/YARN-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3533: Attachment: YARN-3533.001.patch Fix that adds an explicit wait for state and fixes other waits to

[jira] [Commented] (YARN-3387) container complete message couldn't pass to am if am restarted and rm changed

[ https://issues.apache.org/jira/browse/YARN-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508167#comment-14508167 ] Anubhav Dhoot commented on YARN-3387: - Thanks [~sandflee] for reporting the issu

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511816#comment-14511816 ] Anubhav Dhoot commented on YARN-3363: - LGTM > add localization and container

[jira] [Resolved] (YARN-3392) Change NodeManager metrics to not populate resource usage metrics if they are unavailable

[ https://issues.apache.org/jira/browse/YARN-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-3392. - Resolution: Duplicate > Change NodeManager metrics to not populate resource usage metrics if t

[jira] [Assigned] (YARN-4144) Add NM that causes LaunchFailedTransition to blacklist

[ https://issues.apache.org/jira/browse/YARN-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-4144: --- Assignee: (was: Anubhav Dhoot) > Add NM that causes LaunchFailedTransition to blackl

[jira] [Assigned] (YARN-4030) Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup

[ https://issues.apache.org/jira/browse/YARN-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-4030: --- Assignee: (was: Anubhav Dhoot) > Make Nodemanager cgroup usage for container easier

[jira] [Assigned] (YARN-4076) FairScheduler does not allow AM to choose which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-4076: --- Assignee: (was: Anubhav Dhoot) > FairScheduler does not allow AM to choose wh

[jira] [Assigned] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3994: --- Assignee: (was: Anubhav Dhoot) > RM should respect AM resource/placement constrai

[jira] [Assigned] (YARN-4021) RuntimeException/YarnRuntimeException sent over to the client can cause client to assume a local fatal failure

[ https://issues.apache.org/jira/browse/YARN-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-4021: --- Assignee: (was: Anubhav Dhoot) > RuntimeException/YarnRuntimeException sent over to

[jira] [Assigned] (YARN-3257) FairScheduler: MaxAm may be set too low preventing apps from starting

[ https://issues.apache.org/jira/browse/YARN-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3257: --- Assignee: (was: Anubhav Dhoot) > FairScheduler: MaxAm may be set too low preventing a

[jira] [Assigned] (YARN-3229) Incorrect processing of container as LOST on Interruption during NM shutdown

[ https://issues.apache.org/jira/browse/YARN-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3229: --- Assignee: (was: Anubhav Dhoot) > Incorrect processing of container as LOST

[jira] [Assigned] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3119: --- Assignee: (was: Anubhav Dhoot) > Memory limit check need not be enforced unless aggreg

[jira] [Assigned] (YARN-2661) Container Localization is not resource limited

[ https://issues.apache.org/jira/browse/YARN-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2661: --- Assignee: (was: Anubhav Dhoot) > Container Localization is not resource limi

[jira] [Assigned] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2175: --- Assignee: (was: Anubhav Dhoot) > Container localization has no timeouts and tasks can

[jira] [Assigned] (YARN-2331) Distinguish shutdown during supervision vs. shutdown for rolling upgrade

[ https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2331: --- Assignee: Anubhav Dhoot > Distinguish shutdown during supervision vs. shutdown for roll

[jira] [Updated] (YARN-2331) Distinguish shutdown during supervision vs. shutdown for rolling upgrade

[ https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2331: Assignee: (was: Anubhav Dhoot) > Distinguish shutdown during supervision vs. shutdown

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134762#comment-14134762 ] Anubhav Dhoot commented on YARN-1372: - A finishedContainer that was sent to prev

[jira] [Updated] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1959: Attachment: YARN-1959.prelim.patch Preliminary patch as per discussion - does min of

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.006.patch Addressed feedback except for 2 things (transferring all

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141070#comment-14141070 ] Anubhav Dhoot commented on YARN-1372: - Addressed everything Regar

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.007.patch > Ensure all completed containers are reported to the AMs across

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.008.patch After offline discussion with Jian, remove containers from

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.009.patch Redo upload patch to kick jenkins. Removed unnecessary default

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.009.patch Rebased > Ensure all completed containers are reported to the

<    1   2   3   4   5   6   7   >