[jira] [Updated] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3604: Description: removeApplication in ZKRMStateStore should also disable watch. Function removeApplication is add

[jira] [Updated] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3604: Labels: BB2015-05-TBR (was: ) > removeApplication in ZKRMStateStore should also disable watch. > ---

[jira] [Updated] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3604: Attachment: YARN-3604.000.patch > removeApplication in ZKRMStateStore should also disable watch. > --

[jira] [Updated] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3604: Issue Type: Bug (was: Improvement) > removeApplication in ZKRMStateStore should also disable watch. > --

[jira] [Updated] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3604: Issue Type: Improvement (was: Bug) > removeApplication in ZKRMStateStore should also disable watch. > --

[jira] [Updated] (YARN-3395) [Fair Scheduler] Handle the user name correctly when user name is used as default queue name.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3395: Attachment: YARN-3395.001.patch > [Fair Scheduler] Handle the user name correctly when user name is used as

[jira] [Commented] (YARN-3395) [Fair Scheduler] Handle the user name correctly when user name is used as default queue name.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535193#comment-14535193 ] zhihai xu commented on YARN-3395: - Hi [~asuresh], thanks for the review. I uploaded a new p

[jira] [Commented] (YARN-3395) [Fair Scheduler] Handle the user name correctly when user name is used as default queue name.

2015-05-08 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535959#comment-14535959 ] zhihai xu commented on YARN-3395: - TestNodeLabelContainerAllocation failure is not related

[jira] [Commented] (YARN-3604) removeApplication in ZKRMStateStore should also disable watch.

2015-05-09 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536272#comment-14536272 ] zhihai xu commented on YARN-3604: - thanks [~jianhe] for the review and committing the patch

[jira] [Commented] (YARN-3602) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IOException from cleanup

2015-05-09 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536270#comment-14536270 ] zhihai xu commented on YARN-3602: - thanks [~xgong] for the review and committing the patch!

[jira] [Commented] (YARN-3395) FairScheduler: Trim whitespaces when using username for queuename

2015-05-09 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537014#comment-14537014 ] zhihai xu commented on YARN-3395: - thanks [~asuresh] for the review and thanks [~kasha] for

[jira] [Created] (YARN-3628) The default value for yarn.nodemanager.container-metrics.period-ms should not be -1.

2015-05-11 Thread zhihai xu (JIRA)
zhihai xu created YARN-3628: --- Summary: The default value for yarn.nodemanager.container-metrics.period-ms should not be -1. Key: YARN-3628 URL: https://issues.apache.org/jira/browse/YARN-3628 Project: Hadoo

[jira] [Updated] (YARN-3628) The default value for yarn.nodemanager.container-metrics.period-ms should not be -1.

2015-05-11 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Attachment: YARN-3628.000.patch > The default value for yarn.nodemanager.container-metrics.period-ms should n

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539421#comment-14539421 ] zhihai xu commented on YARN-3619: - thanks [~kasha] for assigning this JIRA to me. The root

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540715#comment-14540715 ] zhihai xu commented on YARN-3591: - Hi [~lavkesh], thanks for working on this issue. It look

[jira] [Updated] (YARN-3628) The default value for yarn.nodemanager.container-metrics.period-ms should not be -1.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Attachment: (was: YARN-3628.000.patch) > The default value for yarn.nodemanager.container-metrics.period-

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Description: ContainerMetrics should support always-flush mode. It will be good to set ContainerMetrics as al

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Attachment: YARN-3628.000.patch > ContainerMetrics should support always-flush mode. > --

[jira] [Updated] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3619: Attachment: test.patch > ContainerMetrics unregisters during getMetrics and leads to > ConcurrentModificatio

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541328#comment-14541328 ] zhihai xu commented on YARN-3619: - I attached a test patch which can reproduce this issue w

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Attachment: (was: YARN-3628.000.patch) > ContainerMetrics should support always-flush mode. > ---

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Attachment: YARN-3628.000.patch > ContainerMetrics should support always-flush mode. > --

[jira] [Commented] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-12 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541368#comment-14541368 ] zhihai xu commented on YARN-3628: - I updated the patch to fix the whitespace issue. > Cont

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-13 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542347#comment-14542347 ] zhihai xu commented on YARN-3591: - [~vvasudev], that is a good suggestion, which will give

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-13 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Issue Type: Improvement (was: Bug) > ContainerMetrics should support always-flush mode. > --

