[jira] [Commented] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[ https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875928#comment-13875928 ] chandrashekhar Kotekar commented on YARN-1586: -- Hi, I am newbie to Hadoop contribution. I think this is the great chance for me to understand how to contribute to Hadoop. Shall I go forward and create the patch for this issue? > Rename FSSchedulerApp to FSSchedulerAppAttempt > -- > > Key: YARN-1586 > URL: https://issues.apache.org/jira/browse/YARN-1586 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Sandy Ryza > Labels: newbie > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[ https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875939#comment-13875939 ] Sandy Ryza commented on YARN-1586: -- Hi chandrashekhar, go for it. > Rename FSSchedulerApp to FSSchedulerAppAttempt > -- > > Key: YARN-1586 > URL: https://issues.apache.org/jira/browse/YARN-1586 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Sandy Ryza > Labels: newbie > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[ https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chandrashekhar Kotekar updated YARN-1586: - Attachment: HADOOP-YARN-1586.patch Done. I have renamed FSSchedulerApp class to FSSchedulerAppAttempt and its corresponding test class TestFSSchedulerApp to TestFSSchedulerAppAttempt. Please check if patch file is correct or not. Thanks, Chandrashekhar > Rename FSSchedulerApp to FSSchedulerAppAttempt > -- > > Key: YARN-1586 > URL: https://issues.apache.org/jira/browse/YARN-1586 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Sandy Ryza > Labels: newbie > Attachments: HADOOP-YARN-1586.patch > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[
https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875979#comment-13875979
]
Hadoop QA commented on YARN-1586:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12623862/HADOOP-YARN-1586.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2909//console
This message is automatically generated.
> Rename FSSchedulerApp to FSSchedulerAppAttempt
> --
>
> Key: YARN-1586
> URL: https://issues.apache.org/jira/browse/YARN-1586
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
>Reporter: Sandy Ryza
> Labels: newbie
> Attachments: HADOOP-YARN-1586.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[ https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhiraj Butala updated YARN-1586: - Attachment: YARN-1586.patch mv-fsschedulerapp.sh Hello, Looks like I was working on this simultaneously too. Please find the attached patch file and the shell script to 'svn mv' the files. I could apply the patch cleanly using dev-support/test-patch.sh . I have captured an issue I faced on my Mac for generating the patch when svn mv is involved on yarn-dev mailing list yesterday: http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201401.mbox/%3CCACn45ToZCTpGpsV5dP-tJ1Yynop-5gybd=FuwbGoPUYVK3=v...@mail.gmail.com%3E Thanks, Abhiraj > Rename FSSchedulerApp to FSSchedulerAppAttempt > -- > > Key: YARN-1586 > URL: https://issues.apache.org/jira/browse/YARN-1586 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Sandy Ryza > Labels: newbie > Attachments: HADOOP-YARN-1586.patch, YARN-1586.patch, > mv-fsschedulerapp.sh > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1586) Rename FSSchedulerApp to FSSchedulerAppAttempt
[
https://issues.apache.org/jira/browse/YARN-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876069#comment-13876069
]
Hadoop QA commented on YARN-1586:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12623878/YARN-1586.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2910//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2910//console
This message is automatically generated.
> Rename FSSchedulerApp to FSSchedulerAppAttempt
> --
>
> Key: YARN-1586
> URL: https://issues.apache.org/jira/browse/YARN-1586
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
>Reporter: Sandy Ryza
> Labels: newbie
> Attachments: HADOOP-YARN-1586.patch, YARN-1586.patch,
> mv-fsschedulerapp.sh
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1613) Fix config name YARN_HISTORY_SERVICE_ENABLED
[ https://issues.apache.org/jira/browse/YARN-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-1613: Attachment: YARN-1613.patch Attaching a patch to fix config name. > Fix config name YARN_HISTORY_SERVICE_ENABLED > > > Key: YARN-1613 > URL: https://issues.apache.org/jira/browse/YARN-1613 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Zhijie Shen > Attachments: YARN-1613.patch > > > YARN_HISTORY_SERVICE_ENABLED property name is "yarn.ahs..enabled", which is > wrong. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1613) Fix config name YARN_HISTORY_SERVICE_ENABLED
[
https://issues.apache.org/jira/browse/YARN-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876151#comment-13876151
]
Hadoop QA commented on YARN-1613:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12623893/YARN-1613.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2911//console
This message is automatically generated.
> Fix config name YARN_HISTORY_SERVICE_ENABLED
>
>
> Key: YARN-1613
> URL: https://issues.apache.org/jira/browse/YARN-1613
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Zhijie Shen
>Assignee: Akira AJISAKA
> Labels: newbie
> Attachments: YARN-1613.patch
>
>
> YARN_HISTORY_SERVICE_ENABLED property name is "yarn.ahs..enabled", which is
> wrong.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (YARN-1615) Fix typos in FSSchedulerApp.java
Akira AJISAKA created YARN-1615:
---
Summary: Fix typos in FSSchedulerApp.java
Key: YARN-1615
URL: https://issues.apache.org/jira/browse/YARN-1615
Project: Hadoop YARN
Issue Type: Bug
Components: documentation, scheduler
Affects Versions: 2.2.0
Reporter: Akira AJISAKA
Assignee: Akira AJISAKA
Priority: Trivial
In FSSchedulerApp.java there're 4 typos:
{code}
* containers over rack-local or off-switch containers. To acheive this
* we first only allow node-local assigments for a given prioirty level,
* then relax the locality threshold once we've had a long enough period
* without succesfully scheduling. We measure both the number of "missed"
{code}
They should be fixed as follows:
{code}
* containers over rack-local or off-switch containers. To achieve this
* we first only allow node-local assignments for a given priority level,
* then relax the locality threshold once we've had a long enough period
* without successfully scheduling. We measure both the number of "missed"
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1611) Make admin refresh* s work for both Active RM and Standby RM
[ https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1611: Attachment: YARN-1611.1.patch > Make admin refresh* s work for both Active RM and Standby RM > > > Key: YARN-1611 > URL: https://issues.apache.org/jira/browse/YARN-1611 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Xuan Gong >Assignee: Xuan Gong > Attachments: YARN-1611.1.patch > > > Currently, If we do refresh* for a standby RM, it will failover to the > current active RM, and do the refresh* based on the local configuration file > of the active RM. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (YARN-1615) Fix typos in FSSchedulerApp.java
[
https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated YARN-1615:
Attachment: YARN-1615.patch
Attaching a patch.
> Fix typos in FSSchedulerApp.java
>
>
> Key: YARN-1615
> URL: https://issues.apache.org/jira/browse/YARN-1615
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, scheduler
>Affects Versions: 2.2.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Trivial
> Labels: newbie
> Attachments: YARN-1615.patch
>
>
> In FSSchedulerApp.java there're 4 typos:
> {code}
>* containers over rack-local or off-switch containers. To acheive this
>* we first only allow node-local assigments for a given prioirty level,
>* then relax the locality threshold once we've had a long enough period
>* without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>* containers over rack-local or off-switch containers. To achieve this
>* we first only allow node-local assignments for a given priority level,
>* then relax the locality threshold once we've had a long enough period
>* without successfully scheduling. We measure both the number of "missed"
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.
[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876175#comment-13876175 ] Xuan Gong commented on YARN-1525: - Yes. [~cindy2012]. Please do that. It is hard to view what exact changes. > Web UI should redirect to active RM when HA is enabled. > --- > > Key: YARN-1525 > URL: https://issues.apache.org/jira/browse/YARN-1525 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Xuan Gong >Assignee: Cindy Li > Attachments: YARN1525.patch.v1 > > > When failover happens, web UI should redirect to the current active rm. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (YARN-1615) Fix typos in FSSchedulerApp.java
[
https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876179#comment-13876179
]
Hadoop QA commented on YARN-1615:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12623903/YARN-1615.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2913//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2913//console
This message is automatically generated.
> Fix typos in FSSchedulerApp.java
>
>
> Key: YARN-1615
> URL: https://issues.apache.org/jira/browse/YARN-1615
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation, scheduler
>Affects Versions: 2.2.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Trivial
> Labels: newbie
> Attachments: YARN-1615.patch
>
>
> In FSSchedulerApp.java there're 4 typos:
> {code}
>* containers over rack-local or off-switch containers. To acheive this
>* we first only allow node-local assigments for a given prioirty level,
>* then relax the locality threshold once we've had a long enough period
>* without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>* containers over rack-local or off-switch containers. To achieve this
>* we first only allow node-local assignments for a given priority level,
>* then relax the locality threshold once we've had a long enough period
>* without successfully scheduling. We measure both the number of "missed"
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1611) Make admin refresh* s work for both Active RM and Standby RM
[
https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876188#comment-13876188
]
Hadoop QA commented on YARN-1611:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12623902/YARN-1611.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.client.TestRMFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2912//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/2912//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-common.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2912//console
This message is automatically generated.
> Make admin refresh* s work for both Active RM and Standby RM
>
>
> Key: YARN-1611
> URL: https://issues.apache.org/jira/browse/YARN-1611
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Xuan Gong
>Assignee: Xuan Gong
> Attachments: YARN-1611.1.patch
>
>
> Currently, If we do refresh* for a standby RM, it will failover to the
> current active RM, and do the refresh* based on the local configuration file
> of the active RM.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1613) Fix config name YARN_HISTORY_SERVICE_ENABLED
[ https://issues.apache.org/jira/browse/YARN-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876198#comment-13876198 ] Shinichi Yamashita commented on YARN-1613: -- +1, LGTM. > Fix config name YARN_HISTORY_SERVICE_ENABLED > > > Key: YARN-1613 > URL: https://issues.apache.org/jira/browse/YARN-1613 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Zhijie Shen >Assignee: Akira AJISAKA > Labels: newbie > Attachments: YARN-1613.patch > > > YARN_HISTORY_SERVICE_ENABLED property name is "yarn.ahs..enabled", which is > wrong. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
