[jira] [Commented] (AMBARI-19083) After ambari only upgrade Enable security(Configure Ambari Identity) was failed because could not run "ambari-sudo.sh"
[ https://issues.apache.org/jira/browse/AMBARI-19083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722878#comment-15722878 ] Hudson commented on AMBARI-19083: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6156 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6156/]) AMBARI-19083. After ambari only upgrade Enable security(Configure Ambari (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=89b9cf5beb1304b0d90dad00b371947a3c467e8a]) * (edit) ambari-server/src/main/python/ambari_server_main.py > After ambari only upgrade Enable security(Configure Ambari Identity) was > failed because could not run "ambari-sudo.sh" > --- > > Key: AMBARI-19083 > URL: https://issues.apache.org/jira/browse/AMBARI-19083 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19083.patch > > > **STR:** > 1)Deploy cluster > 2)Make ambari only upgrade > 3)Enable security(MIT) > **Actual result:** Enable security(Configure Ambari Identity) was failed > because could not run program "ambari-sudo.sh". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19086) LDAP sync creates groups with "Local" type
[
https://issues.apache.org/jira/browse/AMBARI-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19086:
---
Summary: LDAP sync creates groups with "Local" type (was: LDAP sync
creates group with local type)
> LDAP sync creates groups with "Local" type
> --
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups
> order by group_name;
> group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo | LOCAL | 1
> 2 | ambari| LOCAL | 0
>72 | ambari-server | LOCAL | 1
>81 | ams | LOCAL | 1
>60 | atlas | LOCAL | 1
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723391#comment-15723391
]
Hadoop QA commented on AMBARI-19074:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841779/AMBARI-19074.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9531//console
This message is automatically generated.
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19088) Make sure AMS in embedded mode cannot have more than 1 deployed instance
Aravindan Vijayan created AMBARI-19088: -- Summary: Make sure AMS in embedded mode cannot have more than 1 deployed instance Key: AMBARI-19088 URL: https://issues.apache.org/jira/browse/AMBARI-19088 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Critical Fix For: 2.5.0 AMS in embedded mode uses embedded HBase using local Zk and local disk for data. If there are 2 instances of embedded AMS installed on the cluster, it can lead to data fragmentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18450: --- Attachment: AMBARI-18450.patch > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > Attachments: AMBARI-18450.patch > > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19039) In stack version, build number should not be mandatory
[ https://issues.apache.org/jira/browse/AMBARI-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723384#comment-15723384 ] Di Li commented on AMBARI-19039: Pushed to Trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=b5122e258bfe5a2e56511eb9dd29a70cf1260a9c Pushed to Branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=b90b0f8a7fa2445eec220f7987c14488406367c7 > In stack version, build number should not be mandatory > -- > > Key: AMBARI-19039 > URL: https://issues.apache.org/jira/browse/AMBARI-19039 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, > AMBARI-19039_v1.patch > > > In stack version, build number should not be mandatory. mapreduce.tar.gz > file does not get copied during blueprint deployment when stack version does > not have build version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi reassigned AMBARI-18450: -- Assignee: Vitaly Brodetskyi > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19036) Add default roles to auto created views
[ https://issues.apache.org/jira/browse/AMBARI-19036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723275#comment-15723275 ] Hudson commented on AMBARI-19036: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #457 (See [https://builds.apache.org/job/Ambari-branch-2.5/457/]) AMBARI-19036. Add default roles to auto created views. (Ashwin Rajeev (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=829304fbcdcfbbc1fd0e5d189eeed5758dd144f4]) * (edit) contrib/views/files/src/main/resources/view.xml * (edit) contrib/views/hive-next/src/main/resources/view.xml * (edit) contrib/views/capacity-scheduler/src/main/resources/view.xml * (edit) contrib/views/tez/src/main/resources/view.xml > Add default roles to auto created views > --- > > Key: AMBARI-19036 > URL: https://issues.apache.org/jira/browse/AMBARI-19036 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-19036.trunk.2.patch, AMBARI-19036.trunk.3.patch, > AMBARI-19036.trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Add the following roles to auto instances > ||View||Role|| > |Pig|CLUSTER.USER| > |Hive|CLUSTER.USER| > |Tez|CLUSTER.USER| > |File browser|CLUSTER.USER| > |Zepplin|CLUSTER.USER| > |Capacity Scheduler|CLUSTER.ADMINISTRATOR| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723367#comment-15723367
]
Hudson commented on AMBARI-19074:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6158 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6158/])
AMBARI-19074. Host-Ordered: Empty groups are returned for Downgrade (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=50ead4d237b0c03fee68192a5983044409e3e9db])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/UpgradePack.java
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19082) Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and added a port of -1
[
https://issues.apache.org/jira/browse/AMBARI-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723388#comment-15723388
]
Hadoop QA commented on AMBARI-19082:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841775/AMBARI-19082.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9530//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9530//console
This message is automatically generated.
> Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and
> added a port of -1
> --
>
> Key: AMBARI-19082
> URL: https://issues.apache.org/jira/browse/AMBARI-19082
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19082.patch
>
>
> After upgrade some properties has port number "-1".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-19074:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18450: --- Status: Patch Available (was: Open) > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > Attachments: AMBARI-18450.patch > > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19039) In stack version, build number should not be mandatory
[ https://issues.apache.org/jira/browse/AMBARI-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19039: --- Resolution: Fixed Status: Resolved (was: Patch Available) > In stack version, build number should not be mandatory > -- > > Key: AMBARI-19039 > URL: https://issues.apache.org/jira/browse/AMBARI-19039 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, > AMBARI-19039_v1.patch > > > In stack version, build number should not be mandatory. mapreduce.tar.gz > file does not get copied during blueprint deployment when stack version does > not have build version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19088) Make sure AMS in embedded mode cannot have more than 1 deployed instance
[ https://issues.apache.org/jira/browse/AMBARI-19088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19088: --- Status: Patch Available (was: Open) > Make sure AMS in embedded mode cannot have more than 1 deployed instance > > > Key: AMBARI-19088 > URL: https://issues.apache.org/jira/browse/AMBARI-19088 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19088.patch > > > AMS in embedded mode uses embedded HBase using local Zk and local disk for > data. If there are 2 instances of embedded AMS installed on the cluster, it > can lead to data fragmentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19088) Make sure AMS in embedded mode cannot have more than 1 deployed instance
[ https://issues.apache.org/jira/browse/AMBARI-19088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19088: --- Attachment: AMBARI-19088.patch > Make sure AMS in embedded mode cannot have more than 1 deployed instance > > > Key: AMBARI-19088 > URL: https://issues.apache.org/jira/browse/AMBARI-19088 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19088.patch > > > AMS in embedded mode uses embedded HBase using local Zk and local disk for > data. If there are 2 instances of embedded AMS installed on the cluster, it > can lead to data fragmentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19036) Add default roles to auto created views
[ https://issues.apache.org/jira/browse/AMBARI-19036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723291#comment-15723291 ] Hudson commented on AMBARI-19036: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6157 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6157/]) AMBARI-19036. Add default roles to auto created views. (Ashwin Rajeev (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8fbc2718e65a3771a6af9acc48f1b06d13c32bd4]) * (edit) contrib/views/files/src/main/resources/view.xml * (edit) contrib/views/capacity-scheduler/src/main/resources/view.xml * (edit) contrib/views/hive-next/src/main/resources/view.xml * (edit) contrib/views/tez/src/main/resources/view.xml > Add default roles to auto created views > --- > > Key: AMBARI-19036 > URL: https://issues.apache.org/jira/browse/AMBARI-19036 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-19036.trunk.2.patch, AMBARI-19036.trunk.3.patch, > AMBARI-19036.trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Add the following roles to auto instances > ||View||Role|| > |Pig|CLUSTER.USER| > |Hive|CLUSTER.USER| > |Tez|CLUSTER.USER| > |File browser|CLUSTER.USER| > |Zepplin|CLUSTER.USER| > |Capacity Scheduler|CLUSTER.ADMINISTRATOR| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19036) Add default roles to auto created views
[ https://issues.apache.org/jira/browse/AMBARI-19036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-19036: --- Attachment: AMBARI-19036.trunk.3.patch > Add default roles to auto created views > --- > > Key: AMBARI-19036 > URL: https://issues.apache.org/jira/browse/AMBARI-19036 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-19036.trunk.2.patch, AMBARI-19036.trunk.3.patch, > AMBARI-19036.trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Add the following roles to auto instances > ||View||Role|| > |Pig|CLUSTER.USER| > |Hive|CLUSTER.USER| > |Tez|CLUSTER.USER| > |File browser|CLUSTER.USER| > |Zepplin|CLUSTER.USER| > |Capacity Scheduler|CLUSTER.ADMINISTRATOR| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19036) Add default roles to auto created views
[ https://issues.apache.org/jira/browse/AMBARI-19036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19036: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Add default roles to auto created views > --- > > Key: AMBARI-19036 > URL: https://issues.apache.org/jira/browse/AMBARI-19036 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-19036.trunk.2.patch, AMBARI-19036.trunk.3.patch, > AMBARI-19036.trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Add the following roles to auto instances > ||View||Role|| > |Pig|CLUSTER.USER| > |Hive|CLUSTER.USER| > |Tez|CLUSTER.USER| > |File browser|CLUSTER.USER| > |Zepplin|CLUSTER.USER| > |Capacity Scheduler|CLUSTER.ADMINISTRATOR| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19059) Falcon quicklinks combobox is absent
[ https://issues.apache.org/jira/browse/AMBARI-19059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722875#comment-15722875 ] Hudson commented on AMBARI-19059: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6156 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6156/]) AMBARI-19059 Falcon quicklinks combobox is absent (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=431d2659c67f7c07fe704b67eded4f83fe30d25a]) * (add) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml > Falcon quicklinks combobox is absent > > > Key: AMBARI-19059 > URL: https://issues.apache.org/jira/browse/AMBARI-19059 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-19059.patch, screenshot-1.png > > > Falcon quicklinks combobox is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19067) Special characters break creating user homes
[ https://issues.apache.org/jira/browse/AMBARI-19067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722775#comment-15722775 ] Hudson commented on AMBARI-19067: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6155 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6155/]) AMBARI-19067. Special characters break creating user homes (Laszlo (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cac20e090151785edf2b8176d9ac0bddb1adc86f]) * (edit) ambari-server/src/main/resources/scripts/post-user-creation-hook.sh > Special characters break creating user homes > > > Key: AMBARI-19067 > URL: https://issues.apache.org/jira/browse/AMBARI-19067 > Project: Ambari > Issue Type: Bug >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-19067.trunk.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > The initial implementation of the post user creation script generates a json > from the csv passed to it to create user home folders in bulk. > If usernames contain special characters like quotes etc .. the generated json > input file gets broken. > The fix is to escape usernames while generating the json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18065) Change Ranger Admin start script to setup db for ranger
[ https://issues.apache.org/jira/browse/AMBARI-18065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723062#comment-15723062 ] Hudson commented on AMBARI-18065: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #456 (See [https://builds.apache.org/job/Ambari-branch-2.5/456/]) AMBARI-18065. Change Ranger Admin start script to setup db for ranger (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cae5008984d6f45385d8962d35aff1a7f8ea059d]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * (add) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-secured.json * (add) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (add) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-default.json * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py > Change Ranger Admin start script to setup db for ranger > --- > > Key: AMBARI-18065 > URL: https://issues.apache.org/jira/browse/AMBARI-18065 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18065.patch > > > When using option 'blueprint.skip_install_tasks' to skip install tasks on a > preconfigured environment, Ranger Admin start is failing due to missing > ranger db configs because Ranger db is only configured in INSTALL phase. DB > setup should be moved to configure method so that start request would setup > db as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19086) LDAP sync creates group with local type
[
https://issues.apache.org/jira/browse/AMBARI-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722777#comment-15722777
]
Hadoop QA commented on AMBARI-19086:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841763/AMBARI-19086.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9526//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9526//console
This message is automatically generated.
> LDAP sync creates group with local type
> ---
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups
> order by group_name;
> group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo | LOCAL | 1
> 2 | ambari| LOCAL | 0
>72 | ambari-server | LOCAL | 1
>81 | ams | LOCAL | 1
>60 | atlas | LOCAL | 1
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[
https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722896#comment-15722896
]
Hadoop QA commented on AMBARI-19075:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841752/AMBARI-19075.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-portal ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9527//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9527//console
This message is automatically generated.
> Cookie management for Ambari LogSearch Integration
> --
>
> Key: AMBARI-19075
> URL: https://issues.apache.org/jira/browse/AMBARI-19075
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19075.patch
>
>
> Ambari server opens a lot of sessions with LogSearch Portal, because the
> integration code does not contain any session handling
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-19074:
---
Attachment: AMBARI-19074.patch
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-19074:
---
Status: Patch Available (was: Open)
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs
[ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722774#comment-15722774 ] Hudson commented on AMBARI-19058: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6155 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6155/]) AMBARI-19058. Perf: Deploy 3000 Agent cluster and find perf bugs. Part (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08342b3cb268481e5033c99cbf418f123e509327]) * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > Perf: Deploy 3000 Agent cluster and find perf bugs > -- > > Key: AMBARI-19058 > URL: https://issues.apache.org/jira/browse/AMBARI-19058 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-19058_part1.patch > > > Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and > start finding perf bugs in the following areas. > Agent registration (batches of 600 at a time are still very slow) > Alerts > Commands like starting/restarting/rolling restart, etc. > Memory leaks after letting it run for a week? > We may need to also run a memory profiler on the java process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18065) Change Ranger Admin start script to setup db for ranger
[ https://issues.apache.org/jira/browse/AMBARI-18065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722888#comment-15722888 ] Hudson commented on AMBARI-18065: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6156 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6156/]) AMBARI-18065. Change Ranger Admin start script to setup db for ranger (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f5051dcb7f17f0e26fed9e70eef35a3758a35e60]) * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py * (add) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-default.json * (add) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-secured.json * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (add) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json > Change Ranger Admin start script to setup db for ranger > --- > > Key: AMBARI-18065 > URL: https://issues.apache.org/jira/browse/AMBARI-18065 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18065.patch > > > When using option 'blueprint.skip_install_tasks' to skip install tasks on a > preconfigured environment, Ranger Admin start is failing due to missing > ranger db configs because Ranger db is only configured in INSTALL phase. DB > setup should be moved to configure method so that start request would setup > db as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19082) Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and added a port of -1
[
https://issues.apache.org/jira/browse/AMBARI-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722965#comment-15722965
]
Hadoop QA commented on AMBARI-19082:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841775/AMBARI-19082.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9529//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9529//console
This message is automatically generated.
> Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and
> added a port of -1
> --
>
> Key: AMBARI-19082
> URL: https://issues.apache.org/jira/browse/AMBARI-19082
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19082.patch
>
>
> After upgrade some properties has port number "-1".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19059) Falcon quicklinks combobox is absent
[ https://issues.apache.org/jira/browse/AMBARI-19059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723061#comment-15723061 ] Hudson commented on AMBARI-19059: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #456 (See [https://builds.apache.org/job/Ambari-branch-2.5/456/]) AMBARI-19059 Falcon quicklinks combobox is absent (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a0b0a053f3e8e4160f13d53c25e6415c80d3ba73]) * (add) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml > Falcon quicklinks combobox is absent > > > Key: AMBARI-19059 > URL: https://issues.apache.org/jira/browse/AMBARI-19059 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-19059.patch, screenshot-1.png > > > Falcon quicklinks combobox is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19084) Custom property added to the Notification settings appears twice
[ https://issues.apache.org/jira/browse/AMBARI-19084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722882#comment-15722882 ] Hudson commented on AMBARI-19084: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6156 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6156/]) AMBARI-19084. Custom property added to the Notification settings appears (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b2d2ef1689d5434c20d6a791ace598f58742605a]) * (edit) ambari-web/app/templates/common/configs/notifications_configs.hbs * (edit) ambari-web/app/views/common/configs/custom_category_views/notification_configs_view.js * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js > Custom property added to the Notification settings appears twice > > > Key: AMBARI-19084 > URL: https://issues.apache.org/jira/browse/AMBARI-19084 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19084.patch > > > * Proceed to the step7 > * Open MISC tab > * Add custom property to the Notifications-section > *AR* New property appears twice > *ER* New property appears once -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19086) LDAP sync creates groups with "Local" type
[
https://issues.apache.org/jira/browse/AMBARI-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19086:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/a00c] and
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/7492e65f].
> LDAP sync creates groups with "Local" type
> --
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups
> order by group_name;
> group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo | LOCAL | 1
> 2 | ambari| LOCAL | 0
>72 | ambari-server | LOCAL | 1
>81 | ams | LOCAL | 1
>60 | atlas | LOCAL | 1
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
Vivek Rathod created AMBARI-19089: - Summary: Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search Key: AMBARI-19089 URL: https://issues.apache.org/jira/browse/AMBARI-19089 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19082) Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and added a port of -1
[ https://issues.apache.org/jira/browse/AMBARI-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19082: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and > added a port of -1 > -- > > Key: AMBARI-19082 > URL: https://issues.apache.org/jira/browse/AMBARI-19082 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19082.patch > > > After upgrade some properties has port number "-1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15623) Support distributed aggregation for multiple AMS instances
[ https://issues.apache.org/jira/browse/AMBARI-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15623: --- Affects Version/s: 2.5.0 > Support distributed aggregation for multiple AMS instances > -- > > Key: AMBARI-15623 > URL: https://issues.apache.org/jira/browse/AMBARI-15623 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Attachments: AMBARI-15623.patch > > > Tasks: > Support "distributed" mode in AMS, this implies following changes to the > collector service: > - Collectors discover each other > - Add a service to discover all collector by knowing any one > - Aggregation functions are distributed among collectors automatically with > failover tolerance > - Save checkpoint data in Zookeeper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18265) Make sure AMS embedded works after AMS HA changes
[ https://issues.apache.org/jira/browse/AMBARI-18265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18265: --- Fix Version/s: (was: trunk) 2.5.0 > Make sure AMS embedded works after AMS HA changes > - > > Key: AMBARI-18265 > URL: https://issues.apache.org/jira/browse/AMBARI-18265 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-18265.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18199:
---
Fix Version/s: (was: trunk)
2.5.0
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18199.patch, AMBARI-18199_2.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17726) ArrayIndexOutOfBounds exception thrown on shard calculation
[
https://issues.apache.org/jira/browse/AMBARI-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17726:
---
Affects Version/s: 2.5.0
> ArrayIndexOutOfBounds exception thrown on shard calculation
> ---
>
> Key: AMBARI-17726
> URL: https://issues.apache.org/jira/browse/AMBARI-17726
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-17726.patch
>
>
> {code}
> java.lang.ArrayIndexOutOfBoundsException: -1
> at java.util.ArrayList.elementData(ArrayList.java:418)
> at java.util.ArrayList.get(ArrayList.java:431)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricSinkWriteShardHostnameHashingStrategy.findCollectorShard(MetricSinkWriteShardHostnameHashingStrategy.java:40)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:371)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:368)
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:192)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:380)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18199:
---
Affects Version/s: (was: trunk)
2.5.0
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18199.patch, AMBARI-18199_2.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign requested address
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17716) AMS HA not working in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17716:
---
Affects Version/s: 2.5.0
> AMS HA not working in secure cluster
>
>
> Key: AMBARI-17716
> URL: https://issues.apache.org/jira/browse/AMBARI-17716
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-17716.patch
>
>
> Helix not able to connect to Zk while starting up.
> {code}
> 2016-07-13 17:56:41,263 INFO org.apache.helix.manager.zk.ZKHelixManager:
> KeeperState: SyncConnected, zookeeper:State:CONNECTED Timeout:3
> sessionid:0x355e190123e001d local:/10.240.0.32:54434
> remoteserver:ambari-sid-3.c.pramod-thangali.internal/10.240.0.30:2181
> lastZxid:8589
> 935298 xid:9 sent:9 recv:11 queuedpkts:0 pendingresp:0 queuedevents:0
> 2016-07-13 17:57:41,264 ERROR org.apache.helix.manager.zk.ZKHelixManager:
> fail to connect zkserver:
> ambari-sid-1.c.pramod-thangali.internal:2181,ambari-sid-2.c.pramod-thangali.internal:2181,ambari-sid-3.c.pramod-thangali.internal:2181
> in 6ms. expiredSessionId: null, clusterName: ambari-metrics-cluster
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17726) ArrayIndexOutOfBounds exception thrown on shard calculation
[
https://issues.apache.org/jira/browse/AMBARI-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17726:
---
Fix Version/s: (was: trunk)
2.5.0
> ArrayIndexOutOfBounds exception thrown on shard calculation
> ---
>
> Key: AMBARI-17726
> URL: https://issues.apache.org/jira/browse/AMBARI-17726
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-17726.patch
>
>
> {code}
> java.lang.ArrayIndexOutOfBoundsException: -1
> at java.util.ArrayList.elementData(ArrayList.java:418)
> at java.util.ArrayList.get(ArrayList.java:431)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricSinkWriteShardHostnameHashingStrategy.findCollectorShard(MetricSinkWriteShardHostnameHashingStrategy.java:40)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:371)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:368)
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:192)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:380)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19082) Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and added a port of -1
[ https://issues.apache.org/jira/browse/AMBARI-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723573#comment-15723573 ] Hudson commented on AMBARI-19082: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #459 (See [https://builds.apache.org/job/Ambari-branch-2.5/459/]) AMBARI-19082. Ambari Server upgrade from 2.0.2 to 2.2.2 changed the (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=655ec87d24c99c97a19e98ea1f1d7f6ddc300ce3]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java > Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and > added a port of -1 > -- > > Key: AMBARI-19082 > URL: https://issues.apache.org/jira/browse/AMBARI-19082 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19082.patch > > > After upgrade some properties has port number "-1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
Alejandro Fernandez created AMBARI-19094: Summary: HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes Key: AMBARI-19094 URL: https://issues.apache.org/jira/browse/AMBARI-19094 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 New service definition for YARN/MR in HDP 3.0 TP * Flatten configs, metrics, widgets, kerberos * Break up Stack Advisor into Service Advisor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
Alejandro Fernandez created AMBARI-19093: Summary: HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes Key: AMBARI-19093 URL: https://issues.apache.org/jira/browse/AMBARI-19093 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 New service definition for HDFS in HDP 3.0 TP * Flatten configs, metrics, widgets, kerberos * Break up Stack Advisor into Service Advisor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19082) Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and added a port of -1
[ https://issues.apache.org/jira/browse/AMBARI-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723613#comment-15723613 ] Hudson commented on AMBARI-19082: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6160 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6160/]) AMBARI-19082. Ambari Server upgrade from 2.0.2 to 2.2.2 changed the (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=edf8ab2432af6b73f73c4ae386ff13c93c6c38c2]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java > Ambari Server upgrade from 2.0.2 to 2.2.2 changed the following configs and > added a port of -1 > -- > > Key: AMBARI-19082 > URL: https://issues.apache.org/jira/browse/AMBARI-19082 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.2.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19082.patch > > > After upgrade some properties has port number "-1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19092) HDP 3.0 support for ZK with configs, kerberos, widgets, metrics, quicklinks, and themes
Alejandro Fernandez created AMBARI-19092: Summary: HDP 3.0 support for ZK with configs, kerberos, widgets, metrics, quicklinks, and themes Key: AMBARI-19092 URL: https://issues.apache.org/jira/browse/AMBARI-19092 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 New service definition for ZK in HDP 3.0 TP * Flatten configs, metrics, widgets, kerberos * Break up Stack Advisor into Service Advisor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19086) LDAP sync creates groups with "Local" type
[
https://issues.apache.org/jira/browse/AMBARI-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723614#comment-15723614
]
Hudson commented on AMBARI-19086:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6160 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6160/])
AMBARI-19086. LDAP sync creates groups with Local type (Attila Doroszla
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a00c54a8063c1728d2f3ba24db04504864da])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/GroupEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java
> LDAP sync creates groups with "Local" type
> --
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups
> order by group_name;
> group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo | LOCAL | 1
> 2 | ambari| LOCAL | 0
>72 | ambari-server | LOCAL | 1
>81 | ams | LOCAL | 1
>60 | atlas | LOCAL | 1
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
Alejandro Fernandez created AMBARI-19098: Summary: HDP 3.0 TP - create Service Advisor for YARN/MR Key: AMBARI-19098 URL: https://issues.apache.org/jira/browse/AMBARI-19098 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. The Service Advisor must encapsulate all of the logic inherited/overwritten from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Attachment: (was: AMBARI-18941.v2.trunk.patch) > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16991) Fix metric sink
[ https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16991: --- Affects Version/s: (was: 2.4.1) 2.5.0 > Fix metric sink > --- > > Key: AMBARI-16991 > URL: https://issues.apache.org/jira/browse/AMBARI-16991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-16991.patch > > > After a recent change the AbstractTimelineMetricsSink class has an abstract > function called getZookeeperQuorum(). If the extending class is returning > null, then the sink is not working (neither does it if it returns a valid > zookeeper connection string). Fixed the first issue, now it is working > without a zookeeper connect string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15623) Support distributed aggregation for multiple AMS instances
[ https://issues.apache.org/jira/browse/AMBARI-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15623: --- Fix Version/s: 2.5.0 > Support distributed aggregation for multiple AMS instances > -- > > Key: AMBARI-15623 > URL: https://issues.apache.org/jira/browse/AMBARI-15623 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.5.0 > > Attachments: AMBARI-15623.patch > > > Tasks: > Support "distributed" mode in AMS, this implies following changes to the > collector service: > - Collectors discover each other > - Add a service to discover all collector by knowing any one > - Aggregation functions are distributed among collectors automatically with > failover tolerance > - Save checkpoint data in Zookeeper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18517: --- Fix Version/s: (was: 3.0.0) 2.5.0 > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16991) Fix metric sink
[ https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16991: --- Fix Version/s: (was: trunk) 2.5.0 > Fix metric sink > --- > > Key: AMBARI-16991 > URL: https://issues.apache.org/jira/browse/AMBARI-16991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-16991.patch > > > After a recent change the AbstractTimelineMetricsSink class has an abstract > function called getZookeeperQuorum(). If the extending class is returning > null, then the sink is not working (neither does it if it returns a valid > zookeeper connection string). Fixed the first issue, now it is working > without a zookeeper connect string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19088) Make sure AMS in embedded mode cannot have more than 1 deployed instance
[ https://issues.apache.org/jira/browse/AMBARI-19088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723666#comment-15723666 ] Hudson commented on AMBARI-19088: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #460 (See [https://builds.apache.org/job/Ambari-branch-2.5/460/]) AMBARI-19088 : Make sure AMS in embedded mode cannot have more than 1 (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5fd60daf16def4aef546ed6c3521501600b3e3ce]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py > Make sure AMS in embedded mode cannot have more than 1 deployed instance > > > Key: AMBARI-19088 > URL: https://issues.apache.org/jira/browse/AMBARI-19088 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19088.patch > > > AMS in embedded mode uses embedded HBase using local Zk and local disk for > data. If there are 2 instances of embedded AMS installed on the cluster, it > can lead to data fragmentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18965) Investigate and reduce AMS HA dependency on Zookeeper.
[ https://issues.apache.org/jira/browse/AMBARI-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723665#comment-15723665 ] Hudson commented on AMBARI-18965: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #460 (See [https://builds.apache.org/job/Ambari-branch-2.5/460/]) AMBARI-18965 : Investigate and reduce AMS HA dependency on Zookeeper. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1c89883e80231a6033160de37e389457ae3d630e]) * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAControllerTest.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/TestApplicationHistoryServer.java * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregator.java * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHATest.java > Investigate and reduce AMS HA dependency on Zookeeper. > -- > > Key: AMBARI-18965 > URL: https://issues.apache.org/jira/browse/AMBARI-18965 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18965-4.patch, AMBARI-18965.patch > > > In AMS embedded mode or distributed mode single collector deployments, we > should try and reduce sink dependency on Zookeeper. In general, we should > investigate how to reduce Zk fallback on single and multi-collector > deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19091: - Summary: HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks (was: HDP 3.0 TP - bootstrap the stack with metainfo, RCO, cluster-env, repos, and hooks) > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > metainfo > Role Command Order > configs in cluster-env > repositories > hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[
https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723783#comment-15723783
]
Hadoop QA commented on AMBARI-18941:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841851/AMBARI-18941.v2.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9535//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9535//console
This message is automatically generated.
> When HS2Interactive is enabled, any hive config change results in a CS queue
> refresh
>
>
> Key: AMBARI-18941
> URL: https://issues.apache.org/jira/browse/AMBARI-18941
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch,
> AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch
>
>
> Ambari keeps refreshing CS queues each time any config is changed in Hive -
> including Hive1 configs. The refresh should happen when the user actually
> changes the capacity scheduler slider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16828) Support round-robin scheduling with failover for Sinks with distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-16828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16828: --- Fix Version/s: (was: trunk) 2.5.0 > Support round-robin scheduling with failover for Sinks with distributed > collector > - > > Key: AMBARI-16828 > URL: https://issues.apache.org/jira/browse/AMBARI-16828 > Project: Ambari > Issue Type: Task > Components: amvari-me >Affects Versions: 2.4.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.5.0 > > Attachments: AMBARI-16828.patch > > > - Initial set of collectors is configured in the configuration files > - Find available collectors by connecting to zookeeper thereafter > - Remember available collectors, refresh this information only when one > collector cannot be reached with a very low frequency of checks, example: > random interval between 10-12 minutes, check if a new collector is available. > Set a low client side zk timeout. > - Round robin the write between the collector choosing the first one at random > - If a write timed out, choose the next available collector, remember the > attempts with the first one > - Set a configurable attempt count for failed connector (default = 3), after > which the failed connector is no longer in the available collectors list. > - The next retry will be triggered after refresh with zookeeper is successful > - If no failed collectors available, zk refresh interval should be chosen > randomly between 1-2 minutes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18171: --- Affects Version/s: (was: trunk) 2.5.0 > AMS, Accumulo, Hive metrics do not show up in AMS HA clusters. > -- > > Key: AMBARI-18171 > URL: https://issues.apache.org/jira/browse/AMBARI-18171 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18171.patch > > > There is an issue in the jinja template that causes the the metrics collector > protocol to be duplicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17457) Modify the AMS stack scripts to support distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-17457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17457: --- Fix Version/s: (was: 3.0.0) 2.5.0 > Modify the AMS stack scripts to support distributed collector > - > > Key: AMBARI-17457 > URL: https://issues.apache.org/jira/browse/AMBARI-17457 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17457.patch, AMBARI-17457_2.patch > > > _Tasks_: > - If collector mode = distributed: > -- Do not start zookeeper and use the zk quorum property to find cluster zk. > -- Start Master and RS as before > -- Add metrics_collectors property to ams-site > -- Add the same to the metrics_monitor.ini file template > - Make changes to the stack advisor: > -- Validate ZK quorum property > -- Set metrics_collectors property in ams-site with comma separated collector > hostnames > -- Validate hbase.rootdir is pointing to HDFS path -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18171: --- Fix Version/s: (was: trunk) 2.5.0 > AMS, Accumulo, Hive metrics do not show up in AMS HA clusters. > -- > > Key: AMBARI-18171 > URL: https://issues.apache.org/jira/browse/AMBARI-18171 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18171.patch > > > There is an issue in the jinja template that causes the the metrics collector > protocol to be duplicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18517: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17458) Add support for distributed collector to Ambari REST API
[ https://issues.apache.org/jira/browse/AMBARI-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17458: --- Fix Version/s: (was: 3.0.0) 2.5.0 > Add support for distributed collector to Ambari REST API > > > Key: AMBARI-17458 > URL: https://issues.apache.org/jira/browse/AMBARI-17458 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17458-3.patch > > > _Tasks_: > - Add a Zookeeper watcher for the AMS znode > - Find available collectors and round-robin the READ calls from > AMSPropertyProvider > - Tolerate failure by switching to available collector -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18518:
---
Fix Version/s: (was: 3.0.0)
2.5.0
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Fix Version/s: (was: 3.0.0) 2.5.0 > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18487-trunk.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs
[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18362: --- Fix Version/s: (was: trunk) 2.5.0 > Update sinks to read multiple collector hostnames from configs > -- > > Key: AMBARI-18362 > URL: https://issues.apache.org/jira/browse/AMBARI-18362 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18362.patch, AMBARI-18362_2.patch, > AMBARI-18362_3.patch > > > Update sinks to read multiple collector hostnames from configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17458) Add support for distributed collector to Ambari REST API
[ https://issues.apache.org/jira/browse/AMBARI-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17458: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Add support for distributed collector to Ambari REST API > > > Key: AMBARI-17458 > URL: https://issues.apache.org/jira/browse/AMBARI-17458 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17458-3.patch > > > _Tasks_: > - Add a Zookeeper watcher for the AMS znode > - Find available collectors and round-robin the READ calls from > AMSPropertyProvider > - Tolerate failure by switching to available collector -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18965) Investigate and reduce AMS HA dependency on Zookeeper.
[ https://issues.apache.org/jira/browse/AMBARI-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18965: --- Attachment: AMBARI-18965-4.patch > Investigate and reduce AMS HA dependency on Zookeeper. > -- > > Key: AMBARI-18965 > URL: https://issues.apache.org/jira/browse/AMBARI-18965 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18965-4.patch, AMBARI-18965.patch > > > In AMS embedded mode or distributed mode single collector deployments, we > should try and reduce sink dependency on Zookeeper. In general, we should > investigate how to reduce Zk fallback on single and multi-collector > deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19090) HDP 3.0 Tech Preview in Ambari 2.5
Alejandro Fernandez created AMBARI-19090: Summary: HDP 3.0 Tech Preview in Ambari 2.5 Key: AMBARI-19090 URL: https://issues.apache.org/jira/browse/AMBARI-19090 Project: Ambari Issue Type: Epic Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 HDP 3.0 Tech Preview for Ambari 2.5 in January Services: HDFS, YARN, MR, ZK Plan: # HDP 3.0 bits for Hadoop core # New stack definition in Ambari # Flatten configs, metrics, widgets, kerberos for the services listed above # Break up Stack Advisor into Service Advisor per service listed above # Testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Attachment: AMBARI-18941.v2.trunk.patch > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Status: Open (was: Patch Available) > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Attachment: AMBARI-18941.v2.branch2.5.patch > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Attachment: AMBARI-18941.v2.trunk.patch > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Status: Patch Available (was: Open) > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Status: Open (was: Patch Available) > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[
https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723687#comment-15723687
]
Hadoop QA commented on AMBARI-18450:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841818/AMBARI-18450.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9533//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9533//console
This message is automatically generated.
> Putting a service or process in Maintenance Mode doesn't take it off of the
> "Restart All Required" list
> ---
>
> Key: AMBARI-18450
> URL: https://issues.apache.org/jira/browse/AMBARI-18450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: amarnathreddy
>Assignee: Vitaly Brodetskyi
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18450.patch
>
>
> Putting a service or process in Maintenance Mode doesn't take it off of the
> "Restart All Required" list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18941) When HS2Interactive is enabled, any hive config change results in a CS queue refresh
[ https://issues.apache.org/jira/browse/AMBARI-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18941: Status: Patch Available (was: Open) > When HS2Interactive is enabled, any hive config change results in a CS queue > refresh > > > Key: AMBARI-18941 > URL: https://issues.apache.org/jira/browse/AMBARI-18941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18941.v0.patch, AMBARI-18941.v1.trunk.patch, > AMBARI-18941.v2.branch2.5.patch, AMBARI-18941.v2.trunk.patch > > > Ambari keeps refreshing CS queues each time any config is changed in Hive - > including Hive1 configs. The refresh should happen when the user actually > changes the capacity scheduler slider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19099) Improve and Fix "Wizard pages" after new guidelines
Xi Wang created AMBARI-19099: Summary: Improve and Fix "Wizard pages" after new guidelines Key: AMBARI-19099 URL: https://issues.apache.org/jira/browse/AMBARI-19099 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 In all wizard steps: 1. should always show completed step markers in green, not grey. Even if those steps were disabled. 2. Summary and review page text line height. 3. In "Assign Master" step, the green labels of components need more padding 4. Wizard menu and content should be divided with a clean line, the line in the red circle is not clean. This is because the background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19039) In stack version, build number should not be mandatory
[ https://issues.apache.org/jira/browse/AMBARI-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723464#comment-15723464 ] Hudson commented on AMBARI-19039: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #458 (See [https://builds.apache.org/job/Ambari-branch-2.5/458/]) AMBARI-19039: In stack version, build number should not be mandatory (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b90b0f8a7fa2445eec220f7987c14488406367c7]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/dynamic_variable_interpretation.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py > In stack version, build number should not be mandatory > -- > > Key: AMBARI-19039 > URL: https://issues.apache.org/jira/browse/AMBARI-19039 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, > AMBARI-19039_v1.patch > > > In stack version, build number should not be mandatory. mapreduce.tar.gz > file does not get copied during blueprint deployment when stack version does > not have build version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19039) In stack version, build number should not be mandatory
[ https://issues.apache.org/jira/browse/AMBARI-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723481#comment-15723481 ] Hudson commented on AMBARI-19039: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6159 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6159/]) AMBARI-19039: In stack version, build number should not be mandatory (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b5122e258bfe5a2e56511eb9dd29a70cf1260a9c]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/dynamic_variable_interpretation.py > In stack version, build number should not be mandatory > -- > > Key: AMBARI-19039 > URL: https://issues.apache.org/jira/browse/AMBARI-19039 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, > AMBARI-19039_v1.patch > > > In stack version, build number should not be mandatory. mapreduce.tar.gz > file does not get copied during blueprint deployment when stack version does > not have build version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.
[
https://issues.apache.org/jira/browse/AMBARI-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18012:
---
Fix Version/s: (was: trunk)
2.5.0
> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
> - Unable to conne
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18265) Make sure AMS embedded works after AMS HA changes
[ https://issues.apache.org/jira/browse/AMBARI-18265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18265: --- Affects Version/s: (was: trunk) 2.5.0 > Make sure AMS embedded works after AMS HA changes > - > > Key: AMBARI-18265 > URL: https://issues.apache.org/jira/browse/AMBARI-18265 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-18265.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18170: --- Fix Version/s: (was: trunk) 2.5.0 > Kafka Metrics do not show up in AMS HA enabled cluster > -- > > Key: AMBARI-18170 > URL: https://issues.apache.org/jira/browse/AMBARI-18170 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18170-2.patch > > > No kafka metrics are seen in trunk deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18170: --- Affects Version/s: (was: trunk) 2.5.0 > Kafka Metrics do not show up in AMS HA enabled cluster > -- > > Key: AMBARI-18170 > URL: https://issues.apache.org/jira/browse/AMBARI-18170 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18170-2.patch > > > No kafka metrics are seen in trunk deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17457) Modify the AMS stack scripts to support distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-17457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17457: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Modify the AMS stack scripts to support distributed collector > - > > Key: AMBARI-17457 > URL: https://issues.apache.org/jira/browse/AMBARI-17457 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17457.patch, AMBARI-17457_2.patch > > > _Tasks_: > - If collector mode = distributed: > -- Do not start zookeeper and use the zk quorum property to find cluster zk. > -- Start Master and RS as before > -- Add metrics_collectors property to ams-site > -- Add the same to the metrics_monitor.ini file template > - Make changes to the stack advisor: > -- Validate ZK quorum property > -- Set metrics_collectors property in ams-site with comma separated collector > hostnames > -- Validate hbase.rootdir is pointing to HDFS path -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.
[
https://issues.apache.org/jira/browse/AMBARI-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18012:
---
Affects Version/s: (was: trunk)
2.5.0
> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
> - Unable to conne
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17716) AMS HA not working in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17716:
---
Fix Version/s: (was: trunk)
2.5.0
> AMS HA not working in secure cluster
>
>
> Key: AMBARI-17716
> URL: https://issues.apache.org/jira/browse/AMBARI-17716
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-17716.patch
>
>
> Helix not able to connect to Zk while starting up.
> {code}
> 2016-07-13 17:56:41,263 INFO org.apache.helix.manager.zk.ZKHelixManager:
> KeeperState: SyncConnected, zookeeper:State:CONNECTED Timeout:3
> sessionid:0x355e190123e001d local:/10.240.0.32:54434
> remoteserver:ambari-sid-3.c.pramod-thangali.internal/10.240.0.30:2181
> lastZxid:8589
> 935298 xid:9 sent:9 recv:11 queuedpkts:0 pendingresp:0 queuedevents:0
> 2016-07-13 17:57:41,264 ERROR org.apache.helix.manager.zk.ZKHelixManager:
> fail to connect zkserver:
> ambari-sid-1.c.pramod-thangali.internal:2181,ambari-sid-2.c.pramod-thangali.internal:2181,ambari-sid-3.c.pramod-thangali.internal:2181
> in 6ms. expiredSessionId: null, clusterName: ambari-metrics-cluster
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19088) Make sure AMS in embedded mode cannot have more than 1 deployed instance
[ https://issues.apache.org/jira/browse/AMBARI-19088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19088: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Make sure AMS in embedded mode cannot have more than 1 deployed instance > > > Key: AMBARI-19088 > URL: https://issues.apache.org/jira/browse/AMBARI-19088 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19088.patch > > > AMS in embedded mode uses embedded HBase using local Zk and local disk for > data. If there are 2 instances of embedded AMS installed on the cluster, it > can lead to data fragmentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19086) LDAP sync creates groups with "Local" type
[
https://issues.apache.org/jira/browse/AMBARI-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723575#comment-15723575
]
Hudson commented on AMBARI-19086:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #459 (See
[https://builds.apache.org/job/Ambari-branch-2.5/459/])
AMBARI-19086. LDAP sync creates groups with Local type (Attila Doroszla
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7492e65f7374cd7b01e9b1f2dd0e5b21a1d10ff1])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/GroupEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
> LDAP sync creates groups with "Local" type
> --
>
> Key: AMBARI-19086
> URL: https://issues.apache.org/jira/browse/AMBARI-19086
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-19086.patch
>
>
> STR:
> {noformat}
> ambari-server setup-ldap
> ambari-server restart
> ambari-server sync-ldap --all
> {noformat}
> Result: users synced from LDAP are created with type LDAP, but groups are
> created with type LOCAL:
> {noformat}
> ambari=> select group_id, group_name, group_type, ldap_group from groups
> order by group_name;
> group_id |group_name | group_type | ldap_group
> --+---++
>59 | accumulo | LOCAL | 1
> 2 | ambari| LOCAL | 0
>72 | ambari-server | LOCAL | 1
>81 | ams | LOCAL | 1
>60 | atlas | LOCAL | 1
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
[
https://issues.apache.org/jira/browse/AMBARI-19074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723574#comment-15723574
]
Hudson commented on AMBARI-19074:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #459 (See
[https://builds.apache.org/job/Ambari-branch-2.5/459/])
AMBARI-19074. Host-Ordered: Empty groups are returned for Downgrade (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0693f552b21e86eb4df11c3f34c5ef6ce2526289])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/UpgradePack.java
> Host-Ordered: Empty groups are returned for Downgrade
> -
>
> Key: AMBARI-19074
> URL: https://issues.apache.org/jira/browse/AMBARI-19074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19074.patch
>
>
> When issuing a downgrade for HOU, the server is responding with an error:
> {noformat}
> org.apache.ambari.server.AmbariException: There are no groupings available
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19095) HDP 3.0 flatten Role Command Order and update service versions in metainfo.xml
Alejandro Fernandez created AMBARI-19095: Summary: HDP 3.0 flatten Role Command Order and update service versions in metainfo.xml Key: AMBARI-19095 URL: https://issues.apache.org/jira/browse/AMBARI-19095 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Flatten out Role Command Order for HDP 3.0 TP based on previous stacks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK
Alejandro Fernandez created AMBARI-19096: Summary: HDP 3.0 TP - create Service Advisor for ZK Key: AMBARI-19096 URL: https://issues.apache.org/jira/browse/AMBARI-19096 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Create a Service Advisor script for ZK in HDP 3.0 Tech Preview. The Service Advisor must encapsulate all of the logic inherited/overwritten from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
Alejandro Fernandez created AMBARI-19097: Summary: HDP 3.0 TP - create Service Advisor for HDFS Key: AMBARI-19097 URL: https://issues.apache.org/jira/browse/AMBARI-19097 Project: Ambari Issue Type: Story Components: stacks Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview. The Service Advisor must encapsulate all of the logic inherited/overwritten from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[
https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723785#comment-15723785
]
Hadoop QA commented on AMBARI-19091:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841835/AMBARI-19091.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9536//console
This message is automatically generated.
> HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
> -
>
> Key: AMBARI-19091
> URL: https://issues.apache.org/jira/browse/AMBARI-19091
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19091.patch
>
>
> Bootstrap the HDP 3.0 Tech Preview stack with the following
> metainfo
> Role Command Order
> configs in cluster-env
> repositories
> hooks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19089: -- Attachment: Screen Shot 2016-12-05 at 1.47.33 PM.png > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 > Return to search > > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: Screen Shot 2016-12-05 at 1.47.33 PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19039) In stack version, build number should not be mandatory
[ https://issues.apache.org/jira/browse/AMBARI-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723467#comment-15723467 ] Amruta Borkar commented on AMBARI-19039: Thank you Di. > In stack version, build number should not be mandatory > -- > > Key: AMBARI-19039 > URL: https://issues.apache.org/jira/browse/AMBARI-19039 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19039.patch, AMBARI-19039_v1.patch, > AMBARI-19039_v1.patch > > > In stack version, build number should not be mandatory. mapreduce.tar.gz > file does not get copied during blueprint deployment when stack version does > not have build version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17456) Support round-robin scheduling with failover for monitors with distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17456: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Support round-robin scheduling with failover for monitors with distributed > collector > > > Key: AMBARI-17456 > URL: https://issues.apache.org/jira/browse/AMBARI-17456 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17456-2.patch, AMBARI-17456.patch, > AMBARI-17456_2.patch > > > _Tasks_: > - Monitors get a fix set of collector nodes, every restart gets a refresh > of available collector nodes > - Round-robin the write for available collectors > - Use failed attempts to blacklist collectors > - Use configurable interval to white-list already black-listed collectors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18518:
---
Affects Version/s: (was: 3.0.0)
2.5.0
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17456) Support round-robin scheduling with failover for monitors with distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17456: --- Fix Version/s: (was: 3.0.0) 2.5.0 > Support round-robin scheduling with failover for monitors with distributed > collector > > > Key: AMBARI-17456 > URL: https://issues.apache.org/jira/browse/AMBARI-17456 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17456-2.patch, AMBARI-17456.patch, > AMBARI-17456_2.patch > > > _Tasks_: > - Monitors get a fix set of collector nodes, every restart gets a refresh > of available collector nodes > - Round-robin the write for available collectors > - Use failed attempts to blacklist collectors > - Use configurable interval to white-list already black-listed collectors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18487-trunk.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15901) Ambari Metrics System Distributed mode - multiple Collectors
[ https://issues.apache.org/jira/browse/AMBARI-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15901: --- Fix Version/s: 2.5.0 > Ambari Metrics System Distributed mode - multiple Collectors > > > Key: AMBARI-15901 > URL: https://issues.apache.org/jira/browse/AMBARI-15901 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.5.0 > > Attachments: Metrics-HA-Arch.png > > > UX: > - Configure AMS in distributed mode, write to distributed FS supported by > HBase, example: HDFS / WASB, etc > - Add a new Metrics Collector by navigating to a host and selecting the > component from dropdown > - Same can be achieved by adding a Collector from INSTALL wizard or from a > blueprint > - No additional configuration is required -- This message was sent by Atlassian JIRA (v6.3.4#6332)