[jira] [Commented] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-13 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542988#comment-14542988 ] zhihai xu commented on YARN-3628: - Sorry for the confusion. It is jmx. The following is emp

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

2015-05-13 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Description: ContainerMetrics should support always-flush mode. It will be good to set ContainerMetrics as al

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-14 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544708#comment-14544708 ] zhihai xu commented on YARN-3591: - I think the current code call {{removeResource}} instead

[jira] [Created] (YARN-3655) FairScheduler: potential deadlock due to maxAMShare limitation and container reservation

2015-05-15 Thread zhihai xu (JIRA)
zhihai xu created YARN-3655: --- Summary: FairScheduler: potential deadlock due to maxAMShare limitation and container reservation Key: YARN-3655 URL: https://issues.apache.org/jira/browse/YARN-3655 Project:

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.000.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Description: FairScheduler: potential livelock due to maxAMShare limitation and container reservation. If a

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546420#comment-14546420 ] zhihai xu commented on YARN-3655: - I uploaded a patch YARN-3655.000.patch for review. > Fa

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546461#comment-14546461 ] zhihai xu commented on YARN-3591: - [~vinodkv], yes, keeping the ownership of turning disks

[jira] [Created] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-15 Thread zhihai xu (JIRA)
zhihai xu created YARN-3667: --- Summary: Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS Key: YARN-3667 URL: https://issues.apache.

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Description: Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemana

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Attachment: YARN-3667.000.patch > Fix findbugs warning Inconsistent synchronization of > org.apache.hadoop.y

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Description: Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemana

[jira] [Commented] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546521#comment-14546521 ] zhihai xu commented on YARN-3667: - I uploaded a patch for review. The patch is to add synch

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546525#comment-14546525 ] zhihai xu commented on YARN-3655: - findbugs warning is not related to the attached patch, I

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-15 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546590#comment-14546590 ] zhihai xu commented on YARN-3591: - [~lavkesh], Currently DirectoryCollection supports {{ful

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-18 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.001.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-18 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547687#comment-14547687 ] zhihai xu commented on YARN-3655: - I uploaded a new patch YARN-3655.001.patch, which added

[jira] [Updated] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

2015-05-19 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3619: Attachment: YARN-3619.000.patch > ContainerMetrics unregisters during getMetrics and leads to > ConcurrentMo

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

2015-05-19 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550894#comment-14550894 ] zhihai xu commented on YARN-3619: - I uploaded a patch YARN-3619.000.patch for review. I add

[jira] [Commented] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

2015-05-19 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551673#comment-14551673 ] zhihai xu commented on YARN-3667: - [~ozawa], yes, please go ahead and close it as duplicate

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-20 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.002.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-20 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553636#comment-14553636 ] zhihai xu commented on YARN-3655: - thanks [~asuresh] for the review. I think the flip-flop

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553777#comment-14553777 ] zhihai xu commented on YARN-3591: - [~lavkesh], thanks for the new patch. It looks like your

[jira] [Updated] (YARN-3697) FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes.

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3697: Component/s: fairscheduler Affects Version/s: 2.7.0 > FairScheduler: ContinuousSchedulingThread can

[jira] [Created] (YARN-3697) FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes.

2015-05-21 Thread zhihai xu (JIRA)
zhihai xu created YARN-3697: --- Summary: FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes. Key: YARN-3697 URL: https://issues.apache.org/jira/browse/YARN-3697 Project: Hadoop

[jira] [Updated] (YARN-3697) FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes.

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3697: Attachment: YARN-3697.000.patch > FairScheduler: ContinuousSchedulingThread can't be shutdown after stop > s

[jira] [Commented] (YARN-3697) FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes.

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554951#comment-14554951 ] zhihai xu commented on YARN-3697: - I uploaded a patch YARN-3697.000.patch for review. I fi

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555187#comment-14555187 ] zhihai xu commented on YARN-3591: - Calling checkLocalizedResources() on both goodirs and fu

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-21 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555228#comment-14555228 ] zhihai xu commented on YARN-3655: - [~asuresh], thanks for the review. As [~kasha] suggested

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-25 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.003.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Created] (YARN-3710) FairScheduler: Should allocate more containers for assign-multiple after assignReservedContainer turns the reservation into an allocation.

