[jira] [Updated] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-18284:
--
Labels: patch-available (was: )
Status: Patch Available (was: Open)
> Ambari PigView stores the script in HDFS in non UTF-8 format
>
>
> Key: AMBARI-18284
> URL: https://issues.apache.org/jira/browse/AMBARI-18284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Labels: patch-available
> Attachments: AMBARI-18284.patch, PigView_After-1.png,
> PigView_After-2.png
>
>
> - In Ambari PigView if we have a script like following containing some
> special characters like 'á'
> {code}
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á');
> DESCRIBE STOCK_A;
> {code}
> Then after executing the script we see that in the HDFS it is stored as
> following:
> {code}
> hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?');
> DESCRIBE STOCK_A;
> {code}
> *Notice:* the 'á' is converted to '?'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma reassigned AMBARI-18284:
-
Assignee: JaySenSharma
> Ambari PigView stores the script in HDFS in non UTF-8 format
>
>
> Key: AMBARI-18284
> URL: https://issues.apache.org/jira/browse/AMBARI-18284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Attachments: AMBARI-18284.patch, PigView_After-1.png,
> PigView_After-2.png
>
>
> - In Ambari PigView if we have a script like following containing some
> special characters like 'á'
> {code}
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á');
> DESCRIBE STOCK_A;
> {code}
> Then after executing the script we see that in the HDFS it is stored as
> following:
> {code}
> hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?');
> DESCRIBE STOCK_A;
> {code}
> *Notice:* the 'á' is converted to '?'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-18284:
--
Attachment: PigView_After-2.png
PigView_After-1.png
> Ambari PigView stores the script in HDFS in non UTF-8 format
>
>
> Key: AMBARI-18284
> URL: https://issues.apache.org/jira/browse/AMBARI-18284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
> Attachments: AMBARI-18284.patch, PigView_After-1.png,
> PigView_After-2.png
>
>
> - In Ambari PigView if we have a script like following containing some
> special characters like 'á'
> {code}
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á');
> DESCRIBE STOCK_A;
> {code}
> Then after executing the script we see that in the HDFS it is stored as
> following:
> {code}
> hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?');
> DESCRIBE STOCK_A;
> {code}
> *Notice:* the 'á' is converted to '?'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-18284:
--
Attachment: AMBARI-18284.patch
Attaching patch to read write in HDFS in UTF-8 format as
{code}
output.write(request.file.getFileContent().getBytes("UTF-8"));
{code}
> Ambari PigView stores the script in HDFS in non UTF-8 format
>
>
> Key: AMBARI-18284
> URL: https://issues.apache.org/jira/browse/AMBARI-18284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
> Environment: All
>Reporter: JaySenSharma
> Attachments: AMBARI-18284.patch
>
>
> - In Ambari PigView if we have a script like following containing some
> special characters like 'á'
> {code}
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á');
> DESCRIBE STOCK_A;
> {code}
> Then after executing the script we see that in the HDFS it is stored as
> following:
> {code}
> hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
> STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?');
> DESCRIBE STOCK_A;
> {code}
> *Notice:* the 'á' is converted to '?'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18284) Ambari PigView stores the script in HDFS in non UTF-8 format
JaySenSharma created AMBARI-18284:
-
Summary: Ambari PigView stores the script in HDFS in non UTF-8
format
Key: AMBARI-18284
URL: https://issues.apache.org/jira/browse/AMBARI-18284
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: trunk
Environment: All
Reporter: JaySenSharma
- In Ambari PigView if we have a script like following containing some special
characters like 'á'
{code}
STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('á');
DESCRIBE STOCK_A;
{code}
Then after executing the script we see that in the HDFS it is stored as
following:
{code}
hdfs dfs -cat /user/admin/pig/scripts/testlatin-2016-08-30_12-15.pig
STOCK_A = LOAD '/user/admin/dummy.csv' USING PigStorage('?');
DESCRIBE STOCK_A;
{code}
*Notice:* the 'á' is converted to '?'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14964) AMS cannot be installed on trunk
[
https://issues.apache.org/jira/browse/AMBARI-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450750#comment-15450750
]
Aravindan Vijayan commented on AMBARI-14964:
[~Denpong-Hoover]
Are you trying to build Ambari or just Ambari Metrics Service (sub portion of
Ambari) ? Also, please use the mailing list d...@ambari.apache.org to direct
your query.
> AMS cannot be installed on trunk
>
>
> Key: AMBARI-14964
> URL: https://issues.apache.org/jira/browse/AMBARI-14964
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-14964.patch
>
>
> Installation of AMS fails due to the following:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 65, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 238, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 28, in install
> self.install_packages(env, exclude_packages =
> ['ambari-metrics-collector'])
> TypeError: install_packages() got an unexpected keyword argument
> 'exclude_packages'
> stdout:
> 2016-02-08 23:55:57,518 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-02-08 23:55:57,519 - Group['hadoop'] {}
> 2016-02-08 23:55:57,520 - Group['users'] {}
> 2016-02-08 23:55:57,520 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,520 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,521 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,521 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'users']}
> 2016-02-08 23:55:57,522 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'users']}
> 2016-02-08 23:55:57,522 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,523 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,523 - User['hcat'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,524 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,524 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
> 2016-02-08 23:55:57,525 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-02-08 23:55:57,526 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2016-02-08 23:55:57,529 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if
> 2016-02-08 23:55:57,530 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
> 'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
> 2016-02-08 23:55:57,530 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-02-08 23:55:57,531 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> hbase /home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase']
> {'not_if': '(test $(id -u hbase) -gt 1000) || (false)'}
> 2016-02-08 23:55:57,534 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
> /home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase'] due
> to not_if
> 2016-02-08 23:55:57,534 - Group['hdfs'] {}
> 2016-02-08 23:55:57,534 - User['hdfs'] {'fetch_nonlocal_groups': True,
> 'groups': [u'hadoop', u'hdfs']}
> 2016-02-08 23:55:57,535 - FS Type:
> 2016-02-08 23:55:57,535 - Directory['/etc/hadoop'] {'mode': 0755}
> 2016-02-08 23:55:57,548 -
> File['/usr/hdp/current/hadoop-client/conf/hadoop-env.sh'] {'content':
> InlineTemplate(...), 'owner': 'hdfs', 'group': 'hadoop'}
> 2016-02-08 23:55:57,548 -
> Directory['/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir'] {'owner':
> 'hdfs', 'group': 'hadoop', 'mode': 0777}
> 2016-02-08 23:55:57,557 - Repository['HDP-2.3'] {'base_url':
> 'http://public-repo-1.hortonworks.com/HDP/ubuntu12/2.x/updates/2.3.4.0',
> 'action':
[jira] [Commented] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450747#comment-15450747 ] Hudson commented on AMBARI-18282: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5604 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5604/]) AMBARI-18282. By default 2.3.ECS stack should be disabled for HDP (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14639858d71d56ce0cd4d8a1bee23f792d8dbcc0]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/metainfo.xml > By default 2.3.ECS stack should be disabled for HDP > --- > > Key: AMBARI-18282 > URL: https://issues.apache.org/jira/browse/AMBARI-18282 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.1 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: trunk, 2.4.1, 2.5.0 > > Attachments: AMBARI-18282.patch > > > By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450748#comment-15450748
]
Hudson commented on AMBARI-18275:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5604 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5604/])
AMBARI-18275. Ambari server upgrade script deletes all .pyc files (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f45e9054d724e53f78cc3dd8768da6587909c8f4])
* (edit) ambari-server/conf/unix/install-helper.sh
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.4.1, 2.5.0
>
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Attachment: AMBARI-18281.v1.patch > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Attachment: (was: AMBARI-18281.v1.patch) > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Status: Open (was: Patch Available) > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Attachment: AMBARI-18281.v1.patch > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18279) Use the PropertiesFile python command to create property files instead of jinja templates
[
https://issues.apache.org/jira/browse/AMBARI-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450605#comment-15450605
]
Hadoop QA commented on AMBARI-18279:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826229/AMBARI-18279.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/8534//console
This message is automatically generated.
> Use the PropertiesFile python command to create property files instead of
> jinja templates
> -
>
> Key: AMBARI-18279
> URL: https://issues.apache.org/jira/browse/AMBARI-18279
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18279.patch
>
>
> Instead of using jinja templates use the PropetiesFile command in
> resource_management.libraries.resources.properties_file to generate the
> property files, thus prevent enumerating all the non-custom properties in
> params.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[
https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450603#comment-15450603
]
Hadoop QA commented on AMBARI-18280:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826231/AMBARI-18280.v0.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/8533//console
This message is automatically generated.
> Ambari widget graph is not aggregating the data correctly for Total Request
> Count
> -
>
> Key: AMBARI-18280
> URL: https://issues.apache.org/jira/browse/AMBARI-18280
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18280.v0.patch
>
>
> *PROBLEM:* Total Request Count is not growing exponentially
> *IMPACT:* User is not able to monitor the data correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[
https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450601#comment-15450601
]
Hadoop QA commented on AMBARI-18281:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826244/AMBARI-18281.v0.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/8532//console
This message is automatically generated.
> Expose Disabling of Alert Targets in Web Client
> ---
>
> Key: AMBARI-18281
> URL: https://issues.apache.org/jira/browse/AMBARI-18281
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 3.0.0
>
> Attachments: AMBARI-18281.v0.patch
>
>
> Add an option to Enable/ Disable alert notifications in Manage Notifications
> popup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14964) AMS cannot be installed on trunk
[
https://issues.apache.org/jira/browse/AMBARI-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450571#comment-15450571
]
Hoover commented on AMBARI-14964:
-
hi Aravindan Vijayan,
Build and install Ambari 2.4.0 from Source
according the page:
https://cwiki.apache.org/confluence/display/AMBARI/Build+and+install+Ambari+2.4.0+from+Source
when runing:
pushd ambari-metrics
mvn versions:set -DnewVersion=2.4.0
the console logging:
[INFO] Local aggregation root: /root/apache-ambari-2.4.0-src
[INFO] Processing change of org.apache.ambari:ambari-metrics:2.4.0.0.0 -> 2.4.0
[ERROR]
java.io.FileNotFoundException:
/root/apache-ambari-2.4.0-src/ambari-metrics/ambari-metrics (No such file or
directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.codehaus.plexus.util.xml.XmlReader.(XmlReader.java:124)
at
org.codehaus.plexus.util.xml.XmlStreamReader.(XmlStreamReader.java:67)
at
org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:118)
at
org.codehaus.mojo.versions.api.PomHelper.readXmlFile(PomHelper.java:1606)
at
org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.process(AbstractVersionsUpdaterMojo.java:321)
at org.codehaus.mojo.versions.SetMojo.execute(SetMojo.java:298)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] Processing org.apache.ambari:ambari-metrics
[INFO] Updating project org.apache.ambari:ambari-metrics
[INFO] from version 2.4.0.0.0 to 2.4.0
how to work arround ?
> AMS cannot be installed on trunk
>
>
> Key: AMBARI-14964
> URL: https://issues.apache.org/jira/browse/AMBARI-14964
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-14964.patch
>
>
> Installation of AMS fails due to the following:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 65, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 238, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 28, in install
> self.install_packages(env, exclude_packages =
> ['ambari-metrics-collector'])
> TypeError: install_packages() got an unexpected keyword argument
> 'exclude_packages'
> stdout:
> 2016-02-08 23:55:57,518 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-02-08 23:55:57,519 - Group['hadoop'] {}
> 2016-02-08 23:55:57,520 - Group['users'] {}
> 2016-02-08
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18275:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.4.1, 2.5.0
>
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-18282. Resolution: Fixed > By default 2.3.ECS stack should be disabled for HDP > --- > > Key: AMBARI-18282 > URL: https://issues.apache.org/jira/browse/AMBARI-18282 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.1 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: trunk, 2.4.1, 2.5.0 > > Attachments: AMBARI-18282.patch > > > By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450473#comment-15450473 ] Jayush Luniya commented on AMBARI-18282: +1 > By default 2.3.ECS stack should be disabled for HDP > --- > > Key: AMBARI-18282 > URL: https://issues.apache.org/jira/browse/AMBARI-18282 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.1 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: trunk, 2.4.1, 2.5.0 > > Attachments: AMBARI-18282.patch > > > By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18275:
---
Fix Version/s: 2.4.1
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.4.1, 2.5.0
>
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18282: --- Fix Version/s: 2.5.0 trunk > By default 2.3.ECS stack should be disabled for HDP > --- > > Key: AMBARI-18282 > URL: https://issues.apache.org/jira/browse/AMBARI-18282 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.1 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: trunk, 2.4.1, 2.5.0 > > Attachments: AMBARI-18282.patch > > > By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18282: --- Attachment: AMBARI-18282.patch Tested locally by making the changes manually. > By default 2.3.ECS stack should be disabled for HDP > --- > > Key: AMBARI-18282 > URL: https://issues.apache.org/jira/browse/AMBARI-18282 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.1 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.4.1 > > Attachments: AMBARI-18282.patch > > > By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP
Sumit Mohanty created AMBARI-18282: -- Summary: By default 2.3.ECS stack should be disabled for HDP Key: AMBARI-18282 URL: https://issues.apache.org/jira/browse/AMBARI-18282 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.1 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.4.1 By default 2.3.ECS stack should be disabled for HDP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Status: Patch Available (was: Open) > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18281: - Issue Type: New Feature (was: Bug) > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18281: Attachment: AMBARI-18281.v0.patch > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
Vivek Ratnavel Subramanian created AMBARI-18281: --- Summary: Expose Disabling of Alert Targets in Web Client Key: AMBARI-18281 URL: https://issues.apache.org/jira/browse/AMBARI-18281 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 3.0.0 Add an option to Enable/ Disable alert notifications in Manage Notifications popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-9476) Use JDBC driver symbolic link instead of filename in ranger install
[
https://issues.apache.org/jira/browse/AMBARI-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449945#comment-15449945
]
Chandan Kumar commented on AMBARI-9476:
---
May be I know which version this fix has been pushed, I am using ambari 2.2.2.0
and I could still see the same issue.
> Use JDBC driver symbolic link instead of filename in ranger install
> ---
>
> Key: AMBARI-9476
> URL: https://issues.apache.org/jira/browse/AMBARI-9476
> Project: Ambari
> Issue Type: Bug
>Reporter: Velmurugan Periasamy
>Assignee: Velmurugan Periasamy
> Fix For: 2.0.0
>
>
> One of the requirements for adding Ranger to an existing cluster is to run
> "ambari-server setup" to deploy the JDBC driver.
> Below command is run to meet this requirement.
> {code}
> ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java-5.1.17.jar
> {code}
> However, this caused Ranger install phase to fail, because it is trying to
> download the driver file from
> http://ambari-host:8080/resources/mysql-connector-java.jar, which does not
> exist.
> Note that if you had run the below it works.
> {code}
> ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java.jar
> {code}
> However, relying on the exact filename is error prone.
> The ambari-server setup command creates a symlink called
> "mysql-jdbc-driver.jar" that points to the actual jar file. So the ranger
> setup script should use that name instead for MySQL. Also check
> corresponding driver name for Oracle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18280: Status: Patch Available (was: Open) > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18280: Attachment: AMBARI-18280.v0.patch Local ambari-web test passed. 30014 tests complete (27 seconds) 154 tests pending Manual testing done. > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18279) Use the PropertiesFile python command to create property files instead of jinja templates
[ https://issues.apache.org/jira/browse/AMBARI-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18279: Attachment: AMBARI-18279.patch > Use the PropertiesFile python command to create property files instead of > jinja templates > - > > Key: AMBARI-18279 > URL: https://issues.apache.org/jira/browse/AMBARI-18279 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18279.patch > > > Instead of using jinja templates use the PropetiesFile command in > resource_management.libraries.resources.properties_file to generate the > property files, thus prevent enumerating all the non-custom properties in > params.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18279) Use the PropertiesFile python command to create property files instead of jinja templates
[ https://issues.apache.org/jira/browse/AMBARI-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18279: Status: Patch Available (was: In Progress) > Use the PropertiesFile python command to create property files instead of > jinja templates > - > > Key: AMBARI-18279 > URL: https://issues.apache.org/jira/browse/AMBARI-18279 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18279.patch > > > Instead of using jinja templates use the PropetiesFile command in > resource_management.libraries.resources.properties_file to generate the > property files, thus prevent enumerating all the non-custom properties in > params.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
Zhe (Joe) Wang created AMBARI-18280: --- Summary: Ambari widget graph is not aggregating the data correctly for Total Request Count Key: AMBARI-18280 URL: https://issues.apache.org/jira/browse/AMBARI-18280 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.2 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.5.0 *PROBLEM:* Total Request Count is not growing exponentially *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18279) Use the PropertiesFile python command to create property files instead of jinja templates
Miklos Gergely created AMBARI-18279: --- Summary: Use the PropertiesFile python command to create property files instead of jinja templates Key: AMBARI-18279 URL: https://issues.apache.org/jira/browse/AMBARI-18279 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 Instead of using jinja templates use the PropetiesFile command in resource_management.libraries.resources.properties_file to generate the property files, thus prevent enumerating all the non-custom properties in params.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449769#comment-15449769 ] Hudson commented on AMBARI-18277: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5603 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5603/]) AMBARI-18277. Configs recommendations request fails (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=04652804d70fef1e2ba515a375887b29d7d3143e]) * (edit) ambari-web/app/mixins/common/configs/enhanced_configs.js > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18274) Hive service check failed
[
https://issues.apache.org/jira/browse/AMBARI-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449623#comment-15449623
]
Hadoop QA commented on AMBARI-18274:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826175/AMBARI-18274.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/8531//console
This message is automatically generated.
> Hive service check failed
> -
>
> Key: AMBARI-18274
> URL: https://issues.apache.org/jira/browse/AMBARI-18274
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-18274.patch
>
>
> STR:
> # Deploy cluster HDP 2.3.2.0-2950
> # Enable NN HA
> # Register and install HDP 2.5.0.0-1243
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 191, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 97, in service_check
> webhcat_service_check()
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service_check.py",
> line 125, in webhcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> nat-u14-pqys-ambari-hv-r-upg-11-4.openstacklocal ambari-qa 20111
> idtest.ambari-qa.1472174540.57.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {"error":"User: cstm-hcat is not allowed to impersonate
> ambari-qa"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449616#comment-15449616
]
Hadoop QA commented on AMBARI-18278:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826208/AMBARI-18278.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/8529//console
This message is automatically generated.
> Provide Notes On Service Config Changes During Ambari Upgrade
> -
>
> Key: AMBARI-18278
> URL: https://issues.apache.org/jira/browse/AMBARI-18278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18278.patch
>
>
> For every configuration change made, a meaningful note should be included so
> that administrators understand why so many versions are being created. Any of
> the following would be fine:
> - Ambari Upgrade updated storm-site
> - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site
> - The following configurations were changed as part of the Ambar Server
> Upgrade: storm-site
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[
https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449613#comment-15449613
]
Hadoop QA commented on AMBARI-18273:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826211/AMBARI-18273.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/8528//console
This message is automatically generated.
> Add logging to differentiate between ambari-server start/restart commands vs.
> other commands
>
>
> Key: AMBARI-18273
> URL: https://issues.apache.org/jira/browse/AMBARI-18273
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18273.patch
>
>
> Add ambari server python side logging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17228) Blueprint deployments should support a "START_ONLY" provision_action for clusters
[ https://issues.apache.org/jira/browse/AMBARI-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17228: - Fix Version/s: (was: 2.5.0) trunk > Blueprint deployments should support a "START_ONLY" provision_action for > clusters > - > > Key: AMBARI-17228 > URL: https://issues.apache.org/jira/browse/AMBARI-17228 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Sandor Magyari >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-17228_v3.patch > > > This JIRA tracks an extension to the work started in: > AMBARI-16220 > In that JIRA, support is being added to allow Blueprint deployments that skip > the installation steps, and only attempt to start all components in the > cluster after the configuration phase has completed. > In AMBARI-16220, the feature is configured via a property in > "ambari.properties", which configures this feature on the ambari-server > itself. > This current JIRA tracks a suggestion to extend this feature, such that the > "START_ONLY" mode can be treated as a new type of "provision_action". > Using the property specified in ambari.properties isn't incorrect, but may be > inconvenient in the future for enhancements and maintenance. > In multi-cluster scenarios, it might be better to configure this at the > cluster-level. > There has already been some work done to configure provisioning in a more > fine-grained way. > Sid's patch for the following Blueprints feature: > https://issues.apache.org/jira/browse/AMBARI-14283 > Shows how a "provision_action" can be selected for a given deployment. > This notion of a "provision_action" has also been extended to the component > level as well: > https://issues.apache.org/jira/browse/AMBARI-14555 > Currently, this "provision_action" configuration is only used to select an > INSTALL_ONLY deployment, but it could certainly be extended to have a > "START_ONLY" action as well. This would have the benefit of being able to > choose this option on a per-cluster basis, and not require an ambari-server > restart if this feature is desired but not enabled by default. > The following code reference shows how the "provision_action" configuration > option is used by a Blueprints deployment: > org.apache.ambari.server.topology.HostRequest#createTasks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17602) Capacity Scheduler View - Fetching current RM configuration of queues and preemption implementation
[ https://issues.apache.org/jira/browse/AMBARI-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17602: - Fix Version/s: (was: 2.5.0) trunk > Capacity Scheduler View - Fetching current RM configuration of queues and > preemption implementation > --- > > Key: AMBARI-17602 > URL: https://issues.apache.org/jira/browse/AMBARI-17602 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: trunk > > Attachments: AMBARI-17602.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18263) Agent connection retry fails after one try
[
https://issues.apache.org/jira/browse/AMBARI-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-18263:
-
Fix Version/s: (was: 2.5.0)
trunk
> Agent connection retry fails after one try
> --
>
> Key: AMBARI-18263
> URL: https://issues.apache.org/jira/browse/AMBARI-18263
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18263.patch
>
>
> Currently agent connection retry mechanism fails after one try:
> {code}
> WARNING 2016-08-12 16:13:08,291 main.py:351 - Unable to determine the IP
> address of the Ambari server 'ambari-server'
> ERROR 2016-08-12 16:13:08,292 main.py:392 - Exiting with exception:
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 387, in
>
> main(heartbeat_stop_callback)
> File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 355, in
> main
> (retries, connected, stopped) = netutil.try_to_connect(server_url,
> MAX_RETRIES, logger)
> UnboundLocalError: local variable 'server_url' referenced before assignment
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18269) Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric
[ https://issues.apache.org/jira/browse/AMBARI-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18269: - Fix Version/s: (was: 2.5.0) > Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric > > > Key: AMBARI-18269 > URL: https://issues.apache.org/jira/browse/AMBARI-18269 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > > *PROBLEM*: > Under Ambari Dashboard -> Cluster metrics. > It has been noticed that the metrics Nodes._avg and CPUs._avg are showing the > same data. > Nodes._avg should ideally denote the number of nodes in the cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-2330) Ambari should support "auto start" and "desired state" of service components
[ https://issues.apache.org/jira/browse/AMBARI-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-2330: - Reopening since in 2.4.0 we hid this from the UI as an experimental feature. > Ambari should support "auto start" and "desired state" of service components > > > Key: AMBARI-2330 > URL: https://issues.apache.org/jira/browse/AMBARI-2330 > Project: Ambari > Issue Type: Improvement >Affects Versions: 1.2.4 >Reporter: Jeff Sposetti >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > > Ambari Server and Agents can be setup to auto-start on system reboot (using > the init.d scripts) > In the case of hadoop Components (like NN, JT, DN, etc), the user has to go > into Ambari and click "start", which can be cumbersome. And if > missed/forgotten, can cause unintended outages. > Ambari should impose "desired" service state, with the ability to designate > "auto start". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[ https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18273: --- Attachment: (was: AMBARI-18273.patch) > Add logging to differentiate between ambari-server start/restart commands vs. > other commands > > > Key: AMBARI-18273 > URL: https://issues.apache.org/jira/browse/AMBARI-18273 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18273.patch > > > Add ambari server python side logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[ https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18273: --- Attachment: AMBARI-18273.patch > Add logging to differentiate between ambari-server start/restart commands vs. > other commands > > > Key: AMBARI-18273 > URL: https://issues.apache.org/jira/browse/AMBARI-18273 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18273.patch > > > Add ambari server python side logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18278: Fix Version/s: 3.0.0 > Provide Notes On Service Config Changes During Ambari Upgrade > - > > Key: AMBARI-18278 > URL: https://issues.apache.org/jira/browse/AMBARI-18278 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 3.0.0 > > Attachments: AMBARI-18278.patch > > > For every configuration change made, a meaningful note should be included so > that administrators understand why so many versions are being created. Any of > the following would be fine: > - Ambari Upgrade updated storm-site > - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site > - The following configurations were changed as part of the Ambar Server > Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18278: Affects Version/s: 2.4.0 > Provide Notes On Service Config Changes During Ambari Upgrade > - > > Key: AMBARI-18278 > URL: https://issues.apache.org/jira/browse/AMBARI-18278 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 3.0.0 > > Attachments: AMBARI-18278.patch > > > For every configuration change made, a meaningful note should be included so > that administrators understand why so many versions are being created. Any of > the following would be fine: > - Ambari Upgrade updated storm-site > - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site > - The following configurations were changed as part of the Ambar Server > Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18278: Attachment: AMBARI-18278.patch > Provide Notes On Service Config Changes During Ambari Upgrade > - > > Key: AMBARI-18278 > URL: https://issues.apache.org/jira/browse/AMBARI-18278 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18278.patch > > > For every configuration change made, a meaningful note should be included so > that administrators understand why so many versions are being created. Any of > the following would be fine: > - Ambari Upgrade updated storm-site > - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site > - The following configurations were changed as part of the Ambar Server > Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
Dmitry Lysnichenko created AMBARI-18278: --- Summary: Provide Notes On Service Config Changes During Ambari Upgrade Key: AMBARI-18278 URL: https://issues.apache.org/jira/browse/AMBARI-18278 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Attachments: AMBARI-18278.patch For every configuration change made, a meaningful note should be included so that administrators understand why so many versions are being created. Any of the following would be fine: - Ambari Upgrade updated storm-site - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site - The following configurations were changed as part of the Ambar Server Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18278: Component/s: ambari-server > Provide Notes On Service Config Changes During Ambari Upgrade > - > > Key: AMBARI-18278 > URL: https://issues.apache.org/jira/browse/AMBARI-18278 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18278.patch > > > For every configuration change made, a meaningful note should be included so > that administrators understand why so many versions are being created. Any of > the following would be fine: > - Ambari Upgrade updated storm-site > - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site > - The following configurations were changed as part of the Ambar Server > Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18278: Status: Patch Available (was: Open) > Provide Notes On Service Config Changes During Ambari Upgrade > - > > Key: AMBARI-18278 > URL: https://issues.apache.org/jira/browse/AMBARI-18278 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18278.patch > > > For every configuration change made, a meaningful note should be included so > that administrators understand why so many versions are being created. Any of > the following would be fine: > - Ambari Upgrade updated storm-site > - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site > - The following configurations were changed as part of the Ambar Server > Upgrade: storm-site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18263) Agent connection retry fails after one try
[
https://issues.apache.org/jira/browse/AMBARI-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-18263:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Agent connection retry fails after one try
> --
>
> Key: AMBARI-18263
> URL: https://issues.apache.org/jira/browse/AMBARI-18263
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18263.patch
>
>
> Currently agent connection retry mechanism fails after one try:
> {code}
> WARNING 2016-08-12 16:13:08,291 main.py:351 - Unable to determine the IP
> address of the Ambari server 'ambari-server'
> ERROR 2016-08-12 16:13:08,292 main.py:392 - Exiting with exception:
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 387, in
>
> main(heartbeat_stop_callback)
> File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 355, in
> main
> (retries, connected, stopped) = netutil.try_to_connect(server_url,
> MAX_RETRIES, logger)
> UnboundLocalError: local variable 'server_url' referenced before assignment
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18277: - Resolution: Fixed Status: Resolved (was: Patch Available) > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449494#comment-15449494 ] Aleksandr Kovalenko commented on AMBARI-18277: -- committed to trunk > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449487#comment-15449487 ] Aleksandr Kovalenko commented on AMBARI-18277: -- Tested manually. Result of running unit tests: 30014 tests complete (37 seconds) 154 tests pending > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18277) Configs recommendations request fails
[
https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449483#comment-15449483
]
Hadoop QA commented on AMBARI-18277:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826205/AMBARI-18277.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/8527//console
This message is automatically generated.
> Configs recommendations request fails
> -
>
> Key: AMBARI-18277
> URL: https://issues.apache.org/jira/browse/AMBARI-18277
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18277.patch
>
>
> 400 Error:
> Request body is not correct, error: null
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449480#comment-15449480 ] Antonenko Alexander commented on AMBARI-18277: -- +1 for the patch > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18277: - Status: Patch Available (was: Open) > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18277) Configs recommendations request fails
[ https://issues.apache.org/jira/browse/AMBARI-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18277: - Attachment: AMBARI-18277.patch > Configs recommendations request fails > - > > Key: AMBARI-18277 > URL: https://issues.apache.org/jira/browse/AMBARI-18277 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18277.patch > > > 400 Error: > Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18277) Configs recommendations request fails
Aleksandr Kovalenko created AMBARI-18277: Summary: Configs recommendations request fails Key: AMBARI-18277 URL: https://issues.apache.org/jira/browse/AMBARI-18277 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 3.0.0 400 Error: Request body is not correct, error: null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18276) YARN Queue Manager Permissions
Elton Atkins created AMBARI-18276: - Summary: YARN Queue Manager Permissions Key: AMBARI-18276 URL: https://issues.apache.org/jira/browse/AMBARI-18276 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.2.2 Environment: Ambari 2.2.2 & HDP 2.4.2 Reporter: Elton Atkins Priority: Minor Hi, I have multiple Ambari local groups to divide and distinguish between Operators and Read-Only users. The Operators have the needed permissions on the Ambari and can restart any service, but noticed that when they go to the YARN Queue Manager; they do not have permissions to change any of the queues capacity values even though they have USE permissions on the VIEW Instance. I then gave an individual user Operator status on the cluster and this managed to give the user the needed modify permissions on the YARN queues, even though he was a member of an Operator group. Don't know whether anyone reported this issue and so opened a ticket myself... Regards, Elton -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18275:
Fix Version/s: 2.4.1
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.1
>
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18275:
Component/s: ambari-server
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18275:
Status: Patch Available (was: Open)
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
Dmitry Lysnichenko created AMBARI-18275:
---
Summary: Ambari server upgrade script deletes all .pyc files
Key: AMBARI-18275
URL: https://issues.apache.org/jira/browse/AMBARI-18275
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Attachments: AMBARI-18275.patch
We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest packages
(1226).
https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
delete any pyc files"
The patch contains the following two lines
{code}
AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
{code}
The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
on the root directory and deletes ALL pyc files from the ambari server machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18275) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18275:
Attachment: AMBARI-18275.patch
> Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18275
> URL: https://issues.apache.org/jira/browse/AMBARI-18275
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18275.patch
>
>
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18274) Hive service check failed
[
https://issues.apache.org/jira/browse/AMBARI-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18274:
---
Status: Patch Available (was: Open)
> Hive service check failed
> -
>
> Key: AMBARI-18274
> URL: https://issues.apache.org/jira/browse/AMBARI-18274
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-18274.patch
>
>
> STR:
> # Deploy cluster HDP 2.3.2.0-2950
> # Enable NN HA
> # Register and install HDP 2.5.0.0-1243
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 191, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 97, in service_check
> webhcat_service_check()
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service_check.py",
> line 125, in webhcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> nat-u14-pqys-ambari-hv-r-upg-11-4.openstacklocal ambari-qa 20111
> idtest.ambari-qa.1472174540.57.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {"error":"User: cstm-hcat is not allowed to impersonate
> ambari-qa"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18274) Hive service check failed
[
https://issues.apache.org/jira/browse/AMBARI-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18274:
---
Attachment: AMBARI-18274.patch
> Hive service check failed
> -
>
> Key: AMBARI-18274
> URL: https://issues.apache.org/jira/browse/AMBARI-18274
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-18274.patch
>
>
> STR:
> # Deploy cluster HDP 2.3.2.0-2950
> # Enable NN HA
> # Register and install HDP 2.5.0.0-1243
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 191, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 97, in service_check
> webhcat_service_check()
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service_check.py",
> line 125, in webhcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> nat-u14-pqys-ambari-hv-r-upg-11-4.openstacklocal ambari-qa 20111
> idtest.ambari-qa.1472174540.57.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {"error":"User: cstm-hcat is not allowed to impersonate
> ambari-qa"}http_code <500>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18274) Hive service check failed
Vitaly Brodetskyi created AMBARI-18274:
--
Summary: Hive service check failed
Key: AMBARI-18274
URL: https://issues.apache.org/jira/browse/AMBARI-18274
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: trunk
STR:
# Deploy cluster HDP 2.3.2.0-2950
# Enable NN HA
# Register and install HDP 2.5.0.0-1243
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
line 191, in
HiveServiceCheck().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
line 97, in service_check
webhcat_service_check()
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service_check.py",
line 125, in webhcat_service_check
logoutput=True)
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 71, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 93, in checked_call
tries=tries, try_sleep=try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 141, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 294, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of
'/var/lib/ambari-agent/tmp/templetonSmoke.sh
nat-u14-pqys-ambari-hv-r-upg-11-4.openstacklocal ambari-qa 20111
idtest.ambari-qa.1472174540.57.pig no_keytab false kinit no_principal
/var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd): Failed.
: {"error":"User: cstm-hcat is not allowed to impersonate ambari-qa"}http_code
<500>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[ https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18273: --- Status: Patch Available (was: Open) > Add logging to differentiate between ambari-server start/restart commands vs. > other commands > > > Key: AMBARI-18273 > URL: https://issues.apache.org/jira/browse/AMBARI-18273 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18273.patch > > > Add ambari server python side logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448750#comment-15448750 ] wangyaoxin edited comment on AMBARI-17728 at 8/30/16 11:08 AM: --- Hi ,[~afernandez], thank you for review my patch, I have to trouble you to commit the patch. Thank you! was (Author: forestsissi): Hi ,[~alejandro.villa], thank you for review my patch, I have to trouble you to commit the patch. Thank you! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448750#comment-15448750 ] wangyaoxin commented on AMBARI-17728: - Hi ,[~alejandro.villa], thank you for review my patch, I have to trouble you to commit the patch. Thank you! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-16212) Reduce server startup time
[ https://issues.apache.org/jira/browse/AMBARI-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448443#comment-15448443 ] Laszlo Puskas edited comment on AMBARI-16212 at 8/30/16 8:37 AM: - The view extraction didn't require any code change (extraction can be done manually prior to the server start on environments where the start time is critical). was (Author: lpuskas): The view extraction didn't require any code change (extraction can be done manually). > Reduce server startup time > -- > > Key: AMBARI-16212 > URL: https://issues.apache.org/jira/browse/AMBARI-16212 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Laszlo Puskas > Fix For: 2.4.0 > > > During startup Ambari server does some work such as expanding view jars which > is done sequentially which may last couple of minutes if there are many views > to be extracted. > Perhaps server can be started as part of sys-prep to allow view extraction to > reduce the time for the second start. > In addition, other optimizations should be explored to expedite server start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16212) Reduce server startup time
[ https://issues.apache.org/jira/browse/AMBARI-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Puskas resolved AMBARI-16212. Resolution: Fixed Fix Version/s: (was: 2.4.1) 2.4.0 > Reduce server startup time > -- > > Key: AMBARI-16212 > URL: https://issues.apache.org/jira/browse/AMBARI-16212 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Laszlo Puskas > Fix For: 2.4.0 > > > During startup Ambari server does some work such as expanding view jars which > is done sequentially which may last couple of minutes if there are many views > to be extracted. > Perhaps server can be started as part of sys-prep to allow view extraction to > reduce the time for the second start. > In addition, other optimizations should be explored to expedite server start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16212) Reduce server startup time
[ https://issues.apache.org/jira/browse/AMBARI-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448443#comment-15448443 ] Laszlo Puskas commented on AMBARI-16212: The view extraction didn't require any code change (extraction can be done manually). > Reduce server startup time > -- > > Key: AMBARI-16212 > URL: https://issues.apache.org/jira/browse/AMBARI-16212 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Laszlo Puskas > Fix For: 2.4.1 > > > During startup Ambari server does some work such as expanding view jars which > is done sequentially which may last couple of minutes if there are many views > to be extracted. > Perhaps server can be started as part of sys-prep to allow view extraction to > reduce the time for the second start. > In addition, other optimizations should be explored to expedite server start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15729) ambari-server script not able to load log4.properties other than the default location.
[
https://issues.apache.org/jira/browse/AMBARI-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448359#comment-15448359
]
Andrew Onischuk commented on AMBARI-15729:
--
Hello [~Denpong-Hoover]
you may have an old os_utils pyc/pyo file which prevents this function from
getting loaded in your /usr/lib/python2.6/site-packages/ambari_server
> ambari-server script not able to load log4.properties other than the default
> location.
> --
>
> Key: AMBARI-15729
> URL: https://issues.apache.org/jira/browse/AMBARI-15729
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15729.patch
>
>
> Ambari server script is using hard coded path to load _log4.properties_ file
> **serverConfiguration.py**
>
>
>
> self.OUT_DIR =
> parse_log4j_file(AmbariPath.get("/etc/ambari-server/conf/log4j.properties"))['ambari.log.dir’]
>
> In case Ambari server is installed to other than the default location amber
> server script won't be able to load log4j.properties
> _get_conf_dir()_ should be used to determine the path of log4j.properties
> file.
> e.g.
>
>
>
> self.OUT_DIR = parse_log4j_file(get_conf_dir() +
> "/log4j.properties"))['ambari.log.dir’]
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17107) Ambari Alert for NameNode Last Checkpoint in NameNode HA
[
https://issues.apache.org/jira/browse/AMBARI-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Pathak resolved AMBARI-17107.
---
Resolution: Fixed
Fix Version/s: 2.4.0
> Ambari Alert for NameNode Last Checkpoint in NameNode HA
>
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.2.2
> Environment: Hortonworks HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
> Labels: easyfix
> Fix For: 2.4.0
>
>
> As can be seen in
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster.
> In case of HA this property will not exist and alert will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17107) Ambari Alert for NameNode Last Checkpoint in NameNode HA
[
https://issues.apache.org/jira/browse/AMBARI-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Pathak updated AMBARI-17107:
--
Environment:
Hortonworks HDP 2.4.2 with HDFS HA enabled.
was:Hortonworks hadoop HDP 2.4.2 with HDFS HA enabled.
> Ambari Alert for NameNode Last Checkpoint in NameNode HA
>
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.2.2
> Environment: Hortonworks HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
> Labels: easyfix
>
> As can be seen in
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster.
> In case of HA this property will not exist and alert will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14853) Atlas Integration: Support deploying latest Atlas(which depends on kafka) using Ambari
[
https://issues.apache.org/jira/browse/AMBARI-14853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448156#comment-15448156
]
Geoffrey Shelton Okot commented on AMBARI-14853:
Proof reading error
Just under description .
The directory specified in “atlas.kaka.data” should exist should read
The directory specified in “atlas.kafka.data” should exist.
> Atlas Integration: Support deploying latest Atlas(which depends on kafka)
> using Ambari
> --
>
> Key: AMBARI-14853
> URL: https://issues.apache.org/jira/browse/AMBARI-14853
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-14853.patch
>
>
> Three additional steps need to be done to to install Atlas 0.6 via Ambari.
> 1. Add new Atlas Kafka related properties to the Atlas configuration
> ‘application.properties’
> {code}
> atlas.notification.embedded" : false,
> atlas.kafka.data = /tmp
> atlas.kafka.bootstrap.servers = c6401.ambari.apache.org:6667
> atlas.kafka.zookeeper.connect = c6401.ambari.apache.org:2181
> atlas.kafka.hook.group.id = atlas
> atlas.kafka.entities.group.id = entities
> {code}
> * Note:
> For “atlas.kafka.bootstrap.servers” and “atlas.kafka.zookeeper.connect”,
> modify host names based on your cluster topology.
> The directory specified in “atlas.kaka.data” should exist.
> 2. Add an export of HADOOP_CLASSPATH which includes the required atlas
> directories to hive-env.xml in the 2.3 HDP stack
> {code}
> export
> HADOOP_CLASSPATH=/etc/atlas/conf:/usr/hdp/current/atlas-server/hook/hive:${HADOOP_CLASSPATH}
> {code}
> *Note:
> It is important that the atlas directories are prepended to the existing
> classpath.
> 3. Restart the Atlas and Hive services after the cluster is fully provisioned
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
