[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Status: Patch Available (was: Open) > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v7.patch > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Attachment: AMBARI-18978-quick-link-profile-data-model_trunk_v7.patch Patch with fix. > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v7.patch > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Attachment: (was: AMBARI-18978-quick-link-profile-data-model_trunk_v5.patch) > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: trunk, 2.5.0 > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18978) Create Quick link profile data model and json parser
[ https://issues.apache.org/jira/browse/AMBARI-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18978: --- Status: Open (was: Patch Available) > Create Quick link profile data model and json parser > > > Key: AMBARI-18978 > URL: https://issues.apache.org/jira/browse/AMBARI-18978 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: trunk, 2.5.0 > > > Create the data model and JSON parser for quick link profiles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755788#comment-15755788
]
Hadoop QA commented on AMBARI-19227:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843642/AMBARI-19227.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9712//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9712//console
This message is automatically generated.
> Provide support to show Ranger solr-configs in Ambari
> -
>
> Key: AMBARI-19227
> URL: https://issues.apache.org/jira/browse/AMBARI-19227
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19227.patch
>
>
> Need to provide feature for Ranger and update Ambari stacks to show
> solrconfig.xml on Ambari, so that user can update solr related configs
> directly from Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[
https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755737#comment-15755737
]
Hadoop QA commented on AMBARI-19228:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843651/AMBARI-19228.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9711//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9711//console
This message is automatically generated.
> Knox doesn't redirect to Atlas after entering correct credentials, when Atlas
> is setup with Knox-SSO
>
>
> Key: AMBARI-19228
> URL: https://issues.apache.org/jira/browse/AMBARI-19228
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19228.patch
>
>
> After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands
> back on the login page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755686#comment-15755686 ] Hudson commented on AMBARI-19220: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6252 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6252/]) AMBARI-19220. ADDENDUM. Fix version of HDFS and YARN used by HDP 3.0 (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e8a6b85de5ead2b9feb8afd0c39fa57eeb5bcc4e]) * (edit) ambari-server/pom.xml > Fix version of HDFS and YARN used by HDP 3.0 > > > Key: AMBARI-19220 > URL: https://issues.apache.org/jira/browse/AMBARI-19220 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19220.patch > > > HDP 3.0 is set to use HDFS and YARN from the versions in common services. > HDFS will use 3.0.0.3.0 > YARN will ise 3.0.0.3.0 > Right now there's a bug in that the metainfo.xml file for the new YARN in > common services has its version set to 2.1.0.2.0, which is obviously > incorrect and causes older stack versions to inherit newer properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755663#comment-15755663 ] Hudson commented on AMBARI-19220: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #548 (See [https://builds.apache.org/job/Ambari-branch-2.5/548/]) AMBARI-19220. ADDENDUM. Fix version of HDFS and YARN used by HDP 3.0 (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f2618b485954b17d97e48902049661a0719fed69]) * (edit) ambari-server/pom.xml > Fix version of HDFS and YARN used by HDP 3.0 > > > Key: AMBARI-19220 > URL: https://issues.apache.org/jira/browse/AMBARI-19220 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19220.patch > > > HDP 3.0 is set to use HDFS and YARN from the versions in common services. > HDFS will use 3.0.0.3.0 > YARN will ise 3.0.0.3.0 > Right now there's a bug in that the metainfo.xml file for the new YARN in > common services has its version set to 2.1.0.2.0, which is obviously > incorrect and causes older stack versions to inherit newer properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[ https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19228: Status: Patch Available (was: In Progress) > Knox doesn't redirect to Atlas after entering correct credentials, when Atlas > is setup with Knox-SSO > > > Key: AMBARI-19228 > URL: https://issues.apache.org/jira/browse/AMBARI-19228 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19228.patch > > > After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands > back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Status: Patch Available (was: In Progress) > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[ https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19228: Attachment: AMBARI-19228.patch > Knox doesn't redirect to Atlas after entering correct credentials, when Atlas > is setup with Knox-SSO > > > Key: AMBARI-19228 > URL: https://issues.apache.org/jira/browse/AMBARI-19228 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19228.patch > > > After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands > back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755574#comment-15755574 ] Hudson commented on AMBARI-19201: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #547 (See [https://builds.apache.org/job/Ambari-branch-2.5/547/]) AMBARI-19201. Log size of status command queue size on Ambari agent (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5e9d42cd9ffb92c884935ea4fa75476c40c84f43]) * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Component/s: ambari-server > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type
[
https://issues.apache.org/jira/browse/AMBARI-19225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755564#comment-15755564
]
Hadoop QA commented on AMBARI-19225:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843615/AMBARI-19225.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9710//console
This message is automatically generated.
> Ambari server should prints error messages to its log if it can't find
> property for given property attribute type
> -
>
> Key: AMBARI-19225
> URL: https://issues.apache.org/jira/browse/AMBARI-19225
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19225.patch
>
>
> Ambari server should prints error messages to its log if it can't find
> property for given property attribute type, such as NOT_MANAGED_HDFS_PATH
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5
[
https://issues.apache.org/jira/browse/AMBARI-19229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1570#comment-1570
]
Hadoop QA commented on AMBARI-19229:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843647/AMBARI-19229.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9708//console
This message is automatically generated.
> Remove HDP-3.0.0 stack definition from Ambari-2.5
> -
>
> Key: AMBARI-19229
> URL: https://issues.apache.org/jira/browse/AMBARI-19229
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19229.patch
>
>
> Now that we are targeting Ambari-3.0.0 for HDP-3.0.0 stack, there is no need
> for the stack definition to be in the 2.5 branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.
[
https://issues.apache.org/jira/browse/AMBARI-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1573#comment-1573
]
Hadoop QA commented on AMBARI-19226:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843625/AMBARI-19226.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9709//console
This message is automatically generated.
> Provide default value for hdfs_tmp_dir parameter in HDFS params script.
> ---
>
> Key: AMBARI-19226
> URL: https://issues.apache.org/jira/browse/AMBARI-19226
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19226.patch
>
>
> provide a default value in params.py for hdfs_tmp_dir. The property is not
> shown on the UI, making it difficult for users to change its value via Ambari
> web UI if the cluster is deployed via blueprint and the property is missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755527#comment-15755527 ] Hudson commented on AMBARI-19201: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6251 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6251/]) AMBARI-19201. Log size of status command queue size on Ambari agent (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fd1ff56afba1cb84367947c7440371464ff594a5]) * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19219) Add a Maven Target for ambari-server Which Updates the Configuration Markdown
[
https://issues.apache.org/jira/browse/AMBARI-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755486#comment-15755486
]
Hudson commented on AMBARI-19219:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #546 (See
[https://builds.apache.org/job/Ambari-branch-2.5/546/])
AMBARI-19219 - Add a Maven Target for ambari-server Which Updates the (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ae3a539054fc20abbb223542fd24c1fea1cb2f85])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (add)
ambari-server/src/main/resources/org/apache/ambari/server/configuration/index_template.md
* (edit) ambari-server/pom.xml
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/configuration/index_template.md
> Add a Maven Target for ambari-server Which Updates the Configuration Markdown
> -
>
> Key: AMBARI-19219
> URL: https://issues.apache.org/jira/browse/AMBARI-19219
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-19219.patch
>
>
> The {{Configuration}} class contains some advanced annotations and logic for
> generated a markdown file which is used to define all of the configuration
> properties along with their defaults.
> See:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/configuration/index.md
> Although this is just a matter of invoking the {{main}} method of
> {{Configuration}}, when not using an IDE, this can be a difficult task due to
> dependencies on the classpath. It would be better if we added a new target to
> the {{ambari-server}} {{pom.xml}} so that a simple build command could do
> this work for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5
[ https://issues.apache.org/jira/browse/AMBARI-19229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19229: - Attachment: AMBARI-19229.patch > Remove HDP-3.0.0 stack definition from Ambari-2.5 > - > > Key: AMBARI-19229 > URL: https://issues.apache.org/jira/browse/AMBARI-19229 > Project: Ambari > Issue Type: Task > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19229.patch > > > Now that we are targeting Ambari-3.0.0 for HDP-3.0.0 stack, there is no need > for the stack definition to be in the 2.5 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5
[ https://issues.apache.org/jira/browse/AMBARI-19229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19229: - Status: Patch Available (was: Open) > Remove HDP-3.0.0 stack definition from Ambari-2.5 > - > > Key: AMBARI-19229 > URL: https://issues.apache.org/jira/browse/AMBARI-19229 > Project: Ambari > Issue Type: Task > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19229.patch > > > Now that we are targeting Ambari-3.0.0 for HDP-3.0.0 stack, there is no need > for the stack definition to be in the 2.5 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19201: Resolution: Fixed Status: Resolved (was: Patch Available) > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755480#comment-15755480 ] Sandor Magyari commented on AMBARI-19201: - Committed to trunk & branch-2.5. > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5
Alejandro Fernandez created AMBARI-19229: Summary: Remove HDP-3.0.0 stack definition from Ambari-2.5 Key: AMBARI-19229 URL: https://issues.apache.org/jira/browse/AMBARI-19229 Project: Ambari Issue Type: Task Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Now that we are targeting Ambari-3.0.0 for HDP-3.0.0 stack, there is no need for the stack definition to be in the 2.5 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19219) Add a Maven Target for ambari-server Which Updates the Configuration Markdown
[
https://issues.apache.org/jira/browse/AMBARI-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755459#comment-15755459
]
Hudson commented on AMBARI-19219:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6250 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6250/])
AMBARI-19219 - Add a Maven Target for ambari-server Which Updates the (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=44e60728fe74ce80026eb96a220172f4488d203a])
* (edit) ambari-server/pom.xml
* (add)
ambari-server/src/main/resources/org/apache/ambari/server/configuration/index_template.md
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/configuration/index_template.md
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
> Add a Maven Target for ambari-server Which Updates the Configuration Markdown
> -
>
> Key: AMBARI-19219
> URL: https://issues.apache.org/jira/browse/AMBARI-19219
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-19219.patch
>
>
> The {{Configuration}} class contains some advanced annotations and logic for
> generated a markdown file which is used to define all of the configuration
> properties along with their defaults.
> See:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/configuration/index.md
> Although this is just a matter of invoking the {{main}} method of
> {{Configuration}}, when not using an IDE, this can be a difficult task due to
> dependencies on the classpath. It would be better if we added a new target to
> the {{ambari-server}} {{pom.xml}} so that a simple build command could do
> this work for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755460#comment-15755460 ] Hudson commented on AMBARI-19220: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6250 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6250/]) AMBARI-19220. Fix version of HDFS and YARN used by HDP 3.0 (alejandro) (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ab4b864c4e3278e1c154bd294b993a7594255e5a]) * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-policymgr-ssl.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/alerts/alert_nodemanagers_summary.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/templates/hdfs.conf.j2 * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/hdfs-command.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/balancer-emulator/hdfs-command.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/templates/exclude_hosts_list.j2 * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/balancer-emulator/balancer.log * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/kerberos.json * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-metrics2.properties.xml * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/journalnode_upgrade.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/templates/exclude_hosts_list.j2 * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/themes-mapred/theme.json * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/widgets.json * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/quicklinks/quicklinks.json * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_datanode.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/YARN_metrics.json * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/alerts/alert_nodemanager_health.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/alerts/alert_datanode_unmounted_data_dir.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_windows.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/templates/yarn.conf.j2 * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_snamenode.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/alerts/alert_upgrade_finalized.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/journalnode.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/themes/theme.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/setup_ranger_hdfs.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/ranger-hdfs-audit.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/nfsgateway.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/alerts/alert_checkpoint_time.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/yarn_client.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/files/checkWebUI.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/ranger-hdfs-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/files/validateYarnComponentStatusWindows.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-policymgr-ssl.xml * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/service.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/status_params.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/ssl-client.xml * (add)
[jira] [Created] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
Vishal Suvagia created AMBARI-19228: --- Summary: Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO Key: AMBARI-19228 URL: https://issues.apache.org/jira/browse/AMBARI-19228 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Attachment: AMBARI-19227.patch > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
Vishal Suvagia created AMBARI-19227: --- Summary: Provide support to show Ranger solr-configs in Ambari Key: AMBARI-19227 URL: https://issues.apache.org/jira/browse/AMBARI-19227 Project: Ambari Issue Type: Improvement Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to provide feature for Ranger and update Ambari stacks to show solrconfig.xml on Ambari, so that user can update solr related configs directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755329#comment-15755329 ] Hudson commented on AMBARI-19220: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #545 (See [https://builds.apache.org/job/Ambari-branch-2.5/545/]) AMBARI-19220. Fix version of HDFS and YARN used by HDP 3.0 (alejandro) (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7df6bba4411a304f5750de4a0947f5d6d53833d6]) * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration-mapred/mapred-logsearch-conf.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metainfo.xml * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/namenode_upgrade.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/zkfc_slave.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/templates/mapreduce.conf.j2 * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/yarn_client.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_snamenode.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-policy.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/templates/exclude_hosts_list.j2 * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/templates/container-executor.cfg.j2 * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/params_linux.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/application_timeline_server.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/ssl-client.xml * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/metainfo.xml * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_client.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/templates/slaves.j2 * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/files/checkWebUI.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/journalnode_upgrade.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/zkfc_slave.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-security.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_nfsgateway.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_rebalance.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-metrics2.properties.xml * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/MAPREDUCE2_metrics.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/alerts.json * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hdfs-site.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_windows.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/setup_ranger_yarn.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/datanode.py * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/alerts.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/yarn-env.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/hdfs-log4j.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metrics.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/quicklinks/quicklinks.json * (delete) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration-mapred/mapred-logsearch-conf.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/alerts/alert_nodemanager_health.py * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/quicklinks/quicklinks.json * (delete) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/__init__.py * (delete)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[ https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755299#comment-15755299 ] Hudson commented on AMBARI-19149: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6249 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6249/]) AMBARI-19149. Code cleanup: compiler warnings (Attila Doroszlai via (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=edce0b1173b6629e50b053be140490fa288ec361]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog212Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog211Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/AmbariJpaLocalTxnInterceptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsRequestHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/scheduler/ExecutionScheduleManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/AsyncCallableService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/MITKerberosOperationHandlerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/notifications/dispatchers/SNMPDispatcherTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog221.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/collections/functors/ContainsPredicateTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/utils/Parallel.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/WidgetLayoutResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/WidgetResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ConfigureClusterTaskTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/UtilsTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatProcessorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RootServiceHostComponentResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackModuleTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalServiceTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ExtensionLinkResponse.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AmbariPrivilegeResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/view/RemoteAmbariClusterTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/StateRecoveryManagerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AsyncCallableServiceTest.java * (edit)
[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19097: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for HDFS > > > Key: AMBARI-19097 > URL: https://issues.apache.org/jira/browse/AMBARI-19097 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[
https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19137:
-
Fix Version/s: (was: 2.5.0)
3.0.0
> HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
>
>
> Key: AMBARI-19137
> URL: https://issues.apache.org/jira/browse/AMBARI-19137
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19137.patch
>
>
> Create new versions in common-services for ZK, HDFS, YARN/MR and inherit from
> them in HDP 3.0 TP
> common-services is allowed to define
> * kerberos.json
> * widgets
> * themes
> * configs
> Create new version in common services
> ZK: 3.4.9, inherit from ZK 3.4.6 in common services
> HDFS: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor from
> the previous version in common-services and combine with the flattened files
> from HDP 2.0.6 through HDP 2.6
> YARN/MR: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor
> from the previous version in common-services and combine with the flattened
> files from HDP 2.0.6 through HDP 2.6
> Finally, any configs with references to /usr/hdp must be replaced by
> {{stack_root}, and configs that use ${hdp.version} must be overriden by the
> HDP 3.0 stack and kept clean in the version used by common-services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[
https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19137:
-
Affects Version/s: (was: 2.5.0)
3.0.0
> HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
>
>
> Key: AMBARI-19137
> URL: https://issues.apache.org/jira/browse/AMBARI-19137
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19137.patch
>
>
> Create new versions in common-services for ZK, HDFS, YARN/MR and inherit from
> them in HDP 3.0 TP
> common-services is allowed to define
> * kerberos.json
> * widgets
> * themes
> * configs
> Create new version in common services
> ZK: 3.4.9, inherit from ZK 3.4.6 in common services
> HDFS: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor from
> the previous version in common-services and combine with the flattened files
> from HDP 2.0.6 through HDP 2.6
> YARN/MR: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor
> from the previous version in common-services and combine with the flattened
> files from HDP 2.0.6 through HDP 2.6
> Finally, any configs with references to /usr/hdp must be replaced by
> {{stack_root}, and configs that use ${hdp.version} must be overriden by the
> HDP 3.0 stack and kept clean in the version used by common-services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19097: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for HDFS > > > Key: AMBARI-19097 > URL: https://issues.apache.org/jira/browse/AMBARI-19097 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK
[ https://issues.apache.org/jira/browse/AMBARI-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19096: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for ZK > -- > > Key: AMBARI-19096 > URL: https://issues.apache.org/jira/browse/AMBARI-19096 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for ZK in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK
[ https://issues.apache.org/jira/browse/AMBARI-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19096: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for ZK > -- > > Key: AMBARI-19096 > URL: https://issues.apache.org/jira/browse/AMBARI-19096 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for ZK in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19095) HDP 3.0 flatten Role Command Order and update service versions in metainfo.xml
[ https://issues.apache.org/jira/browse/AMBARI-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19095: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 flatten Role Command Order and update service versions in > metainfo.xml > --- > > Key: AMBARI-19095 > URL: https://issues.apache.org/jira/browse/AMBARI-19095 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Flatten out Role Command Order for HDP 3.0 TP based on previous stacks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19094: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19093: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, > quicklinks, and themes > - > > Key: AMBARI-19093 > URL: https://issues.apache.org/jira/browse/AMBARI-19093 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19093.patch > > > New service definition for HDFS in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19094: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19095) HDP 3.0 flatten Role Command Order and update service versions in metainfo.xml
[ https://issues.apache.org/jira/browse/AMBARI-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19095: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 flatten Role Command Order and update service versions in > metainfo.xml > --- > > Key: AMBARI-19095 > URL: https://issues.apache.org/jira/browse/AMBARI-19095 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Flatten out Role Command Order for HDP 3.0 TP based on previous stacks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19093: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, > quicklinks, and themes > - > > Key: AMBARI-19093 > URL: https://issues.apache.org/jira/browse/AMBARI-19093 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19093.patch > > > New service definition for HDFS in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19092) HDP 3.0 support for ZK with metainfo
[ https://issues.apache.org/jira/browse/AMBARI-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19092: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 support for ZK with metainfo > > > Key: AMBARI-19092 > URL: https://issues.apache.org/jira/browse/AMBARI-19092 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19092.patch > > > New service definition for ZK in HDP 3.0 TP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19091: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > * metainfo > * configs in cluster-env > * repositories > * hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19090) HDP 3.0 Tech Preview in Ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19090: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 Tech Preview in Ambari 2.5 > -- > > Key: AMBARI-19090 > URL: https://issues.apache.org/jira/browse/AMBARI-19090 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > HDP 3.0 Tech Preview for Ambari 2.5 in January > Services: HDFS, YARN, MR, ZK > Plan: > # HDP 3.0 bits for Hadoop core > # New stack definition in Ambari > # Flatten configs, metrics, widgets, kerberos for the services listed above > # Break up Stack Advisor into Service Advisor per service listed above > # Testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19091: - Fix Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > * metainfo > * configs in cluster-env > * repositories > * hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19090) HDP 3.0 Tech Preview in Ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19090: - Affects Version/s: (was: 2.5.0) 3.0.0 > HDP 3.0 Tech Preview in Ambari 2.5 > -- > > Key: AMBARI-19090 > URL: https://issues.apache.org/jira/browse/AMBARI-19090 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > HDP 3.0 Tech Preview for Ambari 2.5 in January > Services: HDFS, YARN, MR, ZK > Plan: > # HDP 3.0 bits for Hadoop core > # New stack definition in Ambari > # Flatten configs, metrics, widgets, kerberos for the services listed above > # Break up Stack Advisor into Service Advisor per service listed above > # Testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19219) Add a Maven Target for ambari-server Which Updates the Configuration Markdown
[
https://issues.apache.org/jira/browse/AMBARI-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19219:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add a Maven Target for ambari-server Which Updates the Configuration Markdown
> -
>
> Key: AMBARI-19219
> URL: https://issues.apache.org/jira/browse/AMBARI-19219
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-19219.patch
>
>
> The {{Configuration}} class contains some advanced annotations and logic for
> generated a markdown file which is used to define all of the configuration
> properties along with their defaults.
> See:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/configuration/index.md
> Although this is just a matter of invoking the {{main}} method of
> {{Configuration}}, when not using an IDE, this can be a difficult task due to
> dependencies on the classpath. It would be better if we added a new target to
> the {{ambari-server}} {{pom.xml}} so that a simple build command could do
> this work for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19220) Fix version of HDFS and YARN used by HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19220: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit ab4b864c4e3278e1c154bd294b993a7594255e5a branch-2.5, commit 7df6bba4411a304f5750de4a0947f5d6d53833d6 > Fix version of HDFS and YARN used by HDP 3.0 > > > Key: AMBARI-19220 > URL: https://issues.apache.org/jira/browse/AMBARI-19220 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19220.patch > > > HDP 3.0 is set to use HDFS and YARN from the versions in common services. > HDFS will use 3.0.0.3.0 > YARN will ise 3.0.0.3.0 > Right now there's a bug in that the metainfo.xml file for the new YARN in > common services has its version set to 2.1.0.2.0, which is obviously > incorrect and causes older stack versions to inherit newer properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.
Di Li created AMBARI-19226: -- Summary: Provide default value for hdfs_tmp_dir parameter in HDFS params script. Key: AMBARI-19226 URL: https://issues.apache.org/jira/browse/AMBARI-19226 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Priority: Minor provide a default value in params.py for hdfs_tmp_dir. The property is not shown on the UI, making it difficult for users to change its value via Ambari web UI if the cluster is deployed via blueprint and the property is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.
[ https://issues.apache.org/jira/browse/AMBARI-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19226: --- Status: Patch Available (was: Open) > Provide default value for hdfs_tmp_dir parameter in HDFS params script. > --- > > Key: AMBARI-19226 > URL: https://issues.apache.org/jira/browse/AMBARI-19226 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19226.patch > > > provide a default value in params.py for hdfs_tmp_dir. The property is not > shown on the UI, making it difficult for users to change its value via Ambari > web UI if the cluster is deployed via blueprint and the property is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.
[ https://issues.apache.org/jira/browse/AMBARI-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19226: --- Attachment: AMBARI-19226.patch > Provide default value for hdfs_tmp_dir parameter in HDFS params script. > --- > > Key: AMBARI-19226 > URL: https://issues.apache.org/jira/browse/AMBARI-19226 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19226.patch > > > provide a default value in params.py for hdfs_tmp_dir. The property is not > shown on the UI, making it difficult for users to change its value via Ambari > web UI if the cluster is deployed via blueprint and the property is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
[
https://issues.apache.org/jira/browse/AMBARI-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754989#comment-15754989
]
Hadoop QA commented on AMBARI-19218:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843604/AMBARI-19218_1216.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/slider.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9707//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9707//console
This message is automatically generated.
> Exception when running Slider view - java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645 WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1]
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type
[ https://issues.apache.org/jira/browse/AMBARI-19225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19225: --- Status: Patch Available (was: Open) > Ambari server should prints error messages to its log if it can't find > property for given property attribute type > - > > Key: AMBARI-19225 > URL: https://issues.apache.org/jira/browse/AMBARI-19225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19225.patch > > > Ambari server should prints error messages to its log if it can't find > property for given property attribute type, such as NOT_MANAGED_HDFS_PATH -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type
[ https://issues.apache.org/jira/browse/AMBARI-19225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19225: --- Attachment: AMBARI-19225.patch > Ambari server should prints error messages to its log if it can't find > property for given property attribute type > - > > Key: AMBARI-19225 > URL: https://issues.apache.org/jira/browse/AMBARI-19225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19225.patch > > > Ambari server should prints error messages to its log if it can't find > property for given property attribute type, such as NOT_MANAGED_HDFS_PATH -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type
Di Li created AMBARI-19225: -- Summary: Ambari server should prints error messages to its log if it can't find property for given property attribute type Key: AMBARI-19225 URL: https://issues.apache.org/jira/browse/AMBARI-19225 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Ambari server should prints error messages to its log if it can't find property for given property attribute type, such as NOT_MANAGED_HDFS_PATH -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19222) %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
[
https://issues.apache.org/jira/browse/AMBARI-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754911#comment-15754911
]
Hadoop QA commented on AMBARI-19222:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843584/AMBARI-19222_branch-2.5-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9706//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9706//console
This message is automatically generated.
> %livy interpreter gives 400 HttpClientError due to spark.master property
> present in livy-spark-blacklist
>
>
> Key: AMBARI-19222
> URL: https://issues.apache.org/jira/browse/AMBARI-19222
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Prabhjyot Singh
> Fix For: 2.5.0
>
> Attachments: AMBARI-19222_branch-2.5-v1.patch
>
>
> spark.master should not be overridden because we want to use livy's own
> default = cluster not overridden by the user via zeppelin. so it should be
> present in the blacklist if I understand right. zeppelin should stop
> specifying livy.spark.master in the livy interpreter in case it does so now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754858#comment-15754858 ] Tuong Truong commented on AMBARI-17666: --- Awesome.. Thanks for fixing this issue Doroszlai. > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19201) Log size of status command queue size on Ambari agent
[
https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754832#comment-15754832
]
Hadoop QA commented on AMBARI-19201:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843588/AMBARI-19201_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9705//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9705//console
This message is automatically generated.
> Log size of status command queue size on Ambari agent
> -
>
> Key: AMBARI-19201
> URL: https://issues.apache.org/jira/browse/AMBARI-19201
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch
>
>
> Before adding new status commands to agent statusCommandQueue, we delete old
> ones. Sometimes status command execution may take too long therefore would be
> useful to log statusCommandQueue size before emptying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754757#comment-15754757
]
Hadoop QA commented on AMBARI-19149:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843595/AMBARI-19149-4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 93 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9704//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9704//console
This message is automatically generated.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, AMBARI-19149-3.patch,
> AMBARI-19149-4.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754731#comment-15754731 ] Hudson commented on AMBARI-17666: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #544 (See [https://builds.apache.org/job/Ambari-branch-2.5/544/]) AMBARI-17666. Fix python test error: cannot import name (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed353f0a0bd8838f2be8ad5b6629068ed544e428]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/utils.py > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754720#comment-15754720 ] Hudson commented on AMBARI-17666: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6248 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6248/]) AMBARI-17666. Fix python test error: cannot import name (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a5b2f6f5ad2315339ca4ccf26099968b76b16b9]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/utils.py > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
[
https://issues.apache.org/jira/browse/AMBARI-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19218:
Status: Open (was: Patch Available)
> Exception when running Slider view - java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645 WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1]
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
[
https://issues.apache.org/jira/browse/AMBARI-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19218:
Status: Patch Available (was: Open)
> Exception when running Slider view - java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645 WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1]
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
[
https://issues.apache.org/jira/browse/AMBARI-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19218:
Attachment: AMBARI-19218_1216.patch
> Exception when running Slider view - java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645 WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1]
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
[
https://issues.apache.org/jira/browse/AMBARI-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19218:
Attachment: (was: AMBARI-19218.patch)
> Exception when running Slider view - java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645 WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1]
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[
https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754632#comment-15754632
]
Hadoop QA commented on AMBARI-17666:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843598/AMBARI-17666_test_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9703//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9703//console
This message is automatically generated.
> Ambari agent can't start when TLSv1 is disabled in Java security
>
>
> Key: AMBARI-17666
> URL: https://issues.apache.org/jira/browse/AMBARI-17666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
>Reporter: Tuong Truong
>Assignee: Dmitry Lysnichenko
> Labels: security
> Fix For: 2.5.0
>
> Attachments: AMBARI-17666_test_trunk.patch
>
>
> Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236
> explicit force the SSL protocol to TLSv1 in
> ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate,
> this setting in effect whenever web_alert pacackged is loaded
> (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py)
> regardless whether ssl is used or not.
> As a result, disabling TLSv1 in Ambari server will cause the agent to fail to
> start.
> Recreate:
> In Ambari's acitve JDK on Ambari server node, in java.security file, set
> jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize <
> 2048
> restart ambari-server, and you will see errors in ambari agent logs:
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF
> occurred in violation of protocol
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect.
> Please check openssl library versions.
> Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more
> details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
[
https://issues.apache.org/jira/browse/AMBARI-19224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754627#comment-15754627
]
Hudson commented on AMBARI-19224:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #543 (See
[https://builds.apache.org/job/Ambari-branch-2.5/543/])
AMBARI-19224. Perf: Host Checks response is way too big (320MB for 1200
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cba0c04af7b1c737ad056d17f23d6375129b9049])
* (edit) ambari-server/src/main/resources/custom_actions/scripts/check_host.py
* (edit) ambari-server/src/test/python/custom_actions/TestCheckHost.py
> Perf: Host Checks response is way too big (320MB for 1200 nodes)
>
>
> Key: AMBARI-19224
> URL: https://issues.apache.org/jira/browse/AMBARI-19224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19224.patch
>
>
> Currently, parsing of Host Checks after registration happens on UI, and on
> 1200 nodes it grows to 320mb of data, which hard to download and then parse.
> We can move parsing and aggregating data on the server, so on UI we will
> receive only required info.
> Request URL:
> {noformat}
>
> /api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
> {noformat}
> Part of response:
> {code:java}
> "tasks" : [
> {
> "href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
> "Tasks" : {
> "attempt_cnt" : 1,
> "command" : "ACTIONEXECUTE",
> "command_detail" : "check_host ACTIONEXECUTE",
> "end_time" : 1481047483941,
> "error_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
> "exit_code" : 0,
> "host_name" : "testvbrodetskyi-0001",
> "id" : 31414,
> "output_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
> "request_id" : 24,
> "role" : "check_host",
> "stage_id" : 0,
> "start_time" : 1481047457478,
> "status" : "COMPLETED",
> "stderr" : "None",
> "stdout" : "2016-12-06 18:04:25,626 - Host checks
> started.\n2016-12-06 18:04:25,626 - Check execute list:
> host_resolution_check\n2016-12-06 18:04:25,626 - IP address forward
> resolution check started.\n2016-12-06 18:04:43,192 - There were 1200 host(s)
> that could not resolve to an IP address.\n2016-12-06 18:04:43,193 - IP
> address forward resolution check completed.\n2016-12-06 18:04:43,215 - Host
> checks completed.\n\nCommand completed successfully!\n",
> "structured_out" : {
> "host_resolution_check" : {
> "exit_code" : 0,
> "failed_count" : 1200,
> "failures" : [
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0601",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> In case of 1200 for each host we have1200 objects in failures array so in
> result we have 1200x1200 objects as:
> {code:java}
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> However we on UI we parse only hosts' names, we can reduce response size by
> changing failures to just array of host_names like:
> "failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
> "testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-17666: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754598#comment-15754598 ] Dmitry Lysnichenko commented on AMBARI-17666: - [~adoroszlai], Thanks for fixing that. To https://git-wip-us.apache.org/repos/asf/ambari.git cba0c04..ed353f0 branch-2.5 -> branch-2.5 aa16f5e..4a5b2f6 trunk -> trunk > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
[
https://issues.apache.org/jira/browse/AMBARI-19224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754568#comment-15754568
]
Hudson commented on AMBARI-19224:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6247 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6247/])
AMBARI-19224. Perf: Host Checks response is way too big (320MB for 1200
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aa16f5ed8836241e9187766b684c51ddcb5f0eeb])
* (edit) ambari-server/src/main/resources/custom_actions/scripts/check_host.py
* (edit) ambari-server/src/test/python/custom_actions/TestCheckHost.py
> Perf: Host Checks response is way too big (320MB for 1200 nodes)
>
>
> Key: AMBARI-19224
> URL: https://issues.apache.org/jira/browse/AMBARI-19224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19224.patch
>
>
> Currently, parsing of Host Checks after registration happens on UI, and on
> 1200 nodes it grows to 320mb of data, which hard to download and then parse.
> We can move parsing and aggregating data on the server, so on UI we will
> receive only required info.
> Request URL:
> {noformat}
>
> /api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
> {noformat}
> Part of response:
> {code:java}
> "tasks" : [
> {
> "href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
> "Tasks" : {
> "attempt_cnt" : 1,
> "command" : "ACTIONEXECUTE",
> "command_detail" : "check_host ACTIONEXECUTE",
> "end_time" : 1481047483941,
> "error_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
> "exit_code" : 0,
> "host_name" : "testvbrodetskyi-0001",
> "id" : 31414,
> "output_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
> "request_id" : 24,
> "role" : "check_host",
> "stage_id" : 0,
> "start_time" : 1481047457478,
> "status" : "COMPLETED",
> "stderr" : "None",
> "stdout" : "2016-12-06 18:04:25,626 - Host checks
> started.\n2016-12-06 18:04:25,626 - Check execute list:
> host_resolution_check\n2016-12-06 18:04:25,626 - IP address forward
> resolution check started.\n2016-12-06 18:04:43,192 - There were 1200 host(s)
> that could not resolve to an IP address.\n2016-12-06 18:04:43,193 - IP
> address forward resolution check completed.\n2016-12-06 18:04:43,215 - Host
> checks completed.\n\nCommand completed successfully!\n",
> "structured_out" : {
> "host_resolution_check" : {
> "exit_code" : 0,
> "failed_count" : 1200,
> "failures" : [
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0601",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> In case of 1200 for each host we have1200 objects in failures array so in
> result we have 1200x1200 objects as:
> {code:java}
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> However we on UI we parse only hosts' names, we can reduce response size by
> changing failures to just array of host_names like:
> "failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
> "testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
[
https://issues.apache.org/jira/browse/AMBARI-19224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19224:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Perf: Host Checks response is way too big (320MB for 1200 nodes)
>
>
> Key: AMBARI-19224
> URL: https://issues.apache.org/jira/browse/AMBARI-19224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19224.patch
>
>
> Currently, parsing of Host Checks after registration happens on UI, and on
> 1200 nodes it grows to 320mb of data, which hard to download and then parse.
> We can move parsing and aggregating data on the server, so on UI we will
> receive only required info.
> Request URL:
> {noformat}
>
> /api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
> {noformat}
> Part of response:
> {code:java}
> "tasks" : [
> {
> "href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
> "Tasks" : {
> "attempt_cnt" : 1,
> "command" : "ACTIONEXECUTE",
> "command_detail" : "check_host ACTIONEXECUTE",
> "end_time" : 1481047483941,
> "error_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
> "exit_code" : 0,
> "host_name" : "testvbrodetskyi-0001",
> "id" : 31414,
> "output_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
> "request_id" : 24,
> "role" : "check_host",
> "stage_id" : 0,
> "start_time" : 1481047457478,
> "status" : "COMPLETED",
> "stderr" : "None",
> "stdout" : "2016-12-06 18:04:25,626 - Host checks
> started.\n2016-12-06 18:04:25,626 - Check execute list:
> host_resolution_check\n2016-12-06 18:04:25,626 - IP address forward
> resolution check started.\n2016-12-06 18:04:43,192 - There were 1200 host(s)
> that could not resolve to an IP address.\n2016-12-06 18:04:43,193 - IP
> address forward resolution check completed.\n2016-12-06 18:04:43,215 - Host
> checks completed.\n\nCommand completed successfully!\n",
> "structured_out" : {
> "host_resolution_check" : {
> "exit_code" : 0,
> "failed_count" : 1200,
> "failures" : [
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0601",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> In case of 1200 for each host we have1200 objects in failures array so in
> result we have 1200x1200 objects as:
> {code:java}
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> However we on UI we parse only hosts' names, we can reduce response size by
> changing failures to just array of host_names like:
> "failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
> "testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-17666: --- Status: Patch Available (was: Reopened) > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > Attachments: AMBARI-17666_test_trunk.patch > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[
https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754479#comment-15754479
]
Doroszlai, Attila edited comment on AMBARI-17666 at 12/16/16 2:02 PM:
--
https://builds.apache.org/job/Ambari-trunk-Commit/6242/consoleText
{noformat}
Total run:1154
Total errors:93
Total failures:1
{noformat}
vs.
{noformat}
Total run:1154
Total errors:0
Total failures:0
{noformat}
Same patch applies to branch-2.5.
https://builds.apache.org/job/Ambari-branch-2.5/542/consoleText
{noformat}
Total run:1146
Total errors:93
Total failures:2
{noformat}
vs
{noformat}
Total run:1146
Total errors:0
Total failures:0
{noformat}
was (Author: adoroszlai):
https://builds.apache.org/job/Ambari-trunk-Commit/6242/consoleText
{noformat}
Total run:1154
Total errors:93
Total failures:1
{noformat}
vs.
{noformat}
Total run:1154
Total errors:0
Total failures:0
{noformat}
> Ambari agent can't start when TLSv1 is disabled in Java security
>
>
> Key: AMBARI-17666
> URL: https://issues.apache.org/jira/browse/AMBARI-17666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
>Reporter: Tuong Truong
>Assignee: Dmitry Lysnichenko
> Labels: security
> Fix For: 2.5.0
>
> Attachments: AMBARI-17666_test_trunk.patch
>
>
> Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236
> explicit force the SSL protocol to TLSv1 in
> ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate,
> this setting in effect whenever web_alert pacackged is loaded
> (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py)
> regardless whether ssl is used or not.
> As a result, disabling TLSv1 in Ambari server will cause the agent to fail to
> start.
> Recreate:
> In Ambari's acitve JDK on Ambari server node, in java.security file, set
> jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize <
> 2048
> restart ambari-server, and you will see errors in ambari agent logs:
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF
> occurred in violation of protocol
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect.
> Please check openssl library versions.
> Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more
> details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[
https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-17666:
---
Attachment: AMBARI-17666_test_trunk.patch
https://builds.apache.org/job/Ambari-trunk-Commit/6242/consoleText
{noformat}
Total run:1154
Total errors:93
Total failures:1
{noformat}
vs.
{noformat}
Total run:1154
Total errors:0
Total failures:0
{noformat}
> Ambari agent can't start when TLSv1 is disabled in Java security
>
>
> Key: AMBARI-17666
> URL: https://issues.apache.org/jira/browse/AMBARI-17666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
>Reporter: Tuong Truong
>Assignee: Dmitry Lysnichenko
> Labels: security
> Fix For: 2.5.0
>
> Attachments: AMBARI-17666_test_trunk.patch
>
>
> Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236
> explicit force the SSL protocol to TLSv1 in
> ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate,
> this setting in effect whenever web_alert pacackged is loaded
> (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py)
> regardless whether ssl is used or not.
> As a result, disabling TLSv1 in Ambari server will cause the agent to fail to
> start.
> Recreate:
> In Ambari's acitve JDK on Ambari server node, in java.security file, set
> jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize <
> 2048
> restart ambari-server, and you will see errors in ambari agent logs:
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF
> occurred in violation of protocol
> ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect.
> Please check openssl library versions.
> Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more
> details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
[
https://issues.apache.org/jira/browse/AMBARI-19224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19224:
---
Status: Patch Available (was: Open)
> Perf: Host Checks response is way too big (320MB for 1200 nodes)
>
>
> Key: AMBARI-19224
> URL: https://issues.apache.org/jira/browse/AMBARI-19224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19224.patch
>
>
> Currently, parsing of Host Checks after registration happens on UI, and on
> 1200 nodes it grows to 320mb of data, which hard to download and then parse.
> We can move parsing and aggregating data on the server, so on UI we will
> receive only required info.
> Request URL:
> {noformat}
>
> /api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
> {noformat}
> Part of response:
> {code:java}
> "tasks" : [
> {
> "href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
> "Tasks" : {
> "attempt_cnt" : 1,
> "command" : "ACTIONEXECUTE",
> "command_detail" : "check_host ACTIONEXECUTE",
> "end_time" : 1481047483941,
> "error_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
> "exit_code" : 0,
> "host_name" : "testvbrodetskyi-0001",
> "id" : 31414,
> "output_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
> "request_id" : 24,
> "role" : "check_host",
> "stage_id" : 0,
> "start_time" : 1481047457478,
> "status" : "COMPLETED",
> "stderr" : "None",
> "stdout" : "2016-12-06 18:04:25,626 - Host checks
> started.\n2016-12-06 18:04:25,626 - Check execute list:
> host_resolution_check\n2016-12-06 18:04:25,626 - IP address forward
> resolution check started.\n2016-12-06 18:04:43,192 - There were 1200 host(s)
> that could not resolve to an IP address.\n2016-12-06 18:04:43,193 - IP
> address forward resolution check completed.\n2016-12-06 18:04:43,215 - Host
> checks completed.\n\nCommand completed successfully!\n",
> "structured_out" : {
> "host_resolution_check" : {
> "exit_code" : 0,
> "failed_count" : 1200,
> "failures" : [
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0601",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> In case of 1200 for each host we have1200 objects in failures array so in
> result we have 1200x1200 objects as:
> {code:java}
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> However we on UI we parse only hosts' names, we can reduce response size by
> changing failures to just array of host_names like:
> "failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
> "testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
[
https://issues.apache.org/jira/browse/AMBARI-19224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19224:
---
Attachment: AMBARI-19224.patch
> Perf: Host Checks response is way too big (320MB for 1200 nodes)
>
>
> Key: AMBARI-19224
> URL: https://issues.apache.org/jira/browse/AMBARI-19224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19224.patch
>
>
> Currently, parsing of Host Checks after registration happens on UI, and on
> 1200 nodes it grows to 320mb of data, which hard to download and then parse.
> We can move parsing and aggregating data on the server, so on UI we will
> receive only required info.
> Request URL:
> {noformat}
>
> /api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
> {noformat}
> Part of response:
> {code:java}
> "tasks" : [
> {
> "href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
> "Tasks" : {
> "attempt_cnt" : 1,
> "command" : "ACTIONEXECUTE",
> "command_detail" : "check_host ACTIONEXECUTE",
> "end_time" : 1481047483941,
> "error_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
> "exit_code" : 0,
> "host_name" : "testvbrodetskyi-0001",
> "id" : 31414,
> "output_log" :
> "/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
> "request_id" : 24,
> "role" : "check_host",
> "stage_id" : 0,
> "start_time" : 1481047457478,
> "status" : "COMPLETED",
> "stderr" : "None",
> "stdout" : "2016-12-06 18:04:25,626 - Host checks
> started.\n2016-12-06 18:04:25,626 - Check execute list:
> host_resolution_check\n2016-12-06 18:04:25,626 - IP address forward
> resolution check started.\n2016-12-06 18:04:43,192 - There were 1200 host(s)
> that could not resolve to an IP address.\n2016-12-06 18:04:43,193 - IP
> address forward resolution check completed.\n2016-12-06 18:04:43,215 - Host
> checks completed.\n\nCommand completed successfully!\n",
> "structured_out" : {
> "host_resolution_check" : {
> "exit_code" : 0,
> "failed_count" : 1200,
> "failures" : [
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0601",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> In case of 1200 for each host we have1200 objects in failures array so in
> result we have 1200x1200 objects as:
> {code:java}
> {
> "type" : "FORWARD_LOOKUP",
> "host" : "testvbrodetskyi-0602",
> "cause" : [
> -2,
> "Name or service not known"
> ]
> },
> {code}
> However we on UI we parse only hosts' names, we can reduce response size by
> changing failures to just array of host_names like:
> "failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
> "testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19224) Perf: Host Checks response is way too big (320MB for 1200 nodes)
Vitaly Brodetskyi created AMBARI-19224:
--
Summary: Perf: Host Checks response is way too big (320MB for 1200
nodes)
Key: AMBARI-19224
URL: https://issues.apache.org/jira/browse/AMBARI-19224
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.5.0
Currently, parsing of Host Checks after registration happens on UI, and on 1200
nodes it grows to 320mb of data, which hard to download and then parse. We can
move parsing and aggregating data on the server, so on UI we will receive only
required info.
Request URL:
{noformat}
/api/v1/requests/24?fields=tasks/Tasks,Requests/inputs,Requests/request_status
{noformat}
Part of response:
{code:java}
"tasks" : [
{
"href" : "http://104.196.95.1:8080/api/v1/requests/24/tasks/31414;,
"Tasks" : {
"attempt_cnt" : 1,
"command" : "ACTIONEXECUTE",
"command_detail" : "check_host ACTIONEXECUTE",
"end_time" : 1481047483941,
"error_log" :
"/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/errors-31414.txt",
"exit_code" : 0,
"host_name" : "testvbrodetskyi-0001",
"id" : 31414,
"output_log" :
"/home/testvbrodetskyi-0001/var/lib/ambari-agent/data/output-31414.txt",
"request_id" : 24,
"role" : "check_host",
"stage_id" : 0,
"start_time" : 1481047457478,
"status" : "COMPLETED",
"stderr" : "None",
"stdout" : "2016-12-06 18:04:25,626 - Host checks started.\n2016-12-06
18:04:25,626 - Check execute list: host_resolution_check\n2016-12-06
18:04:25,626 - IP address forward resolution check started.\n2016-12-06
18:04:43,192 - There were 1200 host(s) that could not resolve to an IP
address.\n2016-12-06 18:04:43,193 - IP address forward resolution check
completed.\n2016-12-06 18:04:43,215 - Host checks completed.\n\nCommand
completed successfully!\n",
"structured_out" : {
"host_resolution_check" : {
"exit_code" : 0,
"failed_count" : 1200,
"failures" : [
{
"type" : "FORWARD_LOOKUP",
"host" : "testvbrodetskyi-0601",
"cause" : [
-2,
"Name or service not known"
]
},
{
"type" : "FORWARD_LOOKUP",
"host" : "testvbrodetskyi-0602",
"cause" : [
-2,
"Name or service not known"
]
},
{code}
In case of 1200 for each host we have1200 objects in failures array so in
result we have 1200x1200 objects as:
{code:java}
{
"type" : "FORWARD_LOOKUP",
"host" : "testvbrodetskyi-0602",
"cause" : [
-2,
"Name or service not known"
]
},
{code}
However we on UI we parse only hosts' names, we can reduce response size by
changing failures to just array of host_names like:
"failures" : ["testvbrodetskyi-0602", "testvbrodetskyi-0603",
"testvbrodetskyi-0604", ...]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: AMBARI-19149-4.patch
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, AMBARI-19149-3.patch,
> AMBARI-19149-4.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19201: Attachment: AMBARI-19201_v2.patch > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19201: Attachment: (was: AMBARI-19201_v2.patch) > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19223) Zeppelin service start "No such file or directory"
Gonzalo Herreros created AMBARI-19223: - Summary: Zeppelin service start "No such file or directory" Key: AMBARI-19223 URL: https://issues.apache.org/jira/browse/AMBARI-19223 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.2 Reporter: Gonzalo Herreros Normally the /var/run directory is on a temporary filesystem and thus wiped on restart. Ambari service scripts ensure the corresponding run directory like /var/run/zeppelin exists on start. However for zeppelin the run directory is only created in install, therefore start no longer works correctly and you get a "No such file or directory" when Ambari tries to store the pid after reboot. In this file the block "# create the pid and zeppelin dirs" should be moved into the create_zeppelin_dir which is called from start https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19222) %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
[ https://issues.apache.org/jira/browse/AMBARI-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19222: - Attachment: AMBARI-19222_branch-2.5-v1.patch > %livy interpreter gives 400 HttpClientError due to spark.master property > present in livy-spark-blacklist > > > Key: AMBARI-19222 > URL: https://issues.apache.org/jira/browse/AMBARI-19222 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19222_branch-2.5-v1.patch > > > spark.master should not be overridden because we want to use livy's own > default = cluster not overridden by the user via zeppelin. so it should be > present in the blacklist if I understand right. zeppelin should stop > specifying livy.spark.master in the livy interpreter in case it does so now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19222) %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
[ https://issues.apache.org/jira/browse/AMBARI-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19222: - Status: Patch Available (was: Open) > %livy interpreter gives 400 HttpClientError due to spark.master property > present in livy-spark-blacklist > > > Key: AMBARI-19222 > URL: https://issues.apache.org/jira/browse/AMBARI-19222 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19222_branch-2.5-v1.patch > > > spark.master should not be overridden because we want to use livy's own > default = cluster not overridden by the user via zeppelin. so it should be > present in the blacklist if I understand right. zeppelin should stop > specifying livy.spark.master in the livy interpreter in case it does so now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19215) Integrate karma with babel preprocessor
[ https://issues.apache.org/jira/browse/AMBARI-19215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754128#comment-15754128 ] Hudson commented on AMBARI-19215: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6246 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6246/]) AMBARI-19215 Integrate karma with babel preprocessor. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=791a24cda09a2fb97e2a36fbb9653c6f9b487ec1]) * (edit) ambari-web/karma.conf.js * (edit) ambari-web/package.json > Integrate karma with babel preprocessor > --- > > Key: AMBARI-19215 > URL: https://issues.apache.org/jira/browse/AMBARI-19215 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19215.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19222) %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
Prabhjyot Singh created AMBARI-19222: Summary: %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist Key: AMBARI-19222 URL: https://issues.apache.org/jira/browse/AMBARI-19222 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Prabhjyot Singh Fix For: 2.5.0 spark.master should not be overridden because we want to use livy's own default = cluster not overridden by the user via zeppelin. so it should be present in the blacklist if I understand right. zeppelin should stop specifying livy.spark.master in the livy interpreter in case it does so now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19201) Log size of status command queue size on Ambari agent
[
https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754114#comment-15754114
]
Hadoop QA commented on AMBARI-19201:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843575/AMBARI-19201_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9702//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9702//console
This message is automatically generated.
> Log size of status command queue size on Ambari agent
> -
>
> Key: AMBARI-19201
> URL: https://issues.apache.org/jira/browse/AMBARI-19201
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch
>
>
> Before adding new status commands to agent statusCommandQueue, we delete old
> ones. Sometimes status command execution may take too long therefore would be
> useful to log statusCommandQueue size before emptying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19221) Preview xml feature is not functional across different tabs
[ https://issues.apache.org/jira/browse/AMBARI-19221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19221: - Attachment: AMBARI-19221_trunk.patch > Preview xml feature is not functional across different tabs > --- > > Key: AMBARI-19221 > URL: https://issues.apache.org/jira/browse/AMBARI-19221 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Belliraj HB > Fix For: 2.5.0 > > Attachments: AMBARI-19221_trunk.patch > > > Preview xml feature is not functional across different tabs.UI hangs when > user tries to view preview workflow from two different tabs. > Steps to reproduce : > 1) Create a workflow and check preview is happening correctly. > 2) Open new tab and create another workflow > 3) UI hangs when user tries to preview. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19215) Integrate karma with babel preprocessor
[ https://issues.apache.org/jira/browse/AMBARI-19215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19215: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Integrate karma with babel preprocessor > --- > > Key: AMBARI-19215 > URL: https://issues.apache.org/jira/browse/AMBARI-19215 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19215.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19215) Integrate karma with babel preprocessor
[ https://issues.apache.org/jira/browse/AMBARI-19215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754066#comment-15754066 ] Andrii Tkach commented on AMBARI-19215: --- committed to trunk > Integrate karma with babel preprocessor > --- > > Key: AMBARI-19215 > URL: https://issues.apache.org/jira/browse/AMBARI-19215 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19215.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19221) Preview xml feature is not functional across different tabs
[ https://issues.apache.org/jira/browse/AMBARI-19221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19221: - Assignee: Belliraj HB > Preview xml feature is not functional across different tabs > --- > > Key: AMBARI-19221 > URL: https://issues.apache.org/jira/browse/AMBARI-19221 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Belliraj HB > Fix For: 2.5.0 > > > Preview xml feature is not functional across different tabs.UI hangs when > user tries to view preview workflow from two different tabs. > Steps to reproduce : > 1) Create a workflow and check preview is happening correctly. > 2) Open new tab and create another workflow > 3) UI hangs when user tries to preview. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19221) Preview xml feature is not functional across different tabs
Padma Priya Nagaraj created AMBARI-19221: Summary: Preview xml feature is not functional across different tabs Key: AMBARI-19221 URL: https://issues.apache.org/jira/browse/AMBARI-19221 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Fix For: 2.5.0 Preview xml feature is not functional across different tabs.UI hangs when user tries to view preview workflow from two different tabs. Steps to reproduce : 1) Create a workflow and check preview is happening correctly. 2) Open new tab and create another workflow 3) UI hangs when user tries to preview. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754038#comment-15754038 ] Hudson commented on AMBARI-19031: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6245 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6245/]) AMBARI-19031: UI Enhancements, import/export assets and smart version (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fb567758d71a4b90afa95d180f8340f6217f4f47]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/bundle/bundle-xml-importer.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/WorkflowFileInfo.java * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/WorkflowFilesService.java * (add) contrib/views/wfmanager/src/main/resources/ui/app/routes/design/jobtab.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/design.js * (add) contrib/views/wfmanager/src/main/resources/ui/tests/integration/components/import-from-stream-test.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowsRepo.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-coord-config.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/assets/AssetService.java * (edit) contrib/views/wfmanager/pom.xml * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-icon.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/search-create-new-bar.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/controllers/job.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/hdfs-browser.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/services/dashboard-context.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-actions.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/preview-dialog.js * (edit) contrib/views/wfmanager/src/main/resources/ui/bower.json * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-coord-config.hbs * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/model/Workflow.java * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/services/dashboard-context-test.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/utils/common-utils.js * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/routes/design/dashboardtab-test.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/AmbariIOUtil.java * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/services/save-job-test.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/schema-versions.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/design.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/job.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/router.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-version-settings.hbs * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/HDFSFileUtils.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/preview-dialog.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/date-with-expr.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-version-settings.hbs * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowsManagerResource.java * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-version-settings.js
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754032#comment-15754032 ] Hudson commented on AMBARI-19031: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #542 (See [https://builds.apache.org/job/Ambari-branch-2.5/542/]) AMBARI-19031: UI Enhancements, import/export assets and smart version (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9bc0b99609e8c746d055dafc5c42eea60a6b80ed]) * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/design/dashboardtab.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/bundle/bundle-xml-generator.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/router.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/model/Workflow.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/coordinator/coordinator-xml-generator.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/utils/common-utils.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/assets/model/ActionAsset.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/hdfs-browser.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/search-create-new-bar.js * (edit) contrib/views/wfmanager/src/main/resources/ui/package.json * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-icon.js * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/routes/design/dashboardtab-test.js * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/WorkflowFileInfo.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/job.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/import-from-stream.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/dashboard.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/date-with-expr.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-actions.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/design/jobtab.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-create-new-bar.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/app/controllers/design/dashboardtab.js * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/workflowmanager/WorkflowsManagerResource.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/name-value-config.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/routes/design/jobtab.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/mapping-utils.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hdfs-browser.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/ember-cli-build.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/app/services/save-job.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/pom.xml * (edit) contrib/views/wfmanager/src/main/resources/ui/bower.json * (add) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/assets/AssetService.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/job-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/job.hbs * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/HDFSFileUtils.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/index.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-job-details.hbs * (edit) contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieUtils.java * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/bundle/bundle-xml-importer.js * (add)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19031: --- Resolution: Fixed Assignee: Nitiraj Singh Rathore Status: Resolved (was: Patch Available) > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19031_branch-2.5.patch, AMBARI-19031_trunk.patch > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753945#comment-15753945 ] Nitiraj Singh Rathore commented on AMBARI-19031: committed to trunk and branch-2.5. > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > Attachments: AMBARI-19031_branch-2.5.patch, AMBARI-19031_trunk.patch > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19201) Log size of status command queue size on Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-19201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19201: Attachment: AMBARI-19201_v2.patch > Log size of status command queue size on Ambari agent > - > > Key: AMBARI-19201 > URL: https://issues.apache.org/jira/browse/AMBARI-19201 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19201.patch, AMBARI-19201_v2.patch > > > Before adding new status commands to agent statusCommandQueue, we delete old > ones. Sometimes status command execution may take too long therefore would be > useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19213) DataNodes Live widget can't be edited
[ https://issues.apache.org/jira/browse/AMBARI-19213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19213: --- Resolution: Fixed Status: Resolved (was: Patch Available) > DataNodes Live widget can't be edited > - > > Key: AMBARI-19213 > URL: https://issues.apache.org/jira/browse/AMBARI-19213 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19213.patch > > > Click on Edit-button for "DataNodes Live" widget causes JS error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
