[jira] [Commented] (YARN-8022) ResourceManager UI cluster/app/ page fails to render
[
https://issues.apache.org/jira/browse/YARN-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394936#comment-16394936
]
Rohith Sharma K S commented on YARN-8022:
-
This seems even after revert it fails with NPE because of callerUgi null is not
handled.
{code}
2018-03-12 13:36:10,860 ERROR org.apache.hadoop.yarn.server.webapp.AppBlock:
Failed to read the attempts of the application application_1520833852015_0001.
java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.webapp.AppBlock.render(AppBlock.java:145)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.RMAppBlock.render(RMAppBlock.java:71)
{code}
There are many issue fix has gone into AppBlock.java. Pls check all these jira
before uploading new patch.
!Screen Shot 2018-03-12 at 1.45.05 PM.png!
> ResourceManager UI cluster/app/ page fails to render
>
>
> Key: YARN-8022
> URL: https://issues.apache.org/jira/browse/YARN-8022
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
>Affects Versions: 3.1.0, 3.2.0
>Reporter: Tarun Parimi
>Assignee: Tarun Parimi
>Priority: Blocker
> Attachments: Screen Shot 2018-03-12 at 1.45.05 PM.png,
> YARN-8022.001.patch
>
>
> The page displays the message "Failed to read the attempts of the application"
>
> The following stack trace is observed in RM log.
> org.apache.hadoop.yarn.server.webapp.AppBlock: Failed to read the attempts of
> the application application_1520597233415_0002.
> java.lang.NullPointerException
> at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:283)
> at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:280)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682)
> at org.apache.hadoop.yarn.server.webapp.AppBlock.render(AppBlock.java:279)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.RMAppBlock.render(RMAppBlock.java:71)
> at org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:69)
> at
> org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:79)
> at org.apache.hadoop.yarn.webapp.View.render(View.java:235)
> at org.apache.hadoop.yarn.webapp.view.HtmlPage$Page.subView(HtmlPage.java:49)
> at
> org.apache.hadoop.yarn.webapp.hamlet2.HamletImpl$EImp._v(HamletImpl.java:117)
> at org.apache.hadoop.yarn.webapp.hamlet2.Hamlet$TD.__(Hamlet.java:848)
> at
> org.apache.hadoop.yarn.webapp.view.TwoColumnLayout.render(TwoColumnLayout.java:71)
> at org.apache.hadoop.yarn.webapp.view.HtmlPage.render(HtmlPage.java:82)
> at org.apache.hadoop.yarn.webapp.Controller.render(Controller.java:212)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.RmController.app(RmController.java:54)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8022) ResourceManager UI cluster/app/ page fails to render
[ https://issues.apache.org/jira/browse/YARN-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8022: Attachment: Screen Shot 2018-03-12 at 1.45.05 PM.png > ResourceManager UI cluster/app/ page fails to render > > > Key: YARN-8022 > URL: https://issues.apache.org/jira/browse/YARN-8022 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Affects Versions: 3.1.0, 3.2.0 >Reporter: Tarun Parimi >Assignee: Tarun Parimi >Priority: Blocker > Attachments: Screen Shot 2018-03-12 at 1.45.05 PM.png, > YARN-8022.001.patch > > > The page displays the message "Failed to read the attempts of the application" > > The following stack trace is observed in RM log. > org.apache.hadoop.yarn.server.webapp.AppBlock: Failed to read the attempts of > the application application_1520597233415_0002. > java.lang.NullPointerException > at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:283) > at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:280) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682) > at org.apache.hadoop.yarn.server.webapp.AppBlock.render(AppBlock.java:279) > at > org.apache.hadoop.yarn.server.resourcemanager.webapp.RMAppBlock.render(RMAppBlock.java:71) > at org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:69) > at > org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:79) > at org.apache.hadoop.yarn.webapp.View.render(View.java:235) > at org.apache.hadoop.yarn.webapp.view.HtmlPage$Page.subView(HtmlPage.java:49) > at > org.apache.hadoop.yarn.webapp.hamlet2.HamletImpl$EImp._v(HamletImpl.java:117) > at org.apache.hadoop.yarn.webapp.hamlet2.Hamlet$TD.__(Hamlet.java:848) > at > org.apache.hadoop.yarn.webapp.view.TwoColumnLayout.render(TwoColumnLayout.java:71) > at org.apache.hadoop.yarn.webapp.view.HtmlPage.render(HtmlPage.java:82) > at org.apache.hadoop.yarn.webapp.Controller.render(Controller.java:212) > at > org.apache.hadoop.yarn.server.resourcemanager.webapp.RmController.app(RmController.java:54) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-8023) REST API doesn't show new application
[
https://issues.apache.org/jira/browse/YARN-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-8023.
-
Resolution: Invalid
> REST API doesn't show new application
> -
>
> Key: YARN-8023
> URL: https://issues.apache.org/jira/browse/YARN-8023
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
>Affects Versions: 2.7.3
> Environment: Release label:emr-5.5.0
> Hadoop distribution:Amazon 2.7.3
> Applications:Spark 2.1.0, Hive 2.1.1, Hue 3.12.0
>Reporter: Airton Sampaio de Sobral
>Priority: Major
> Attachments: Screen Shot 2018-03-10 at 5.46.13 PM.png
>
>
> After killing an application using the HADOOP UI, and creating a new one with
> the same configuration, the brand new one doesn't appear on the API route:
> /api/v1/applications?status=running
> I've tried the applications path as well (/api/v1/applications) without
> success.
> This happens randomly and it seems that after a really long time, the new
> instance appears on the API.
> On the UI the new application instance appears, and it's working fine. (Print
> screen on attachment).
> On the API it shows the last instance of the application as it's running, but
> it's dead by one hour!
> {code:java}
> /api/v1/applications?status=running
> {
> "id" : "application_1511385973584_0087",
> "name" : "AdActionPaymentKafkaToJDBC",
> "attempts" : [ {
> "attemptId" : "1",
> "startTime" : "2018-01-16T19:08:32.275GMT",
> "endTime" : "1969-12-31T23:59:59.999GMT",
> "lastUpdated" : "2018-01-16T19:08:34.016GMT",
> "duration" : 0,
> "sparkUser" : "hadoop",
> "completed" : false,
> "endTimeEpoch" : -1,
> "startTimeEpoch" : 1516129712275,
> "lastUpdatedEpoch" : 1516129714016
> }
> {code}
>
> Update:
> After two hours, the application appeared on the API response:
>
> {code:java}
> {
> "id" : "application_1511385973584_0154",
> "name" : "AdActionPaymentKafkaToJDBC",
> "attempts" : [ {
> "attemptId" : "1",
> "startTime" : "2018-03-10T21:08:30.557GMT",
> "endTime" : "1969-12-31T23:59:59.999GMT",
> "lastUpdated" : "2018-03-10T21:08:32.310GMT",
> "duration" : 0,
> "sparkUser" : "hadoop",
> "completed" : false,
> "endTimeEpoch" : -1,
> "startTimeEpoch" : 1520716110557,
> "lastUpdatedEpoch" : 1520716112310
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8023) REST API doesn't show new application
[
https://issues.apache.org/jira/browse/YARN-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394870#comment-16394870
]
Rohith Sharma K S commented on YARN-8023:
-
The given REST end points and response are not part of RM daemon. It appears it
is specific to particular vendors. May be you need to contact with them
directly.
I am closing it as invalid. Pls reopen if you feel it is an issue from YARN.
> REST API doesn't show new application
> -
>
> Key: YARN-8023
> URL: https://issues.apache.org/jira/browse/YARN-8023
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
>Affects Versions: 2.7.3
> Environment: Release label:emr-5.5.0
> Hadoop distribution:Amazon 2.7.3
> Applications:Spark 2.1.0, Hive 2.1.1, Hue 3.12.0
>Reporter: Airton Sampaio de Sobral
>Priority: Major
> Attachments: Screen Shot 2018-03-10 at 5.46.13 PM.png
>
>
> After killing an application using the HADOOP UI, and creating a new one with
> the same configuration, the brand new one doesn't appear on the API route:
> /api/v1/applications?status=running
> I've tried the applications path as well (/api/v1/applications) without
> success.
> This happens randomly and it seems that after a really long time, the new
> instance appears on the API.
> On the UI the new application instance appears, and it's working fine. (Print
> screen on attachment).
> On the API it shows the last instance of the application as it's running, but
> it's dead by one hour!
> {code:java}
> /api/v1/applications?status=running
> {
> "id" : "application_1511385973584_0087",
> "name" : "AdActionPaymentKafkaToJDBC",
> "attempts" : [ {
> "attemptId" : "1",
> "startTime" : "2018-01-16T19:08:32.275GMT",
> "endTime" : "1969-12-31T23:59:59.999GMT",
> "lastUpdated" : "2018-01-16T19:08:34.016GMT",
> "duration" : 0,
> "sparkUser" : "hadoop",
> "completed" : false,
> "endTimeEpoch" : -1,
> "startTimeEpoch" : 1516129712275,
> "lastUpdatedEpoch" : 1516129714016
> }
> {code}
>
> Update:
> After two hours, the application appeared on the API response:
>
> {code:java}
> {
> "id" : "application_1511385973584_0154",
> "name" : "AdActionPaymentKafkaToJDBC",
> "attempts" : [ {
> "attemptId" : "1",
> "startTime" : "2018-03-10T21:08:30.557GMT",
> "endTime" : "1969-12-31T23:59:59.999GMT",
> "lastUpdated" : "2018-03-10T21:08:32.310GMT",
> "duration" : 0,
> "sparkUser" : "hadoop",
> "completed" : false,
> "endTimeEpoch" : -1,
> "startTimeEpoch" : 1520716110557,
> "lastUpdatedEpoch" : 1520716112310
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[
https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394857#comment-16394857
]
Rohith Sharma K S commented on YARN-8006:
-
Going through HBase code base, TableDescriptor is interface and
HTableDescriptor implements TableDescriptor. Note that HTableDescriptor is
deprecated but it should still work for backward compatibility.
{code}
/**
* HTableDescriptor contains the details about an HBase table such as the
descriptors of
* all the column families, is the table a catalog table, hbase:meta
,
* if the table is read only, the maximum size of the memstore,
* when the region split should occur, coprocessors associated with it etc...
* @deprecated As of release 2.0.0, this will be removed in HBase 3.0.0.
* Use {@link TableDescriptorBuilder} to build {@link
HTableDescriptor}.
*/
@Deprecated
@InterfaceAudience.Public
public class HTableDescriptor implements TableDescriptor,
Comparable {
{code}
> Make Hbase-2 profile as default for YARN-7055 branch
>
>
> Key: YARN-8006
> URL: https://issues.apache.org/jira/browse/YARN-8006
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Major
> Attachments: YARN-8006-YARN-7055.001.patch,
> YARN-8006-YARN-8006.00.patch
>
>
> In last weekly call folks discussed that we should have separate branch with
> hbase-2 as profile by default. Trunk default profile is hbase-1 which runs
> all the tests under hbase-1 profile. But for hbase-2 profile tests are not
> running.
> As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as
> default. Any server side patches can be given to this branch as well which
> runs tests for hbase-2 profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[
https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394836#comment-16394836
]
Rohith Sharma K S commented on YARN-8006:
-
{quote}But I am not sure how this goes undetected in YARN-7346 when I ran the
test with -Dhbase.profile=2.0.
{quote}
However, in my local machine these tests doesn't fail.
> Make Hbase-2 profile as default for YARN-7055 branch
>
>
> Key: YARN-8006
> URL: https://issues.apache.org/jira/browse/YARN-8006
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Major
> Attachments: YARN-8006-YARN-7055.001.patch,
> YARN-8006-YARN-8006.00.patch
>
>
> In last weekly call folks discussed that we should have separate branch with
> hbase-2 as profile by default. Trunk default profile is hbase-1 which runs
> all the tests under hbase-1 profile. But for hbase-2 profile tests are not
> running.
> As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as
> default. Any server side patches can be given to this branch as well which
> runs tests for hbase-2 profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[ https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394834#comment-16394834 ] Rohith Sharma K S commented on YARN-8006: - thanks [~haibochen] for investigations. bq. But I am not sure how this goes undetected in YARN-7346 when I ran the test with -Dhbase.profile=2.0. I am wondering I did install a cluster with Hbase-2-beta1, created a tables, run sample jobs and able to view from timeline reader and yarn ui2 as well. How can it happen in tests? Do you think it is happening because timelineservice-hbase-client compiled on hbase-1.2.6 and trying to run against hbase-2.0-beta1? > Make Hbase-2 profile as default for YARN-7055 branch > > > Key: YARN-8006 > URL: https://issues.apache.org/jira/browse/YARN-8006 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-8006-YARN-7055.001.patch, > YARN-8006-YARN-8006.00.patch > > > In last weekly call folks discussed that we should have separate branch with > hbase-2 as profile by default. Trunk default profile is hbase-1 which runs > all the tests under hbase-1 profile. But for hbase-2 profile tests are not > running. > As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as > default. Any server side patches can be given to this branch as well which > runs tests for hbase-2 profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8022) ResourceManager UI cluster/app/ page fails to render
[ https://issues.apache.org/jira/browse/YARN-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394828#comment-16394828 ] Rohith Sharma K S commented on YARN-8022: - +1 for reverting only AppBlock. thanks [~tarunparimi] for finding this issue. > ResourceManager UI cluster/app/ page fails to render > > > Key: YARN-8022 > URL: https://issues.apache.org/jira/browse/YARN-8022 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Affects Versions: 3.1.0, 3.2.0 >Reporter: Tarun Parimi >Assignee: Tarun Parimi >Priority: Blocker > Attachments: YARN-8022.001.patch > > > The page displays the message "Failed to read the attempts of the application" > > The following stack trace is observed in RM log. > org.apache.hadoop.yarn.server.webapp.AppBlock: Failed to read the attempts of > the application application_1520597233415_0002. > java.lang.NullPointerException > at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:283) > at org.apache.hadoop.yarn.server.webapp.AppBlock$3.run(AppBlock.java:280) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682) > at org.apache.hadoop.yarn.server.webapp.AppBlock.render(AppBlock.java:279) > at > org.apache.hadoop.yarn.server.resourcemanager.webapp.RMAppBlock.render(RMAppBlock.java:71) > at org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:69) > at > org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:79) > at org.apache.hadoop.yarn.webapp.View.render(View.java:235) > at org.apache.hadoop.yarn.webapp.view.HtmlPage$Page.subView(HtmlPage.java:49) > at > org.apache.hadoop.yarn.webapp.hamlet2.HamletImpl$EImp._v(HamletImpl.java:117) > at org.apache.hadoop.yarn.webapp.hamlet2.Hamlet$TD.__(Hamlet.java:848) > at > org.apache.hadoop.yarn.webapp.view.TwoColumnLayout.render(TwoColumnLayout.java:71) > at org.apache.hadoop.yarn.webapp.view.HtmlPage.render(HtmlPage.java:82) > at org.apache.hadoop.yarn.webapp.Controller.render(Controller.java:212) > at > org.apache.hadoop.yarn.server.resourcemanager.webapp.RmController.app(RmController.java:54) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[ https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392676#comment-16392676 ] Rohith Sharma K S commented on YARN-8006: - The test failures are not happening when run local machine. But regularly failing in jenkins. I clean up maven repo and tried to run tests. It got succeeded. I am unable to trace what is going wrong in jenkins. > Make Hbase-2 profile as default for YARN-7055 branch > > > Key: YARN-8006 > URL: https://issues.apache.org/jira/browse/YARN-8006 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-8006-YARN-7055.001.patch > > > In last weekly call folks discussed that we should have separate branch with > hbase-2 as profile by default. Trunk default profile is hbase-1 which runs > all the tests under hbase-1 profile. But for hbase-2 profile tests are not > running. > As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as > default. Any server side patches can be given to this branch as well which > runs tests for hbase-2 profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[ https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389361#comment-16389361 ] Rohith Sharma K S commented on YARN-8006: - [~haibochen] could you review patch? It appears like test failures and other failures are because of switching to hbase-2 profile default. > Make Hbase-2 profile as default for YARN-7055 branch > > > Key: YARN-8006 > URL: https://issues.apache.org/jira/browse/YARN-8006 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-8006-YARN-7055.001.patch > > > In last weekly call folks discussed that we should have separate branch with > hbase-2 as profile by default. Trunk default profile is hbase-1 which runs > all the tests under hbase-1 profile. But for hbase-2 profile tests are not > running. > As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as > default. Any server side patches can be given to this branch as well which > runs tests for hbase-2 profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
[ https://issues.apache.org/jira/browse/YARN-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8006: Attachment: YARN-8006-YARN-7055.001.patch > Make Hbase-2 profile as default for YARN-7055 branch > > > Key: YARN-8006 > URL: https://issues.apache.org/jira/browse/YARN-8006 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-8006-YARN-7055.001.patch > > > In last weekly call folks discussed that we should have separate branch with > hbase-2 as profile by default. Trunk default profile is hbase-1 which runs > all the tests under hbase-1 profile. But for hbase-2 profile tests are not > running. > As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as > default. Any server side patches can be given to this branch as well which > runs tests for hbase-2 profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389214#comment-16389214 ] Rohith Sharma K S commented on YARN-2442: - test failure is unrelated to the patch, YARN-5240 is exiting jira id. > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8003) Backport the code structure changes in YARN-7346 to branch-2
[ https://issues.apache.org/jira/browse/YARN-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389156#comment-16389156 ] Rohith Sharma K S commented on YARN-8003: - +lgtm.. committing shortly > Backport the code structure changes in YARN-7346 to branch-2 > > > Key: YARN-8003 > URL: https://issues.apache.org/jira/browse/YARN-8003 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 2.10.0 >Reporter: Haibo Chen >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-8003-branch-2.00.patch > > > As discussed in YARN-7346, we want to keep the ATSv2 source code structure in > branch-2 close to that in trunk, in order to ease any future backport. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-7946) Update TimelineServerV2 doc as per YARN-7919
[ https://issues.apache.org/jira/browse/YARN-7946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-7946: --- Assignee: Rohith Sharma K S > Update TimelineServerV2 doc as per YARN-7919 > > > Key: YARN-7946 > URL: https://issues.apache.org/jira/browse/YARN-7946 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > > Post YARN-7919, document need to be updated for co processor jar name and > other related details if any. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7946) Update TimelineServerV2 doc as per YARN-7919
[ https://issues.apache.org/jira/browse/YARN-7946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7946: Issue Type: Sub-task (was: Bug) Parent: YARN-7213 > Update TimelineServerV2 doc as per YARN-7919 > > > Key: YARN-7946 > URL: https://issues.apache.org/jira/browse/YARN-7946 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Priority: Major > > Post YARN-7919, document need to be updated for co processor jar name and > other related details if any. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-8006) Make Hbase-2 profile as default for YARN-7055 branch
Rohith Sharma K S created YARN-8006: --- Summary: Make Hbase-2 profile as default for YARN-7055 branch Key: YARN-8006 URL: https://issues.apache.org/jira/browse/YARN-8006 Project: Hadoop YARN Issue Type: Sub-task Reporter: Rohith Sharma K S Assignee: Rohith Sharma K S In last weekly call folks discussed that we should have separate branch with hbase-2 as profile by default. Trunk default profile is hbase-1 which runs all the tests under hbase-1 profile. But for hbase-2 profile tests are not running. As per the discussion, lets keep YARN-7055 branch for hbase-2 profile as default. Any server side patches can be given to this branch as well which runs tests for hbase-2 profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-7212) [Atsv2] TimelineSchemaCreator fails to create flowrun table causes RegionServer down!
[
https://issues.apache.org/jira/browse/YARN-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-7212.
-
Resolution: Done
Definitely NO. I am closing this JIRA as done as part of YARN-7346
> [Atsv2] TimelineSchemaCreator fails to create flowrun table causes
> RegionServer down!
> -
>
> Key: YARN-7212
> URL: https://issues.apache.org/jira/browse/YARN-7212
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Rohith Sharma K S
>Priority: Major
>
> *Hbase-2.0* officially support *hadoop-alpha* compilations. So I was trying
> to build and test with HBase-2.0. But table schema creation fails and causes
> RegionServer to shutdown with following error
> {noformat}
> Caused by: java.lang.NoSuchMethodError:
> org.apache.hadoop.hbase.Tag.asList([BII)Ljava/util/List;
> at
> org.apache.hadoop.yarn.server.timelineservice.storage.flow.FlowScanner.getCurrentAggOp(FlowScanner.java:250)
> at
> org.apache.hadoop.yarn.server.timelineservice.storage.flow.FlowScanner.nextInternal(FlowScanner.java:226)
> at
> org.apache.hadoop.yarn.server.timelineservice.storage.flow.FlowScanner.next(FlowScanner.java:145)
> at
> org.apache.hadoop.hbase.regionserver.StoreFlusher.performFlush(StoreFlusher.java:132)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreFlusher.flushSnapshot(DefaultStoreFlusher.java:75)
> at org.apache.hadoop.hbase.regionserver.HStore.flushCache(HStore.java:973)
> at
> org.apache.hadoop.hbase.regionserver.HStore$StoreFlusherImpl.flushCache(HStore.java:2252)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2672)
> {noformat}
> Since HBase-2.0 community is ready to release Hadoop-3.x compatible versions,
> ATSv2 also need to support HBase-2.0 versions. For this, we need to take up a
> task of test and validate HBase-2.0 issues!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389011#comment-16389011 ] Rohith Sharma K S commented on YARN-7346: - thanks [~haibochen] for creating YARN-8003. I will take a look at it. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Fix For: 3.2.0 > > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[
https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388071#comment-16388071
]
Rohith Sharma K S commented on YARN-7346:
-
This would become a risk of back porting into branch-2 since HBase-2 claimed to
compile on java8 only. I do see in hbase-env.sh as a note that 1.8+ required.
{code}
# The java implementation to use. Java 1.8+ required.
# export JAVA_HOME=/usr/java/jdk1.8.0/
{code}
Lets drop the idea of supporting HBase-2 in branch-2. cc :/ [~vrushalic]
> Add a profile to allow optional compilation for ATSv2 with HBase-2.0
>
>
> Key: YARN-7346
> URL: https://issues.apache.org/jira/browse/YARN-7346
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Haibo Chen
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: YARN-7346.00.patch, YARN-7346.01.patch,
> YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch,
> YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch,
> YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch,
> YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch,
> YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch,
> YARN-7581.prelim.patch,
> hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml,
> hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt,
> hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml,
> hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt
>
>
> When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3,
> I got the following errors:
> [https://pastebin.com/Ms4jYEVB]
> This issue is to fix the compilation errors.
> The scope of the Jira is to add a profile to allow optional compilation for
> ATSv2 with HBase2.0. The default compilation for trunk will still be for
> hbase 1.2.6.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387957#comment-16387957 ] Rohith Sharma K S commented on YARN-7346: - This is really a good point to be discussed. Does HBase-2.0 officially claims their default Hadoop version is 3.0.0? I just saw looking HBase-2.0-beta release and found that hadoop-2.7.3 jars in HBase/lib folder. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Fix For: 3.2.0 > > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-2442: Attachment: YARN-2442.02.patch > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8001) Newly created Yarn application ID lost after RM failover
[ https://issues.apache.org/jira/browse/YARN-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387624#comment-16387624 ] Rohith Sharma K S commented on YARN-8001: - In such case, YARN Client resubmit the application to new RM with new application id. To the user, there is NO impact. Submitted application start running and succeeds. You should be seeing a log in client something like "Re-submit application with the same ApplicationSubmissionContext" What is the problem are you faced with this kind of restart? Doesn't your application resubmitted and succeeded? > Newly created Yarn application ID lost after RM failover > > > Key: YARN-8001 > URL: https://issues.apache.org/jira/browse/YARN-8001 > Project: Hadoop YARN > Issue Type: Bug > Components: RM >Affects Versions: 2.7.3, 2.9.0 >Reporter: shanyu zhao >Priority: Major > > I’ve seen a problem in Hadoop 2.7.3 where the newly submitted yarn > application was lost after a RM failover. It looks like when handling > Application submission, RM does not write it to the state-store (We are using > zookeeper based state store) immediately before it respond to the client. But > later it failed over to another RM and all write call to the state store > failed. The new RM recovers state from the state-store, and this app is lost. > > The symptom is error message at client side claiming a previously submitted > application ID does not exist: > 2018-02-22 14:54:50,258 [JobControl] WARN > org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider - > Invocation returned exception on [rm1] : > org.apache.hadoop.yarn.exceptions.ApplicationNotFoundException: Application > with id 'application_1519310222933_0160' doesn't exist in RM. Please check > that the job submission was successful. > > This is a timeline excerpted from the resource manager logs: > 2018-02-22 14:54:06.7685260 headnode1 Storing application with id > application_1519310222933_0160 > 2018-02-22 14:54:06.7685660 headnode1 > application_1519310222933_0160 State change from NEW to NEW_SAVING > 2018-02-22 14:54:17.8924760 headnode1 Transitioning to standby state > 2018-02-22 14:54:30.3951160 headnode0 Transitioning to active state -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7919) Refactor timelineservice-hbase module into submodules
[ https://issues.apache.org/jira/browse/YARN-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7919: Fix Version/s: 3.2.0 2.10.0 > Refactor timelineservice-hbase module into submodules > - > > Key: YARN-7919 > URL: https://issues.apache.org/jira/browse/YARN-7919 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineservice >Affects Versions: 3.0.0 >Reporter: Haibo Chen >Assignee: Haibo Chen >Priority: Major > Fix For: 2.10.0, 3.2.0 > > Attachments: YARN-7919-branch-2.05.patch, YARN-7919.00.patch, > YARN-7919.01.patch, YARN-7919.02.patch, YARN-7919.03.patch, > YARN-7919.04.patch, YARN-7919.05.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Fix Version/s: 3.2.0 > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Fix For: 3.2.0 > > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387352#comment-16387352 ] Rohith Sharma K S commented on YARN-7346: - I committed to trunk. thanks [~haibochen] for the patch! Now you can cherry-pick into branch-2. thanks. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387338#comment-16387338 ] Rohith Sharma K S commented on YARN-7346: - I haven't committed yet. I will do it now. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387287#comment-16387287 ] Rohith Sharma K S commented on YARN-7346: - [~haibochen] there are few conflicts for branch-2. Would you provide patch for branch-2? > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387280#comment-16387280 ] Rohith Sharma K S commented on YARN-7346: - committing shortly > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386374#comment-16386374 ] Rohith Sharma K S commented on YARN-7346: - +1 lgtm.. I will commit it later of today if no more objections. thanks [~haibochen] > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.10.patch, > YARN-7346.11.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-4278) On AM registration, response should include cluster Nodes report on demanded by registration request.
[ https://issues.apache.org/jira/browse/YARN-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-4278: --- Assignee: (was: Rohith Sharma K S) > On AM registration, response should include cluster Nodes report on demanded > by registration request. > -- > > Key: YARN-4278 > URL: https://issues.apache.org/jira/browse/YARN-4278 > Project: Hadoop YARN > Issue Type: Improvement > Components: api >Reporter: Rohith Sharma K S >Priority: Major > > From the yarn-dev mailing list discussion thread > [Thread-1|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201510.mbox/%3c0ee80f6f7a98a64ebd18f2be839c91156798a...@szxeml512-mbs.china.huawei.com%3E] > > [Thread-2|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201510.mbox/%3c4f7812fc-ab5d-465d-ac89-824735698...@hortonworks.com%3E] > > Slider required to know about cluster nodes details for providing support for > affinity/anti-affinity on containers. > Current behavior : During life span of application , updatedNodes are sent in > allocate request only if there are any change like added/removed/'state > change' in the nodes. Otherwise cluster nodes not updated to AM. > One of the approach thought by [~ste...@apache.org] is while AM registration > let response hold the cluster nodes report -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.
[
https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S reassigned YARN-6827:
---
Assignee: (was: Rohith Sharma K S)
> [ATS1/1.5] NPE exception while publishing recovering applications into ATS
> during RM restart.
> -
>
> Key: YARN-6827
> URL: https://issues.apache.org/jira/browse/YARN-6827
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Reporter: Rohith Sharma K S
>Priority: Major
>
> While recovering application, it is observed that NPE exception is thrown as
> below.
> {noformat}
> 017-07-13 14:08:12,476 ERROR
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV1Publisher:
> Error when publishing entity
> [YARN_APPLICATION,application_1499929227397_0001]
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.putEntities(TimelineClientImpl.java:178)
> at
> org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV1Publisher.putEntity(TimelineServiceV1Publisher.java:368)
> {noformat}
> This is because in RM service start, active services are started first in Non
> HA case and later ATSv1 services are started. In HA case, tansitionToActive
> event has come first before ATS service are started.
> This gives sufficient time to active services recover the applications which
> tries to publish into ATSv1 while recovering. Since ATS services are not
> started yet, it throws NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-5512) Finished containers for running application should be displayed on container table
[ https://issues.apache.org/jira/browse/YARN-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-5512. - Resolution: Implemented I am not sure which is the sub task under YARN-3368 fixes this issue. But I see completed container details in UI2. So I am closing as implemented. > Finished containers for running application should be displayed on container > table > -- > > Key: YARN-5512 > URL: https://issues.apache.org/jira/browse/YARN-5512 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Major > > In offline discussion with [~vinodkv], one of the point on yarn-web-ui > improvement is, > Currently yarn-web-ui attempt page displays running container details. But > these container disappear once it got finished. Earlier there was no > mechanism to track finished container details. Now, once ATSv2 is ready, > finished containers are being published from NodeManager and can be read. It > would be good if finished containers details also displayed. > In new RM web ui , better if we can consider this also. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6702) Zk connection leak during activeService fail if embedded elector is not curator
[
https://issues.apache.org/jira/browse/YARN-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385916#comment-16385916
]
Rohith Sharma K S commented on YARN-6702:
-
[~bibinchundatt] there are lot of code refactoring happened in ZKRMStateStore.
Do you see is this issue is still a valid ?
> Zk connection leak during activeService fail if embedded elector is not
> curator
> ---
>
> Key: YARN-6702
> URL: https://issues.apache.org/jira/browse/YARN-6702
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha3
>Reporter: Bibin A Chundatt
>Assignee: Rohith Sharma K S
>Priority: Critical
> Attachments: YARN-6702.01.patch
>
>
> {{ResourceManager#transitionToActive}} startActiveService Failure the active
> services are reinitialized.
> {code}
> this.rmLoginUGI.doAs(new PrivilegedExceptionAction() {
> @Override
> public Void run() throws Exception {
> try {
> startActiveServices();
> return null;
> } catch (Exception e) {
> reinitialize(true);
> throw e;
> }
> }
> });
> {code}
> {{ZKRMStateStore#initInternal}} will create another ZK connection.
> {code}
> curatorFramework = resourceManager.getCurator();
> if (curatorFramework == null) {
> curatorFramework = resourceManager.createAndStartCurator(conf);
> }
> {code}
> {quote}
> secureuser@vm1:/opt/hadoop/release/hadoop/sbin> netstat -aen | grep 2181
> tcp0 0 192.168.56.101:49222192.168.56.103:2181
> ESTABLISHED 1004 31984
> tcp0 0 192.168.56.101:46016192.168.56.103:2181
> ESTABLISHED 1004 26120
> tcp0 0 192.168.56.101:50918192.168.56.103:2181
> ESTABLISHED 1004 34761
> tcp0 0 192.168.56.101:49598192.168.56.103:2181
> ESTABLISHED 1004 32483
> tcp0 0 192.168.56.101:49472192.168.56.103:2181
> ESTABLISHED 1004 32364
> tcp0 0 192.168.56.101:50708192.168.56.103:2181
> ESTABLISHED 1004 34310
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7997) Add RM HA state in jmx
[
https://issues.apache.org/jira/browse/YARN-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385914#comment-16385914
]
Rohith Sharma K S commented on YARN-7997:
-
This appears to be duplicate of YARN-2442.
> Add RM HA state in jmx
> ---
>
> Key: YARN-7997
> URL: https://issues.apache.org/jira/browse/YARN-7997
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Bibin A Chundatt
>Priority: Minor
>
> Currently in RM .jmx interface there is not option to know HA state for each
> RM.
> Need an interface similar to Namenode {{FSNamesystem}} provision to know each
> RM state
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-3163) admin support for YarnAuthorizationProvider
[ https://issues.apache.org/jira/browse/YARN-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-3163. - Resolution: Won't Fix > admin support for YarnAuthorizationProvider > --- > > Key: YARN-3163 > URL: https://issues.apache.org/jira/browse/YARN-3163 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > > Runtime configuration support for YarnAuthorizationProvider. Using admin > commands, one should be able to set and get permission from the > YarnAuthorizationProvider. This mechanism will help users without updating > config files and firing reload commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-3162) persistence support for YarnAuthorizationProvider
[ https://issues.apache.org/jira/browse/YARN-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-3162. - Resolution: Won't Fix > persistence support for YarnAuthorizationProvider > - > > Key: YARN-3162 > URL: https://issues.apache.org/jira/browse/YARN-3162 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Sunil G >Assignee: Rohith Sharma K S >Priority: Major > > As discussed in YARN-3100, admin support can be a good addition for > YarnAuthorizationProvider. Hence sync up between memory store and config file > will be of higher importantance. This JIRA will focus on a persistence > storage for ACLs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-7701) Both RM are in standby in secure cluster
[
https://issues.apache.org/jira/browse/YARN-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-7701.
-
Resolution: Cannot Reproduce
I tried in trunk to reproduce same, but could not get this. The reason is
YARN-6061 and YARN-3742 are fixed in trunk which triggers event to transition
to standby.
I am closing as can't reproduce in trunk!
> Both RM are in standby in secure cluster
>
>
> Key: YARN-7701
> URL: https://issues.apache.org/jira/browse/YARN-7701
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Affects Versions: 2.9.0, 2.8.3, 3.0.0
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Critical
> Attachments: YARN-7701.01.patch
>
>
> Both RM were running perfectly fine for many days and switched multiple
> times. At some point of time when RM is switched from ACTIVE -> STANDBY, UGI
> information got either changed or to subject new user got added.
> As a result UGI#getShortUserName() is returning wrong user which result in
> fail to transition to ACTIVE with AccessControlException!
> {code}Caused by: org.apache.hadoop.security.AccessControlException: User
> odsuser doesn't have permission to call 'refreshAdminAcls'
> {code}
> _odsuser_ user is application submitted user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-3418) AM to be able to set/update web URL and IPC ports post-registration
[ https://issues.apache.org/jira/browse/YARN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-3418: --- Assignee: (was: Rohith Sharma K S) > AM to be able to set/update web URL and IPC ports post-registration > --- > > Key: YARN-3418 > URL: https://issues.apache.org/jira/browse/YARN-3418 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.8.0 >Reporter: Steve Loughran >Priority: Major > > Currently the AM can only set the IPC and HTTP(s) ports on AM registration. > This > # creates a possible race condition: the IPC and HTTP ports need to come up > before the app is fully initialised. This is particularly true on > work-preserving AM restarts, as the AM will depend on the list of containers > supplied during registration to build its internal state. > # prevents the AM from changing these values dynamically during application > execution. This matters if the Web or IPC services are hosted not in the AM, > but in a deployed container. If the container is restarted, there's no way to > rebind the services. > A new AM-RM IPC call to publish updated binding information is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384562#comment-16384562 ] Rohith Sharma K S commented on YARN-7346: - I figured out way to compile individual module. It doesn't require any YETUS modifications. Attached incremental patch to know what is the modifications I did for pom.xml. And also attached full patch to run jenkins by taking liberty from Haibo! > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.prelim1.patch, > YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Attachment: YARN-7346.09.patch > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08-incremental.patch, > YARN-7346.08.patch, YARN-7346.09.patch, YARN-7346.prelim1.patch, > YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384349#comment-16384349 ] Rohith Sharma K S commented on YARN-7346: - bq. I believe that personality currently lives in the yetus repository. since you'd be activating a profile, it should only cause a WARN to have the change in place prior to this patch. I cross checked with yarn-UI2 folks [~wangda] [~sunil.gov...@gmail.com] who had added -Pyarn-ui profile for Hadoop. They have added -Pyarn-ui in Hadoop personality precommit in YETUS-463. But for them, yarn-ui is only single module to be build where default compilation wasn't building this profile. In case for ATSv2, there are 2 different module which need to be activated based on the profile. One module will be activated by default always. So my doubt is does Yetus has ability to activate a profile only if corresponding module files are modified? Say, if hbase-2 module files are modified then hbase-2 profile need to be activated. Otherwise I don't think we can control this from YETUS. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7986) ATSv2 REST API queries do not return results for uppercase application tags
[ https://issues.apache.org/jira/browse/YARN-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383384#comment-16383384 ] Rohith Sharma K S commented on YARN-7986: - [~charanh] would you like to provide a patch for this? > ATSv2 REST API queries do not return results for uppercase application tags > --- > > Key: YARN-7986 > URL: https://issues.apache.org/jira/browse/YARN-7986 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Charan Hebri >Priority: Critical > > When applications are submitted to YARN with application tags, the tags are > converted to lowercase. This can be seen on the old/new UI. But using the > original tags for ATSv2 REST API queries do not return results as they expect > the query url to have the tags in lowercase. > This is additional work for the client because each tag needs to be > lowercased before running a query. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383382#comment-16383382 ] Rohith Sharma K S commented on YARN-7346: - I am here by attaching findbug and javadoc report for the 08 patch which is compiled in local machine by activating individual profile. This report shows there is *NO* findbug or javadoc errors exist for hbase-2 profile. - Default profile - hadoop-yarn-server-timelineservice-hbase-server-1 : [^hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml] [^hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt] - Hbase-2 profile - hadoop-yarn-server-timelineservice-hbase-server-2 : [^hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml] [^hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt] > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Attachment: hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Attachment: hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch, > hadoop-yarn-server-timelineservice-hbase-server-1-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-1-javadoc-report.txt, > hadoop-yarn-server-timelineservice-hbase-server-2-findbugsXml.xml, > hadoop-yarn-server-timelineservice-hbase-server-2-javadoc-report.txt > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383113#comment-16383113 ] Rohith Sharma K S commented on YARN-7346: - Thanks [~busbey] for suggestions. Should we raise any corresponding bug in Yetus to make this change? If it is going to be delayed much more then expected, could we do this change post committing this patch? This is first step for supporting hbase-2 profile, and there are many stability issues with hbase-2 which need to be fixed. And many other stories such as ACLs are depends on this JIRA. Basically we have blocked by this patch. However ATSv2 folks takes *responsibility of ensuring that there are NO* findbugs and javadoc errors are introduced for hbase-2 profile modules. We have discussed this plan in weekly call as I commented earlier also to have separate jenkins in branch with hbase-2 profile as default. As a long term, we definitely want to go ahead with your suggestion which we can start discussion how to achieve it. > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to allow optional compilation for ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383079#comment-16383079 ] Rohith Sharma K S commented on YARN-7346: - bq. We should fix this by updating the Hadoop personality so that we only run in each module with an appropriate profile active Sorry didn't get it. Could you elaborate more? Does this change is in Yetus or current patch? > Add a profile to allow optional compilation for ATSv2 with HBase-2.0 > > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > [https://pastebin.com/Ms4jYEVB] > This issue is to fix the compilation errors. > The scope of the Jira is to add a profile to allow optional compilation for > ATSv2 with HBase2.0. The default compilation for trunk will still be for > hbase 1.2.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to compile ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382293#comment-16382293 ] Rohith Sharma K S commented on YARN-7346: - [~haibochen] Its better to attach findbugs report xml file which is compiles against default profile and compiles against hbase-2 profile. And also we should attach javadoc compilation for HBase-2 profile. This gives clarity for viewers that we haven't committed this patch without looking into findbugs or java doc errors. This is necessary because for any viewer who come and look at JIRA, they think that we have committed that patch even though findbugs and javadoc errors reported by jenkins. So, lets upload a final patch findbugs and javadoc compilation report for both the profiles. You can use below commands to run from _hadoop-yarn-server-timelineservice-hbase-server_ module. - Default compilation : *mvn clean install findbugs:findbugs javadoc:javadoc -DskipTests=true* - HBase-2 profile compilation : *mvn clean install findbugs:findbugs javadoc:javadoc -DskipTests=true -Dhbase.profile=2.0* With the above reports, we will be in safer side to convince folks if someone question regarding jenkins report. > Add a profile to compile ATSv2 with HBase-2.0 > - > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382127#comment-16382127
]
Rohith Sharma K S commented on YARN-5028:
-
I have verified basic RM restart scenarios and looks fine if we include
addendum patch. [~sunilg]/[~yufeigu] Could you guys please help to commit this
addendum patch? I am not sure which are all the branches this is committed
earlier!
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007-addendum.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to compile ATSv2 with HBase-2.0
[
https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381951#comment-16381951
]
Rohith Sharma K S commented on YARN-7346:
-
{quote}I'd like to see everything under control before it goes into trunk
though; that's get javadocs and findbugs to shut up
{quote}
By default yetus runs for hbase-1 profile which is default. This is causing
findbug and java doc errors for hbase-2 modules. We can produce a findbug and
java doc report for HBase-2 profile separately and can be attached to JIRA as a
proof. But if someone expect that jenkins has to run for both hbase-1 and
hbase-2 profile all the time then really I don't have solution. IIUC from other
projects like Tez, jenkins runs for single profile always but Yetus is running
for modular compilation which is generating findbug and java doc errors.
{quote}setting the hbase-2 profile will allow the rest of Hadoop to build with
guava.version=21.0?
{quote}
This is something we have to discuss/test irrespective of HBase-2 profile that
compiles against HBase-2.0-beta1 which is doing in this JIRA. I am not sure why
HADOOP-15272 depends on this JIRA! ATSv2 is already uses Hbase-1.2.6 as back
end and uses guava 11.
> Add a profile to compile ATSv2 with HBase-2.0
> -
>
> Key: YARN-7346
> URL: https://issues.apache.org/jira/browse/YARN-7346
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Haibo Chen
>Priority: Major
> Attachments: YARN-7346.00.patch, YARN-7346.01.patch,
> YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch,
> YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch,
> YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch,
> YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch
>
>
> When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3,
> I got the following errors:
> https://pastebin.com/Ms4jYEVB
> This issue is to fix the compilation errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381801#comment-16381801
]
Rohith Sharma K S commented on YARN-5028:
-
Updated patch adding app name and app tags included.
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007-addendum.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-5028:
Attachment: YARN-5028.007-addendum.patch
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007-addendum.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381784#comment-16381784
]
Rohith Sharma K S commented on YARN-5028:
-
I found that couple of more issues where app report also throw NPE for
following URL i.e *http://localhost:8088/ws/v1/cluster/apps*. It seems we
should add application name and application tags as well.
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7986) ATSv2 REST API queries do not return results for uppercase application tags
[
https://issues.apache.org/jira/browse/YARN-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381661#comment-16381661
]
Rohith Sharma K S commented on YARN-7986:
-
Thanks [~charanh] for reporting this issue. This seems to be an issue with tags
which is sent in ApplicationSubmissionContext. I see
ApplicationSubmissionContextPBImpl sets explicitly to lowercase. Seems like
tags are case insensitive as we see explicit comment in below code.
{code}
@Override
public void setApplicationTags(Set tags) {
...
...
// Convert applicationTags to lower case and add
this.applicationTags = new HashSet();
for (String tag : tags) {
this.applicationTags.add(StringUtils.toLowerCase(tag));
}
}
{code}
ATSv2 is designed to be case sensitive. So either we might need to add
documentation that providing a tags is always case insensitive or ATSv2 code
always convert all the parameter into lowercase and store it in back end.
[~vrushalic] [~haibo.chen] any suggestions on this ?
> ATSv2 REST API queries do not return results for uppercase application tags
> ---
>
> Key: YARN-7986
> URL: https://issues.apache.org/jira/browse/YARN-7986
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Charan Hebri
>Priority: Critical
>
> When applications are submitted to YARN with application tags, the tags are
> converted to lowercase. This can be seen on the old/new UI. But using the
> original tags for ATSv2 REST API queries do not return results as they expect
> the query url to have the tags in lowercase.
> This is additional work for the client because each tag needs to be
> lowercased before running a query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381582#comment-16381582
]
Rohith Sharma K S commented on YARN-5028:
-
As it is blocking ATS enabled recovery flows, taking liberty to attach quick
addendum patch for fixing this issue
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-5028:
Attachment: YARN-5028.007-addendum.patch
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007-addendum.patch,
> YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Reopened] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S reopened YARN-5028:
-
Reopening to attach addendum patch
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381556#comment-16381556
]
Rohith Sharma K S commented on YARN-5028:
-
[~grepas] [~yufeigu] this seems to be breaking when ATS is enabled. When
applications are recovered for completed applications, if ats is enabled it try
to publish which is leading NPE. This NPE causes RM to shutdown which is fatal
issue.
{noformat}
2018-02-28 03:21:54,322 ERROR resourcemanager.ResourceManager
(ResourceManager.java:serviceStart(808)) - Failed to load/recover state
java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.metrics.TimelineServiceV1Publisher.appCreated(TimelineServiceV1Publisher.java:91)
at
org.apache.hadoop.yarn.server.resourcemanager.metrics.CombinedSystemMetricsPublisher.appCreated(CombinedSystemMetricsPublisher.java:44)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.sendATSCreateEvent(RMAppImpl.java:1984)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.recover(RMAppImpl.java:946)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:1076)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:1069)
at
org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
at
org.apache.hadoop.yarn.state.StateMachineFactory.access$500(StateMachineFactory.java:46)
at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:487)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:893)
at
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recoverApplication(RMAppManager.java:361)
at
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recover(RMAppManager.java:573)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.recover(ResourceManager.java:1426)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceStart(ResourceManager.java:803)
at
org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.startActiveServices(ResourceManager.java:1179)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$1.run(ResourceManager.java:1219)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$1.run(ResourceManager.java:1215)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.transitionToActive(ResourceManager.java:1215)
at
org.apache.hadoop.yarn.server.resourcemanager.AdminService.transitionToActive(AdminService.java:320)
at
org.apache.hadoop.yarn.server.resourcemanager.ActiveStandbyElectorBasedElectorService.becomeActive(ActiveStandbyElectorBasedElectorService.java:144)
at
org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:893)
at
org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:473)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:611)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510)
{noformat}
This issue has committed into 3.1 which is blocker in this release. Either this
issue need to be reverted or provide a addendum patch for 3.1 release.
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store
[jira] [Commented] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt is launched on the same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381533#comment-16381533 ] Rohith Sharma K S commented on YARN-7835: - This should also need to be fixed for branch-2. Could you cherry-pick it ? > [Atsv2] Race condition in NM while publishing events if second attempt is > launched on the same node > --- > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Fix For: 3.2.0 > > Attachments: YARN-7835.001.patch, YARN-7835.002.patch, > YARN-7835.003.patch, YARN-7835.004.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain
[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7933: Attachment: YARN-7933.02.patch > [atsv2 read acls] Add TimelineWriter#writeDomain > - > > Key: YARN-7933 > URL: https://issues.apache.org/jira/browse/YARN-7933 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7933.01.patch, YARN-7933.02.patch > > > > Add an API TimelineWriter#writeDomain for writing the domain info -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain
[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380096#comment-16380096 ] Rohith Sharma K S commented on YARN-7933: - As discussed offline with [~vrushalic], scope of this JIRA is for collector side implementation. Following will be done as part of this jira # add a REST endpoint i.e */domain* for collector that accepts TimelineDomain object for storing into back-end. Its a PUT operation. # Provide interface in TimelineWriter to write TimelineDomain information to back-end storage. > [atsv2 read acls] Add TimelineWriter#writeDomain > - > > Key: YARN-7933 > URL: https://issues.apache.org/jira/browse/YARN-7933 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7933.01.patch > > > > Add an API TimelineWriter#writeDomain for writing the domain info -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt launched on same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380020#comment-16380020 ] Rohith Sharma K S commented on YARN-7835: - [~haibo.chen] would you be able to commit this patch? > [Atsv2] Race condition in NM while publishing events if second attempt > launched on same node > > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Attachments: YARN-7835.001.patch, YARN-7835.002.patch, > YARN-7835.003.patch, YARN-7835.004.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7932) [atsv2 read acls] Add a API TimelineV2Client#putDomain to publish domain information.
[ https://issues.apache.org/jira/browse/YARN-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7932: Summary: [atsv2 read acls] Add a API TimelineV2Client#putDomain to publish domain information. (was: [atsv2 read acls] Add TimelineDomain to entity) > [atsv2 read acls] Add a API TimelineV2Client#putDomain to publish domain > information. > - > > Key: YARN-7932 > URL: https://issues.apache.org/jira/browse/YARN-7932 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7932.001.patch > > > > Need to have a TimelineDomain class in atsv2 that can contain the acls info > for entities. TimelineEntity will contain TimelineDomain as a member -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Add a profile to compile ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379863#comment-16379863 ] Rohith Sharma K S commented on YARN-7346: - [~busbey] Do you have any concerns/doubts on the approach we are taking? We greatly appreciate your suggestions/inputs. Otherwise we are planning to proceed ahead for committing this patch this weekend. > Add a profile to compile ATSv2 with HBase-2.0 > - > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7932) [atsv2 read acls] Add TimelineDomain to entity
[ https://issues.apache.org/jira/browse/YARN-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379831#comment-16379831 ] Rohith Sharma K S commented on YARN-7932: - As discussed offline with [~vrushalic], exposing TimelineV2Client API is the last step of ACLs story. So we shall keep this to end of ACLs story. Lets start with YARN-7933 which does server side implementation first and related back end jira. > [atsv2 read acls] Add TimelineDomain to entity > -- > > Key: YARN-7932 > URL: https://issues.apache.org/jira/browse/YARN-7932 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7932.001.patch > > > > Need to have a TimelineDomain class in atsv2 that can contain the acls info > for entities. TimelineEntity will contain TimelineDomain as a member -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Add a profile to compile ATSv2 with HBase-2.0
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Summary: Add a profile to compile ATSv2 with HBase-2.0 (was: Fix compilation errors against hbase2 beta release) > Add a profile to compile ATSv2 with HBase-2.0 > - > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7983) Add table for storing timeline domain information
[ https://issues.apache.org/jira/browse/YARN-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7983: Summary: Add table for storing timeline domain information (was: Add table for storing timeline domain informations) > Add table for storing timeline domain information > - > > Key: YARN-7983 > URL: https://issues.apache.org/jira/browse/YARN-7983 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Rohith Sharma K S >Priority: Major > > Create a timeline domain table in HBase for storing domain information -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7983) Add table for storing timeline domain informations
Rohith Sharma K S created YARN-7983: --- Summary: Add table for storing timeline domain informations Key: YARN-7983 URL: https://issues.apache.org/jira/browse/YARN-7983 Project: Hadoop YARN Issue Type: Sub-task Reporter: Rohith Sharma K S Create a timeline domain table in HBase for storing domain information -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7982) Do ACLs check while retrieving entity-types per application
Rohith Sharma K S created YARN-7982:
---
Summary: Do ACLs check while retrieving entity-types per
application
Key: YARN-7982
URL: https://issues.apache.org/jira/browse/YARN-7982
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Rohith Sharma K S
REST end point {{/apps/$appid/entity-types}} retrieves all the entity-types for
given application. This need to be guarded with ACL check
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7978) Do ACLs check for flowrun entities
[ https://issues.apache.org/jira/browse/YARN-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7978: Summary: Do ACLs check for flowrun entities (was: Do ACLs check while retrieving flowrun entities) > Do ACLs check for flowrun entities > -- > > Key: YARN-7978 > URL: https://issues.apache.org/jira/browse/YARN-7978 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelinereader >Reporter: Rohith Sharma K S >Priority: Major > > Verify ACLs while retrieving flowrun entities -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7981) Do ACLs check for sub app entities
Rohith Sharma K S created YARN-7981: --- Summary: Do ACLs check for sub app entities Key: YARN-7981 URL: https://issues.apache.org/jira/browse/YARN-7981 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S ACLs check while retrieving sub app entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7980) Do ACLs check for generic entities
Rohith Sharma K S created YARN-7980: --- Summary: Do ACLs check for generic entities Key: YARN-7980 URL: https://issues.apache.org/jira/browse/YARN-7980 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S This JIRA is to verify ACLs for generic entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7979) Do ACLs check for application entities
Rohith Sharma K S created YARN-7979: --- Summary: Do ACLs check for application entities Key: YARN-7979 URL: https://issues.apache.org/jira/browse/YARN-7979 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S Verify ACLs for application entities -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7978) Do ACLs check while retrieving flowrun entities
[ https://issues.apache.org/jira/browse/YARN-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7978: Summary: Do ACLs check while retrieving flowrun entities (was: Do ACLs check while retriving flowrun entities) > Do ACLs check while retrieving flowrun entities > --- > > Key: YARN-7978 > URL: https://issues.apache.org/jira/browse/YARN-7978 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelinereader >Reporter: Rohith Sharma K S >Priority: Major > > Verify ACLs while retrieving flowrun entities -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7978) Do ACLs check while retriving flowrun entities
Rohith Sharma K S created YARN-7978: --- Summary: Do ACLs check while retriving flowrun entities Key: YARN-7978 URL: https://issues.apache.org/jira/browse/YARN-7978 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S Verify ACLs while retrieving flowrun entities -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7977) Do ACLs check for flow activity entities
Rohith Sharma K S created YARN-7977: --- Summary: Do ACLs check for flow activity entities Key: YARN-7977 URL: https://issues.apache.org/jira/browse/YARN-7977 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Rohith Sharma K S Verify ACLs while retrieving flow activity entities -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7976) [atsv2 read acls] REST API to list domain/domains
Rohith Sharma K S created YARN-7976:
---
Summary: [atsv2 read acls] REST API to list domain/domains
Key: YARN-7976
URL: https://issues.apache.org/jira/browse/YARN-7976
Project: Hadoop YARN
Issue Type: Sub-task
Components: timelinereader
Reporter: Rohith Sharma K S
Assignee: Rohith Sharma K S
Provide REST API to list domains and domain in TimelineReaderWebService.
/domains and /domain/\{domainId}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7957) Yarn service delete option disappears after stopping application
[
https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378102#comment-16378102
]
Rohith Sharma K S commented on YARN-7957:
-
{{ServiceTimelinePublisher#serviceAttemptUnregistered}} publishes state. This
code can be modified to publish service state rather than yarn application
state. But at this point of time, service should have already updated the right
state otherwise old state will be published.
{code}
diff --git
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/timelineservice/ServiceTimelinePublisher.java
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/timelineservice/ServiceTimelinePublisher.java
index 949ce19c8dc..4e2b03959ee 100644
---
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/timelineservice/ServiceTimelinePublisher.java
+++
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/timelineservice/ServiceTimelinePublisher.java
@@ -135,7 +135,7 @@ public void serviceAttemptUnregistered(ServiceContext
context,
context.attemptId.getApplicationId().toString());
Map entityInfos = new HashMap();
entityInfos.put(ServiceTimelineMetricsConstants.STATE,
-FinalApplicationStatus.ENDED);
+context.service.getState());
entityInfos.put(DIAGNOSTICS_INFO, diagnostics);
entity.addInfo(entityInfos);
{code}
> Yarn service delete option disappears after stopping application
>
>
> Key: YARN-7957
> URL: https://issues.apache.org/jira/browse/YARN-7957
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Affects Versions: 3.1.0
>Reporter: Yesha Vora
>Assignee: Sunil G
>Priority: Critical
> Attachments: YARN-7957.01.patch
>
>
> Steps:
> 1) Launch yarn service
> 2) Go to service page and click on Setting button->"Stop Service". The
> application will be stopped.
> 3) Refresh page
> Here, setting button disappears. Thus, user can not delete service from UI
> after stopping application
> Expected behavior:
> Setting button should be present on UI page after application is stopped. If
> application is stopped, setting button should only have "Delete Service"
> action available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375275#comment-16375275 ] Rohith Sharma K S commented on YARN-7346: - +1 lgtm for 08 patch. Pending Jenkins. [~busbey] do you have any concerns/doubts on the approach we are taking? We greatly appreciate your suggestions/inputs. Otherwise I will proceed ahead for committing this patch this weekend. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.07.patch, YARN-7346.08.patch, > YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374508#comment-16374508 ] Rohith Sharma K S edited comment on YARN-7346 at 2/23/18 3:41 PM: -- bq. Even if this module for HBase 2.0.0 support isn't the default used in trunk, shouldn't we still be testing changes to the module? This is the basic conditional compilation modules gap. For this, in last ATSv2 community call decided to use YARN-7055 branch as HBase-2.0 default module. And all the patch going into trunk should also be verified for the branch YARN-7055 as well that confirms that nothing break for HBase-2 module. Otherwise we can't proceed ahead with any decisions ending with this Jenkins issue. There are many other issue to be addressed for stability. Umbrella YARN-7213 tracks it for HBase-2.0 which need to be addressed. This is the first patch with conditional compilation modules to be committed. We ensures that default compilation, packaging, findbug, checkstyle and others doesn't break anything for HBase-1 module which is activated by default. was (Author: rohithsharma): bq. Even if this module for HBase 2.0.0 support isn't the default used in trunk, shouldn't we still be testing changes to the module? This is the basic conditional compilation modules gap. For this, in last ATSv2 community call decided to use YARN-7055 branch as HBase-2.0 default module. And all the patch going into trunk should also be verified for the branch YARN-7055 as well that confirms that nothing break for HBase-2 module. Otherwise we can't proceed ahead with any decisions ending with this Jenkins issue. There are many other issue to be addressed for stability. Umbrella YARN-7213 tracks it for HBase-2.0 which need to be addressed. This is the first patch with conditional compilation modules to be committed. We ensures that default compilation, packaging, findbug, checkstyle and others doesn't break anything from previous ones. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374508#comment-16374508 ] Rohith Sharma K S edited comment on YARN-7346 at 2/23/18 3:40 PM: -- bq. Even if this module for HBase 2.0.0 support isn't the default used in trunk, shouldn't we still be testing changes to the module? This is the basic conditional compilation modules gap. For this, in last ATSv2 community call decided to use YARN-7055 branch as HBase-2.0 default module. And all the patch going into trunk should also be verified for the branch YARN-7055 as well that confirms that nothing break for HBase-2 module. Otherwise we can't proceed ahead with any decisions ending with this Jenkins issue. There are many other issue to be addressed for stability. Umbrella YARN-7213 tracks it for HBase-2.0 which need to be addressed. This is the first patch with conditional compilation modules to be committed. We ensures that default compilation, packaging, findbug, checkstyle and others doesn't break anything from previous ones. was (Author: rohithsharma): bq. Even if this module for HBase 2.0.0 support isn't the default used in trunk, shouldn't we still be testing changes to the module? This is the basic conditional compilation modules gap. For this, in last ATSv2 community call decided to use YARN-7055 branch as HBase-2.0 default module. And all the patch going into trunk should also be verified for the branch YARN-7055 as well that confirms that nothing break for HBase-2 module. Otherwise we can't proceed ahead with any decisions ending with this Jenkins issue. There are many other issue to be addressed for stability. Umbrella YARN-7213 tracks it for HBase-2.0 which need to be addressed. This is the fist patch with conditional compilation modules to be committed. We ensures that default compilation, packaging, findbug, checkstyle and others doesn't break anything from previous ones. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374508#comment-16374508 ] Rohith Sharma K S commented on YARN-7346: - bq. Even if this module for HBase 2.0.0 support isn't the default used in trunk, shouldn't we still be testing changes to the module? This is the basic conditional compilation modules gap. For this, in last ATSv2 community call decided to use YARN-7055 branch as HBase-2.0 default module. And all the patch going into trunk should also be verified for the branch YARN-7055 as well that confirms that nothing break for HBase-2 module. Otherwise we can't proceed ahead with any decisions ending with this Jenkins issue. There are many other issue to be addressed for stability. Umbrella YARN-7213 tracks it for HBase-2.0 which need to be addressed. This is the fist patch with conditional compilation modules to be committed. We ensures that default compilation, packaging, findbug, checkstyle and others doesn't break anything from previous ones. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374000#comment-16374000 ] Rohith Sharma K S commented on YARN-7346: - [~haibochen] To me, we should retain 05 patch itself and findbugs and java docs are irrelevant errors. As I see that Yetus is trying to find findbug.xml file which doesn't exist. I think we should go ahead and commit 05 patch. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.05.patch, > YARN-7346.06.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain
[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7933: Attachment: YARN-7933.01.patch > [atsv2 read acls] Add TimelineWriter#writeDomain > - > > Key: YARN-7933 > URL: https://issues.apache.org/jira/browse/YARN-7933 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7933.01.patch > > > > Add an API TimelineWriter#writeDomain for writing the domain info -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt launched on same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7835: Attachment: YARN-7835.004.patch > [Atsv2] Race condition in NM while publishing events if second attempt > launched on same node > > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Attachments: YARN-7835.001.patch, YARN-7835.002.patch, > YARN-7835.003.patch, YARN-7835.004.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt launched on same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372437#comment-16372437 ] Rohith Sharma K S commented on YARN-7835: - Updated the patch as per comments > [Atsv2] Race condition in NM while publishing events if second attempt > launched on same node > > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Attachments: YARN-7835.001.patch, YARN-7835.002.patch, > YARN-7835.003.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt launched on same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7835: Attachment: YARN-7835.003.patch > [Atsv2] Race condition in NM while publishing events if second attempt > launched on same node > > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Attachments: YARN-7835.001.patch, YARN-7835.002.patch, > YARN-7835.003.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7835) [Atsv2] Race condition in NM while publishing events if second attempt launched on same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372407#comment-16372407 ] Rohith Sharma K S commented on YARN-7835: - Thanks [~haibochen] for detailed review. Make sense to me, I will update the patch with test modifications. > [Atsv2] Race condition in NM while publishing events if second attempt > launched on same node > > > Key: YARN-7835 > URL: https://issues.apache.org/jira/browse/YARN-7835 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Rohith Sharma K S >Assignee: Rohith Sharma K S >Priority: Critical > Attachments: YARN-7835.001.patch, YARN-7835.002.patch > > > It is observed race condition that if master container is killed for some > reason and launched on same node then NMTimelinePublisher doesn't add > timelineClient. But once completed container for 1st attempt has come then > NMTimelinePublisher removes the timelineClient. > It causes all subsequent event publishing from different client fails to > publish with exception Application is not found. ! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7346: Attachment: YARN-7346.04-incremental.patch > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.prelim1.patch, > YARN-7346.prelim2.patch, YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[
https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371512#comment-16371512
]
Rohith Sharma K S commented on YARN-7346:
-
I found that adding below in default profile solves the issue. Updated the
incremental patch for 04 with following changes plus some other comments I
wanted to give for 04 patch!
{code}
org.apache.maven.plugins
maven-compiler-plugin
default-compile
none
{code}
[~haibochen] can you try incremental patch and combine both?
> Fix compilation errors against hbase2 beta release
> --
>
> Key: YARN-7346
> URL: https://issues.apache.org/jira/browse/YARN-7346
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Haibo Chen
>Priority: Major
> Attachments: YARN-7346.00.patch, YARN-7346.01.patch,
> YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch,
> YARN-7346.04-incremental.patch, YARN-7346.04.patch, YARN-7346.prelim1.patch,
> YARN-7346.prelim2.patch, YARN-7581.prelim.patch
>
>
> When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3,
> I got the following errors:
> https://pastebin.com/Ms4jYEVB
> This issue is to fix the compilation errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7932) [atsv2 read acls] Add TimelineDomain to entity
[ https://issues.apache.org/jira/browse/YARN-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371299#comment-16371299 ] Rohith Sharma K S commented on YARN-7932: - Updated the patch to incorporate TimelineDomain into TimelineEntity. And also added new API i.e putDomain(TimelineDomain domain) to publish domain information. This is a blocking call. cc:/ [~vrushalic] > [atsv2 read acls] Add TimelineDomain to entity > -- > > Key: YARN-7932 > URL: https://issues.apache.org/jira/browse/YARN-7932 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7932.001.patch > > > > Need to have a TimelineDomain class in atsv2 that can contain the acls info > for entities. TimelineEntity will contain TimelineDomain as a member -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7932) [atsv2 read acls] Add TimelineDomain to entity
[ https://issues.apache.org/jira/browse/YARN-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7932: Attachment: YARN-7932.001.patch > [atsv2 read acls] Add TimelineDomain to entity > -- > > Key: YARN-7932 > URL: https://issues.apache.org/jira/browse/YARN-7932 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Rohith Sharma K S >Priority: Major > Attachments: YARN-7932.001.patch > > > > Need to have a TimelineDomain class in atsv2 that can contain the acls info > for entities. TimelineEntity will contain TimelineDomain as a member -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371129#comment-16371129 ] Rohith Sharma K S commented on YARN-7346: - Spoke to many of our colleagues offline from different upstream Hadoop projects. The typical conditional compilation would be a same as our original idea i.e activating respective modules based on profile is set. I think we should strict to our original approach and try to solve Jenkins issue where it is running for both modules. Other way to exploit the Jenkin issue is by providing two different patch in different JIRA! # Provide a patch for hbase-2 module by making HBase-2 module as default profile. Do not include hbase-1 src/main java files in module in the patch at all. Jenkins runs for HBase-2 module. We can commit it. # After 1st one is committed, provide a patch for hbase-1 module that includes src files and change default profile to HBase-1 as default. This patch shouldn't contains hbase-2 module changes so that Jenkins doesn't run for hbase-2 modules. But risk factor in future is any changes made for HBase-2 module end up in Jenkins failure. Given, no more changes would come for timelineservice-hbase-server module, then we can go ahead with this approach. IAC, I have dropped a mail to [~aw] and [~ajisakaa] for getting help for this from Yetus. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370996#comment-16370996 ] Rohith Sharma K S commented on YARN-7346: - Looks like compiling both the version fails because of Dependency convergence error for hadoop-yarn-server-timelineservice-hbase-common. We can't go ahead with option-2 because of Dependency convergence check. > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Haibo Chen >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications
[
https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370958#comment-16370958
]
Rohith Sharma K S commented on YARN-5028:
-
latest patch reasonable to me
> RMStateStore should trim down app state for completed applications
> --
>
> Key: YARN-5028
> URL: https://issues.apache.org/jira/browse/YARN-5028
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 2.8.0
>Reporter: Karthik Kambatla
>Assignee: Gergo Repas
>Priority: Major
> Attachments: YARN-5028.000.patch, YARN-5028.001.patch,
> YARN-5028.002.patch, YARN-5028.003.patch, YARN-5028.004.patch,
> YARN-5028.005.patch, YARN-5028.006.patch, YARN-5028.007.patch
>
>
> RMStateStore stores enough information to recover applications in case of a
> restart. The store also retains this information for completed applications
> to serve their status to REST, WebUI, Java and CLI clients. We don't need all
> the information we store today to serve application status; for instance, we
> don't need the {{ApplicationSubmissionContext}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370471#comment-16370471 ] Rohith Sharma K S commented on YARN-7346: - Looking into timelinservice-hbase-* code, it actually depends on only 2 jars i.e hbase-server and hbase-common. Rest of the dependencies we can remove from pom.xml. Considering this, I would recommend for option-2 which I mentioned that ensures we don't break anything across the different versions of hbase. Does it make sense? > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Vrushali C >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370445#comment-16370445 ] Rohith Sharma K S commented on YARN-7346: - [~vrushalic] do you have any suggestion for options? > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Vrushali C >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7346) Fix compilation errors against hbase2 beta release
[ https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370445#comment-16370445 ] Rohith Sharma K S edited comment on YARN-7346 at 2/20/18 6:51 PM: -- [~vrushalic] do you have any suggestion for above mentioned options? was (Author: rohithsharma): [~vrushalic] do you have any suggestion for options? > Fix compilation errors against hbase2 beta release > -- > > Key: YARN-7346 > URL: https://issues.apache.org/jira/browse/YARN-7346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Vrushali C >Priority: Major > Attachments: YARN-7346.00.patch, YARN-7346.01.patch, > YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch, > YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch, > YARN-7581.prelim.patch > > > When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3, > I got the following errors: > https://pastebin.com/Ms4jYEVB > This issue is to fix the compilation errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[
https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370444#comment-16370444
]
Rohith Sharma K S commented on YARN-7346:
-
Ahh I see! I guess src/main/java package is compiled by default if it exist.
If we want to override that compilation then we can use below property which is
NOT recommended.
{code}
true
{code}
However let do following things which I feel that's better
# Option-1
## Lets activate module hbase-1 vs hbase-2 based on profile is set as we are
doing in last patch. It compiles only respective modules based on profile is
set.
## Let add true for hbase-2 for default compilation. It
allows default compilation NOT to happen. This is only for avoiding jenkins not
to run compile against HBase-2.0 unless profile is activated.
# Option-2
## Lets compile both hbase-1 and hbase-2 all the time which ensures compilation
is not broken with patches.
## Include co-process jar in distribution only based on the profile set.
## For this we need to enable corresponding dependencies in hbase-2 modules as
well.
## For test, default profile can be set to hbase1 by default.
> Fix compilation errors against hbase2 beta release
> --
>
> Key: YARN-7346
> URL: https://issues.apache.org/jira/browse/YARN-7346
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Vrushali C
>Priority: Major
> Attachments: YARN-7346.00.patch, YARN-7346.01.patch,
> YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch,
> YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch,
> YARN-7581.prelim.patch
>
>
> When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3,
> I got the following errors:
> https://pastebin.com/Ms4jYEVB
> This issue is to fix the compilation errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7346) Fix compilation errors against hbase2 beta release
[
https://issues.apache.org/jira/browse/YARN-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369901#comment-16369901
]
Rohith Sharma K S commented on YARN-7346:
-
Couple of additional comments
# hadoop-project/pom.xml has jcodings by default. This can be removed since
hbase2 profile has this dependency explicitly.
# For packaging issue which discussed in previously comment, we can use
property to name the module structure. There are 2 modules i.e
_hadoop-yarn-server-timelineservice-hbase-server-1_ and
_hadoop-yarn-server-timelineservice-hbase-server-2_ where one module will be
activated at any given point of time. So we can use module structure like
_hadoop-yarn-server-timelineservice-hbase-server-*${hbase.profile.version}*_ in
hadoop-yarn-dist.xml assembly file. And need to add _hbase.profile.version_
property along with hbase.version in hadoop-project#pom.xml
# Given 2nd option works, hadoop-yarn-dist.xml has commented modifications.
This could be removed.
# Nits : Below names can be consistent either without space or with space
between Timeline Service vs TimelineService!
{code}
[INFO] Apache Hadoop YARN TimelineService HBase Backend ... SUCCESS [ 0.004 s]
[INFO] Apache Hadoop YARN TimelineService HBase Common SUCCESS [ 0.045 s]
[INFO] Apache Hadoop YARN TimelineService HBase Client SUCCESS [ 0.032 s]
[INFO] Apache Hadoop YARN Timeline Service HBase Servers .. SUCCESS [ 0.002 s]
[INFO] Apache Hadoop YARN TimelineService HBase Server 1.2 SUCCESS [ 0.014 s]
[INFO] Apache Hadoop YARN Timeline Service HBase tests SUCCESS [ 0.015 s]
{code}
> Fix compilation errors against hbase2 beta release
> --
>
> Key: YARN-7346
> URL: https://issues.apache.org/jira/browse/YARN-7346
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Vrushali C
>Priority: Major
> Attachments: YARN-7346.00.patch, YARN-7346.01.patch,
> YARN-7346.02.patch, YARN-7346.03-incremental.patch, YARN-7346.03.patch,
> YARN-7346.04.patch, YARN-7346.prelim1.patch, YARN-7346.prelim2.patch,
> YARN-7581.prelim.patch
>
>
> When compiling hadoop-yarn-server-timelineservice-hbase against 2.0.0-alpha3,
> I got the following errors:
> https://pastebin.com/Ms4jYEVB
> This issue is to fix the compilation errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