2015-05-25 Thread zhihai xu (JIRA)
zhihai xu created YARN-3710: --- Summary: FairScheduler: Should allocate more containers for assign-multiple after assignReservedContainer turns the reservation into an allocation. Key: YARN-3710 URL: https://issues.apach

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-25 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558428#comment-14558428 ] zhihai xu commented on YARN-3655: - Hi [~kasha], thanks for the review. bq. 1. okToUnreserve

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-25 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: (was: YARN-3655.003.patch) > FairScheduler: potential livelock due to maxAMShare limitation a

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-05-25 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.003.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-05-25 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558727#comment-14558727 ] zhihai xu commented on YARN-3591: - Yes, I think we can get newErrorDirs and newRepairedDirs

[jira] [Updated] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

2015-05-26 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3713: Labels: cleanup maintenance (was: ) > Remove duplicate function call storeContainerDiagnostics in > Contain

[jira] [Created] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

2015-05-26 Thread zhihai xu (JIRA)
zhihai xu created YARN-3713: --- Summary: Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition Key: YARN-3713 URL: https://issues.apache.org/jira/browse/YARN-3713 Pr

[jira] [Updated] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

2015-05-26 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3713: Attachment: YARN-3713.000.patch > Remove duplicate function call storeContainerDiagnostics in > ContainerDia

[jira] [Updated] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

2015-05-26 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3713: Labels: cleanup (was: cleanup maintenance) > Remove duplicate function call storeContainerDiagnostics in >

[jira] [Created] (YARN-3727) For better error recovery, check if the directory exists before using it for localization.

2015-05-27 Thread zhihai xu (JIRA)
zhihai xu created YARN-3727: --- Summary: For better error recovery, check if the directory exists before using it for localization. Key: YARN-3727 URL: https://issues.apache.org/jira/browse/YARN-3727 Project:

[jira] [Updated] (YARN-3727) For better error recovery, check if the directory exists before using it for localization.

2015-05-27 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3727: Description: For better error recovery, check if the directory exists before using it for localization. We s

[jira] [Updated] (YARN-3727) For better error recovery, check if the directory exists before using it for localization.

2015-05-27 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3727: Attachment: YARN-3727.000.patch > For better error recovery, check if the directory exists before using it fo

[jira] [Commented] (YARN-3727) For better error recovery, check if the directory exists before using it for localization.

2015-05-27 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562219#comment-14562219 ] zhihai xu commented on YARN-3727: - I attached a patch YARN-3727.000.patch for review. The p

[jira] [Commented] (YARN-3713) Remove duplicate function call storeContainerDiagnostics in ContainerDiagnosticsUpdateTransition

2015-05-29 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565671#comment-14565671 ] zhihai xu commented on YARN-3713: - thanks [~rkanter] for the review and committing the patc

[jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID

2015-06-01 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566998#comment-14566998 ] zhihai xu commented on YARN-3017: - Hi [~mufeed.usman], thanks for working on this issue. Th

[jira] [Commented] (YARN-3749) We should make a copy of configuration when init MiniYARNCluster with multiple RMs

2015-06-01 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568187#comment-14568187 ] zhihai xu commented on YARN-3749: - Hi [~chenchun], thanks for filing and working on this is

[jira] [Commented] (YARN-3749) We should make a copy of configuration when init MiniYARNCluster with multiple RMs

2015-06-01 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568492#comment-14568492 ] zhihai xu commented on YARN-3749: - [~iwasakims], thanks for the finding and explanations! [

[jira] [Commented] (YARN-3749) We should make a copy of configuration when init MiniYARNCluster with multiple RMs

2015-06-01 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568555#comment-14568555 ] zhihai xu commented on YARN-3749: - [~chenchun], thanks for the new patch, It looks like we

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

2015-06-02 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569727#comment-14569727 ] zhihai xu commented on YARN-3591: - Hi [~lavkesh], I think we can create a separate JIRA for

[jira] [Commented] (YARN-3749) We should make a copy of configuration when init MiniYARNCluster with multiple RMs

2015-06-02 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570131#comment-14570131 ] zhihai xu commented on YARN-3749: - Hi [~chenchun], thanks for updating the patch quickly bq

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-03 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572177#comment-14572177 ] zhihai xu commented on YARN-3655: - Hi [~kasha], thanks for the review. bq. Is it possible t

[jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID

2015-06-03 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572248#comment-14572248 ] zhihai xu commented on YARN-3017: - +1 non-binding The checkstyle issue looks like a script

[jira] [Commented] (YARN-3768) Index out of range exception with environment variables without values

2015-06-04 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573539#comment-14573539 ] zhihai xu commented on YARN-3768: - Hi [~joeferner], That is a good find. I can see the chan

[jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID

2015-06-04 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573593#comment-14573593 ] zhihai xu commented on YARN-3017: - Hi [~rohithsharma], thanks for the information. Sorry, I

[jira] [Commented] (YARN-3745) SerializedException should also try to instantiate internal exception with the default constructor

2015-06-04 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573724#comment-14573724 ] zhihai xu commented on YARN-3745: - [~lavkesh], thanks for working on this issue. This looks

[jira] [Commented] (YARN-3745) SerializedException should also try to instantiate internal exception with the default constructor

2015-06-04 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573745#comment-14573745 ] zhihai xu commented on YARN-3745: - Sorry, there's one more thing I forgot to mention, Can w

[jira] [Assigned] (YARN-3768) Index out of range exception with environment variables without values

2015-06-04 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu reassigned YARN-3768: --- Assignee: zhihai xu > Index out of range exception with environment variables without values > ---

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.004.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: (was: YARN-3655.004.patch) > FairScheduler: potential livelock due to maxAMShare limitation a

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.004.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Created] (YARN-3776) FairScheduler code refactoring to separate out the code paths for assigning a reserved container and a non-reserved container

2015-06-05 Thread zhihai xu (JIRA)
zhihai xu created YARN-3776: --- Summary: FairScheduler code refactoring to separate out the code paths for assigning a reserved container and a non-reserved container Key: YARN-3776 URL: https://issues.apache.org/jira/bro

[jira] [Updated] (YARN-3776) FairScheduler code refactoring to separate out the code paths for assigning a reserved container and a non-reserved container

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3776: Description: FairScheduler code refactoring to separate out the code paths for assigning a reserved containe

[jira] [Updated] (YARN-3776) FairScheduler code refactoring to separate out the code paths for assigning a reserved container and a non-reserved container

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3776: Description: FairScheduler code refactoring, as discussed at YARN-3655, Separate out the code paths for assig

[jira] [Created] (YARN-3777) Move all reservation-related tests from TestFairScheduler to TestFairSchedulerReservations.

2015-06-05 Thread zhihai xu (JIRA)
zhihai xu created YARN-3777: --- Summary: Move all reservation-related tests from TestFairScheduler to TestFairSchedulerReservations. Key: YARN-3777 URL: https://issues.apache.org/jira/browse/YARN-3777 Project

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575472#comment-14575472 ] zhihai xu commented on YARN-3655: - [~kasha], thanks for the thorough review, I uploaded a n

[jira] [Updated] (YARN-3777) Move all reservation-related tests from TestFairScheduler to TestFairSchedulerReservations.

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3777: Component/s: (was: fairscheduler) > Move all reservation-related tests from TestFairScheduler to > TestF

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: (was: YARN-3655.004.patch) > FairScheduler: potential livelock due to maxAMShare limitation a

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-05 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.004.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-06 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.004.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-06 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: (was: YARN-3655.004.patch) > FairScheduler: potential livelock due to maxAMShare limitation a

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-06 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: (was: YARN-3655.004.patch) > FairScheduler: potential livelock due to maxAMShare limitation a

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-06 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.004.patch > FairScheduler: potential livelock due to maxAMShare limitation and containe

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-06 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575992#comment-14575992 ] zhihai xu commented on YARN-3655: - Updated the patch to fix the checkstyle issue. The lates

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

2015-06-07 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576380#comment-14576380 ] zhihai xu commented on YARN-3655: - thanks [~asuresh] for the review! thanks [~kasha] for re

[jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID

2015-06-07 Thread zhihai xu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576519#comment-14576519 ] zhihai xu commented on YARN-3017: - Hi [~rohithsharma], It looked like the above situation f

<    1   2   3   4   5   6   7   8   9   10   >