[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[ https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178309#comment-14178309 ] Hudson commented on YARN-2673: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #719 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/719/]) YARN-2673. Made timeline client put APIs retry if ConnectException happens. Contributed by Li Lu. (zjshen: rev 89427419a3c5eaab0f73bae98d675979b9efab5f) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestTimelineClient.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/api/impl/TimelineClientImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * hadoop-yarn-project/CHANGES.txt Add retry for timeline client put APIs -- Key: YARN-2673 URL: https://issues.apache.org/jira/browse/YARN-2673 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu Fix For: 2.6.0 Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch, YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-102014.patch Timeline client now does not handle the case gracefully when the server is down. Jobs from distributed shell may fail due to ATS restart. We may need to add some retry mechanisms to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[ https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178428#comment-14178428 ] Hudson commented on YARN-2673: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1908 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1908/]) YARN-2673. Made timeline client put APIs retry if ConnectException happens. Contributed by Li Lu. (zjshen: rev 89427419a3c5eaab0f73bae98d675979b9efab5f) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/api/impl/TimelineClientImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestTimelineClient.java Add retry for timeline client put APIs -- Key: YARN-2673 URL: https://issues.apache.org/jira/browse/YARN-2673 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu Fix For: 2.6.0 Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch, YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-102014.patch Timeline client now does not handle the case gracefully when the server is down. Jobs from distributed shell may fail due to ATS restart. We may need to add some retry mechanisms to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177318#comment-14177318
]
Hadoop QA commented on YARN-2673:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675889/YARN-2673-102014.patch
against trunk revision d5084b9.
{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}. There were no new javadoc 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 2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5462//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5462//console
This message is automatically generated.
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-102014.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[ https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177326#comment-14177326 ] Zhijie Shen commented on YARN-2673: --- +1 will commit the patch Add retry for timeline client put APIs -- Key: YARN-2673 URL: https://issues.apache.org/jira/browse/YARN-2673 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch, YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-102014.patch Timeline client now does not handle the case gracefully when the server is down. Jobs from distributed shell may fail due to ATS restart. We may need to add some retry mechanisms to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[ https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177357#comment-14177357 ] Hudson commented on YARN-2673: -- FAILURE: Integrated in Hadoop-trunk-Commit #6293 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6293/]) YARN-2673. Made timeline client put APIs retry if ConnectException happens. Contributed by Li Lu. (zjshen: rev 89427419a3c5eaab0f73bae98d675979b9efab5f) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestTimelineClient.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/api/impl/TimelineClientImpl.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java Add retry for timeline client put APIs -- Key: YARN-2673 URL: https://issues.apache.org/jira/browse/YARN-2673 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch, YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-102014.patch Timeline client now does not handle the case gracefully when the server is down. Jobs from distributed shell may fail due to ATS restart. We may need to add some retry mechanisms to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176523#comment-14176523
]
Hadoop QA commented on YARN-2673:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675753/YARN-2673-101914.patch
against trunk revision 7bbda6e.
{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}. There were no new javadoc 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 2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5457//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5457//console
This message is automatically generated.
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch, YARN-2673-101714.patch, YARN-2673-101914.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174783#comment-14174783
]
Zhijie Shen commented on YARN-2673:
---
[~gtCarrera], thanks for working on this issue.
bq. Then, on top of this, we can add retry mechanism to delegation token calls
for secured clusters.
GetDelegationToken is not via the jersey client. It needs to be fixed
separately.
bq. We agreed that blocking the timeline client for a short while is better,
since we may not want to drop some critical timeline data.
Make sense to me.
The jersey filter approach looks fine to me. I've some comments w.r.t. the
patch:
1. The variable is only used for testing? Shall we mark it \@VisibleForTesting,
and let the test case access it directly? Also maxRetries and retryInterval.
After retried is set to true first time. It is always true, which means it's
not useful for asserting the second request. Do we really need it? Or we can
spy the filter, and check how many times getNext() has been invoked?
{code}
private boolean retried = false;
{code}
2. Use public synchronized void changeRetrySettings(int maxRetries, long
interval) \{?
{code}
// Customize retry settings synchronously
public void changeRetrySettings(int maxRetries, long interval) {
synchronized(this) {
this.maxRetries = maxRetries;
this.retryInterval = interval;
}
}
{code}
3. Why can it be -1 given the configuration is correct?
{code}
} else {
// note that maxRetries may be -1 at the very beginning
LOG.info(Connection Timeout ( + cr.getURI()
+ ), will keep retrying.);
}
{code}
4. response is unused. And we need to add Assert.fail() after this statement to
ensure the test case will fail if the exception is not thrown.
{code}
TimelinePutResponse response = client.putEntities(generateEntity());
{code}
5. Is this API really necessary? We don't have similar configurations for RPC
based APIs, for example YarnClient methods, right? According to the discussion
on the umbrella YARN-1530, it's still arguable about how to make timeline
client reliable, which may affect this configuration. If we add this API to
timeline client, we have to support it forwardly.
{code}
@Public
public abstract void customizeRetrySettings(int maxRetries,
long retryIntervalMs);
{code}
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175600#comment-14175600
]
Hadoop QA commented on YARN-2673:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675543/YARN-2673-101714.patch
against trunk revision a6aa6e4.
{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}. There were no new javadoc 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 2.0.3) 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-nfs hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs-nfs:
org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication
org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencing
org.apache.hadoop.fs.TestHdfsNativeCodeLoader
The following test timeouts occurred in
hadoop-common-project/hadoop-nfs hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs-nfs:
org.apache.hadoop.hdfs.TestHFlush
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5441//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5441//console
This message is automatically generated.
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch, YARN-2673-101714.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175699#comment-14175699
]
Hadoop QA commented on YARN-2673:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675604/YARN-2673-101714.patch
against trunk revision 1137557.
{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}. There were no new javadoc 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 2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5447//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5447//console
This message is automatically generated.
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch, YARN-2673-101714.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client put APIs
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175814#comment-14175814
]
Zhijie Shen commented on YARN-2673:
---
1. Remove RESTful to be neutral in case the channel is changed?
{code}
+ /** Timeline client RESTful call, max retries (-1 means no limit) */
{code}
2. Add the configs to yarn-default.xml as well
3. It's not necessary any more, because the vars are only set once in the
constructor. In testCheckRetryCount, you can compose config to set the values
you want to use.
{code}
@Private
@VisibleForTesting
public synchronized void changeRetrySettings(int maxRetries, long interval)
{
this.maxRetries = maxRetries;
this.retryInterval = interval;
}
{code}
{code}
// synchronously get a snapshot of current retry settings
int leftRetries = 0;
long sleepMs;
retried = false;
synchronized (this) {
leftRetries = maxRetries;
sleepMs = retryInterval;
}
{code}
4. In testCheckRetryCount, response is not used.
BTW, YARN-2676 is going to change the TimelineClient code. This patch is
subject to rebase.
Add retry for timeline client put APIs
--
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch, YARN-2673-101714.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172052#comment-14172052
]
Hadoop QA commented on YARN-2673:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12674925/YARN-2673-101414-2.patch
against trunk revision 1220bb7.
{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}. There were no new javadoc 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 2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5401//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5401//console
This message is automatically generated.
Add retry for timeline client
-
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client
[ https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171717#comment-14171717 ] Li Lu commented on YARN-2673: - After checking through the code, I'm planning to separate this into two steps. In the first step, we may want to add retry mechanisms to the jersey client that posts timeline entities and domains. After this step, timeline clients for non-secured clusters will be able to retry when timeline server is down. Then, on top of this, we can add retry mechanism to delegation token calls for secured clusters. I'll focus on the non-secured part in this Jira. All secured cluster/token related retry mechanisms will be uploaded to a separate Jira. Add retry for timeline client - Key: YARN-2673 URL: https://issues.apache.org/jira/browse/YARN-2673 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu Timeline client now does not handle the case gracefully when the server is down. Jobs from distributed shell may fail due to ATS restart. We may need to add some retry mechanisms to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171940#comment-14171940
]
Hadoop QA commented on YARN-2673:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12674907/YARN-2673-101414.patch
against trunk revision 0260231.
{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}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 2.0.3) 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-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.yarn.client.api.impl.TestTimelineClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5396//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/5396//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-common.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5396//console
This message is automatically generated.
Add retry for timeline client
-
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171975#comment-14171975
]
Hadoop QA commented on YARN-2673:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12674913/YARN-2673-101414-1.patch
against trunk revision 0260231.
{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}. There were no new javadoc 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 2.0.3) 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-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.yarn.client.api.impl.TestTimelineClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5397//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5397//console
This message is automatically generated.
Add retry for timeline client
-
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-2673) Add retry for timeline client
[
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172026#comment-14172026
]
Hadoop QA commented on YARN-2673:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12674921/YARN-2673-101414-2.patch
against trunk revision 1220bb7.
{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}. There were no new javadoc 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 2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5399//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5399//console
This message is automatically generated.
Add retry for timeline client
-
Key: YARN-2673
URL: https://issues.apache.org/jira/browse/YARN-2673
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Li Lu
Assignee: Li Lu
Attachments: YARN-2673-101414-1.patch, YARN-2673-101414-2.patch,
YARN-2673-101414.patch
Timeline client now does not handle the case gracefully when the server is
down. Jobs from distributed shell may fail due to ATS restart. We may need to
add some retry mechanisms to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
