[jira] [Commented] (AMBARI-11383) Enable async audit log and unfair lock by default in HDP
[
https://issues.apache.org/jira/browse/AMBARI-11383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395140#comment-15395140
]
GAO Rui commented on AMBARI-11383:
--
Thanks for your contribution, [~sumitmohanty] .
Could you share your opinion about why make default value of
dfs.namenode.fslock.fair as false?
In current HDFS source code, the default value is set as true:
{code}
boolean fair = conf.getBoolean("dfs.namenode.fslock.fair", true);
LOG.info("fsLock is fair:" + fair);
fsLock = new FSNamesystemLock(fair);
{code}
And, according to the following document, for a busy cluster(where both write
and read operations concurrency are very high), it's very easy to cause the
problem of writers can never get the lock. Because, once one reader acquire the
read lock and mounts of reader keep acquiring read lock, the writers wound got
the chance to acquire write lock at all.
https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/locks/ReentrantReadWriteLock.html
{code}
Non-fair mode (default)
When constructed as non-fair (the default), the order of entry to the
read and write lock is unspecified, subject to reentrancy constraints. A
nonfair lock that is continuously contended may indefinitely postpone one or
more reader or writer threads, but will normally have higher throughput than a
fair lock.
Fair mode
When constructed as fair, threads contend for entry using an
approximately arrival-order policy. When the currently held lock is released
either the longest-waiting single writer thread will be assigned the write
lock, or if there is a group of reader threads waiting longer than all waiting
writer threads, that group will be assigned the read lock.
A thread that tries to acquire a fair read lock (non-reentrantly) will
block if either the write lock is held, or there is a waiting writer thread.
The thread will not acquire the read lock until after the oldest currently
waiting writer thread has acquired and released the write lock. Of course, if a
waiting writer abandons its wait, leaving one or more reader threads as the
longest waiters in the queue with the write lock free, then those readers will
be assigned the read lock.
A thread that tries to acquire a fair write lock (non-reentrantly) will
block unless both the read lock and write lock are free (which implies there
are no waiting threads). (Note that the non-blocking
ReentrantReadWriteLock.ReadLock.tryLock() and
ReentrantReadWriteLock.WriteLock.tryLock() methods do not honor this fair
setting and will acquire the lock if it is possible, regardless of waiting
threads.)
{code}
> Enable async audit log and unfair lock by default in HDP
>
>
> Key: AMBARI-11383
> URL: https://issues.apache.org/jira/browse/AMBARI-11383
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.1.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11383.patch
>
>
> Set the corresponding conf properties:
> dfs.namenode.audit.log.async=true
> dfs.namenode.fslock.fair=false
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17904) Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395021#comment-15395021
]
Hudson commented on AMBARI-17904:
-
FAILURE: Integrated in Ambari-trunk-Commit #5396 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5396/])
AMBARI-17904. Downgrade Schedules Manual & Configuration Tasks For (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3ef40a40869e747c4f34b713bc3f3c3b65ca46b1])
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
> Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't
> Upgrade
>
>
> Key: AMBARI-17904
> URL: https://issues.apache.org/jira/browse/AMBARI-17904
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17904.patch
>
>
> STR:
> - Install HDP 2.4 with Storm and start an EU to 2.5
> - On the first manual task, click downgrade right away
> You'll notice that in addition to the 2 or 3 "normal" downgrade tasks, Storm
> is also scheduled. There are 2 manual tasks which are scheduled for
> SUPERVISOR and DRPC_SERVER.
> It looks like the cause of this is a bug in the {{TaskWrapperBuilder}} which
> schedules tasks for {{MANUAL}} and {{CONFIGURE}} regardless of whether any
> hosts resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17909) AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation
[ https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17909: -- Attachment: AMBARI-17909-v2.patch > AMS Storm Sink: apply change of Storm metrics improvement - worker level > aggregation > > > Key: AMBARI-17909 > URL: https://issues.apache.org/jira/browse/AMBARI-17909 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim >Priority: Blocker > Attachments: AMBARI-17909-v1.patch, AMBARI-17909-v2.patch > > > Abstraction: > This issue is for following up changes on STORM-2006: Storm metrics feature > improvement: support per-worker level metrics aggregation. > Details: > With recent patches for AMS and AMS Storm sink, AMS stores task level metrics > from Storm, and relevant dashboards can be configured via Grafana. > But we found that it incurs too many kinds of metrics and also too many data > points published to AMS because even a topology can have lots of tasks. > In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm > sink and relevant Storm configurations to be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17904) Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-17904:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't
> Upgrade
>
>
> Key: AMBARI-17904
> URL: https://issues.apache.org/jira/browse/AMBARI-17904
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17904.patch
>
>
> STR:
> - Install HDP 2.4 with Storm and start an EU to 2.5
> - On the first manual task, click downgrade right away
> You'll notice that in addition to the 2 or 3 "normal" downgrade tasks, Storm
> is also scheduled. There are 2 manual tasks which are scheduled for
> SUPERVISOR and DRPC_SERVER.
> It looks like the cause of this is a bug in the {{TaskWrapperBuilder}} which
> schedules tasks for {{MANUAL}} and {{CONFIGURE}} regardless of whether any
> hosts resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17909) AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation
[ https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17909: -- Status: Patch Available (was: In Progress) While patch is made against trunk, it can be easily applied to 2.4 branch. Please ping/mention me if it makes conflict for branch-2.4. > AMS Storm Sink: apply change of Storm metrics improvement - worker level > aggregation > > > Key: AMBARI-17909 > URL: https://issues.apache.org/jira/browse/AMBARI-17909 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim >Priority: Blocker > Attachments: AMBARI-17909-v1.patch > > > Abstraction: > This issue is for following up changes on STORM-2006: Storm metrics feature > improvement: support per-worker level metrics aggregation. > Details: > With recent patches for AMS and AMS Storm sink, AMS stores task level metrics > from Storm, and relevant dashboards can be configured via Grafana. > But we found that it incurs too many kinds of metrics and also too many data > points published to AMS because even a topology can have lots of tasks. > In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm > sink and relevant Storm configurations to be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17909) AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation
[ https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17909: -- Attachment: AMBARI-17909-v1.patch > AMS Storm Sink: apply change of Storm metrics improvement - worker level > aggregation > > > Key: AMBARI-17909 > URL: https://issues.apache.org/jira/browse/AMBARI-17909 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim >Priority: Blocker > Attachments: AMBARI-17909-v1.patch > > > Abstraction: > This issue is for following up changes on STORM-2006: Storm metrics feature > improvement: support per-worker level metrics aggregation. > Details: > With recent patches for AMS and AMS Storm sink, AMS stores task level metrics > from Storm, and relevant dashboards can be configured via Grafana. > But we found that it incurs too many kinds of metrics and also too many data > points published to AMS because even a topology can have lots of tasks. > In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm > sink and relevant Storm configurations to be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17909) AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation
Jungtaek Lim created AMBARI-17909: - Summary: AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation Key: AMBARI-17909 URL: https://issues.apache.org/jira/browse/AMBARI-17909 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Jungtaek Lim Assignee: Jungtaek Lim Priority: Blocker Abstraction: This issue is for following up changes on STORM-2006: Storm metrics feature improvement: support per-worker level metrics aggregation. Details: With recent patches for AMS and AMS Storm sink, AMS stores task level metrics from Storm, and relevant dashboards can be configured via Grafana. But we found that it incurs too many kinds of metrics and also too many data points published to AMS because even a topology can have lots of tasks. In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm sink and relevant Storm configurations to be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17841) UI does not allow to delete service is some host components are in INSTALLED_FAILED state
[ https://issues.apache.org/jira/browse/AMBARI-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17841: Status: Patch Available (was: Reopened) > UI does not allow to delete service is some host components are in > INSTALLED_FAILED state > - > > Key: AMBARI-17841 > URL: https://issues.apache.org/jira/browse/AMBARI-17841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17841.2.patch, AMBARI-17841.patch > > > *STR:* > # Deploy a service ad abort installation in the middle in a way such that > some of its slave host components remains in INSTALLED_FAILED state but no all > # Try deleting service > *Expected Result:* UI should allow service deletion as API allows it in this > scenario > *Actual Result:* UI shows a warning popup in green color and does not let > user delete a service. screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17841) UI does not allow to delete service is some host components are in INSTALLED_FAILED state
[ https://issues.apache.org/jira/browse/AMBARI-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17841: Attachment: AMBARI-17841.2.patch > UI does not allow to delete service is some host components are in > INSTALLED_FAILED state > - > > Key: AMBARI-17841 > URL: https://issues.apache.org/jira/browse/AMBARI-17841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17841.2.patch, AMBARI-17841.patch > > > *STR:* > # Deploy a service ad abort installation in the middle in a way such that > some of its slave host components remains in INSTALLED_FAILED state but no all > # Try deleting service > *Expected Result:* UI should allow service deletion as API allows it in this > scenario > *Actual Result:* UI shows a warning popup in green color and does not let > user delete a service. screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17841) UI does not allow to delete service is some host components are in INSTALLED_FAILED state
[ https://issues.apache.org/jira/browse/AMBARI-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly reopened AMBARI-17841: - Reverted the patch and Reopening the issue as this patch was causing other issues while deleting service > UI does not allow to delete service is some host components are in > INSTALLED_FAILED state > - > > Key: AMBARI-17841 > URL: https://issues.apache.org/jira/browse/AMBARI-17841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17841.patch > > > *STR:* > # Deploy a service ad abort installation in the middle in a way such that > some of its slave host components remains in INSTALLED_FAILED state but no all > # Try deleting service > *Expected Result:* UI should allow service deletion as API allows it in this > scenario > *Actual Result:* UI shows a warning popup in green color and does not let > user delete a service. screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394715#comment-15394715 ] Hudson commented on AMBARI-16027: - FAILURE: Integrated in Ambari-trunk-Commit #5394 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5394/]) AMBARI-16027. Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking - UT (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=85a685eefc4d6d3f29e24c7dd281529519157817]) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394714#comment-15394714 ] Hudson commented on AMBARI-17694: - FAILURE: Integrated in Ambari-trunk-Commit #5394 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5394/]) AMBARI-17694. Kafka listeners property does not show SASL_PLAINTEXT (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=124f48ef899fddb6bdb96ebea9aa3a6a1a6adbca]) * ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/VariableReplacementHelper.java * ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/VariableReplacementHelperTest.java * ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka.py * ambari-server/src/main/resources/common-services/KAFKA/0.9.0/kerberos.json > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17908) Ensure the supplied hostname is a valid hostname when signing agent-side host certs
Robert Levas created AMBARI-17908:
-
Summary: Ensure the supplied hostname is a valid hostname when
signing agent-side host certs
Key: AMBARI-17908
URL: https://issues.apache.org/jira/browse/AMBARI-17908
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.2.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.4.0
Ensure the supplied hostname is a valid hostname when signing agent-side host
certs via the following REST API call:
{noformat}
POST /certs/:HOSTNAME
{noformat}
This is a validity check to make sure only valid hostname are handled.
The following industry accepted regular expression maybe use to validate
hostnames:
{noformat}
^(?:(?:[a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\-\_]*[a-zA-Z0-9])\.)*(?:[A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\-\_]*[A-Za-z0-9])$
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17907) On AMS collector move the webapp address does not change
[
https://issues.apache.org/jira/browse/AMBARI-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-17907:
Status: Patch Available (was: Open)
> On AMS collector move the webapp address does not change
>
>
> Key: AMBARI-17907
> URL: https://issues.apache.org/jira/browse/AMBARI-17907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17907.v0.patch
>
>
> Move collector to a different host. Collector start fails because following
> property is not modified:
> {quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17907) On AMS collector move the webapp address does not change
[
https://issues.apache.org/jira/browse/AMBARI-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-17907:
Attachment: AMBARI-17907.v0.patch
Modified unit test.
Local ambari-web test passed.
29371 tests complete (25 seconds)
154 tests pending
Manual testing done.
> On AMS collector move the webapp address does not change
>
>
> Key: AMBARI-17907
> URL: https://issues.apache.org/jira/browse/AMBARI-17907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17907.v0.patch
>
>
> Move collector to a different host. Collector start fails because following
> property is not modified:
> {quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17907) On AMS collector move the webapp address does not change
Zhe (Joe) Wang created AMBARI-17907:
---
Summary: On AMS collector move the webapp address does not change
Key: AMBARI-17907
URL: https://issues.apache.org/jira/browse/AMBARI-17907
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.2.2
Reporter: Zhe (Joe) Wang
Assignee: Zhe (Joe) Wang
Fix For: 2.4.0
Move collector to a different host. Collector start fails because following
property is not modified:
{quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394531#comment-15394531 ] Hudson commented on AMBARI-17782: - FAILURE: Integrated in Ambari-trunk-Commit #5393 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5393/]) AMBARI-17782. Config changes for Atlas in HDP 2.5 related to (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e424b5b538537ea16f7d8cc24899c7a4ff5864a0]) * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * ambari-common/src/main/python/ambari_commons/constants.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/SQOOP/kerberos.json * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-atlas-application.properties.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/SQOOP/configuration/sqoop-site.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * ambari-server/src/main/resources/common-services/STORM/1.0.1/configuration/storm-site.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py * ambari-server/src/test/python/stacks/2.5/configs/default.json * ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-site.xml * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-atlas-application.properties.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/metainfo.xml * ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml * ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml.orig * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient
[jira] [Updated] (AMBARI-17904) Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-17904:
---
Status: Patch Available (was: Open)
> Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't
> Upgrade
>
>
> Key: AMBARI-17904
> URL: https://issues.apache.org/jira/browse/AMBARI-17904
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17904.patch
>
>
> STR:
> - Install HDP 2.4 with Storm and start an EU to 2.5
> - On the first manual task, click downgrade right away
> You'll notice that in addition to the 2 or 3 "normal" downgrade tasks, Storm
> is also scheduled. There are 2 manual tasks which are scheduled for
> SUPERVISOR and DRPC_SERVER.
> It looks like the cause of this is a bug in the {{TaskWrapperBuilder}} which
> schedules tasks for {{MANUAL}} and {{CONFIGURE}} regardless of whether any
> hosts resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17904) Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-17904:
---
Attachment: AMBARI-17904.patch
> Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't
> Upgrade
>
>
> Key: AMBARI-17904
> URL: https://issues.apache.org/jira/browse/AMBARI-17904
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17904.patch
>
>
> STR:
> - Install HDP 2.4 with Storm and start an EU to 2.5
> - On the first manual task, click downgrade right away
> You'll notice that in addition to the 2 or 3 "normal" downgrade tasks, Storm
> is also scheduled. There are 2 manual tasks which are scheduled for
> SUPERVISOR and DRPC_SERVER.
> It looks like the cause of this is a bug in the {{TaskWrapperBuilder}} which
> schedules tasks for {{MANUAL}} and {{CONFIGURE}} regardless of whether any
> hosts resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394422#comment-15394422 ] Alejandro Fernandez commented on AMBARI-16027: -- +1 for [^AMBARI-16027.addendum.patch] > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17771) Update alert definition for Ranger Admin after kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394415#comment-15394415 ] Hudson commented on AMBARI-17771: - FAILURE: Integrated in Ambari-trunk-Commit #5392 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5392/]) AMBARI-17771. Update alert definition for Ranger Admin after kerberos (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5ebb04a2e9da16c694622354dcb8a5a749f0b0f6]) * ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerWebAlertConfigActionTest.java * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/common-services/RANGER/0.6.0/alerts.json * ambari-server/src/test/resources/stacks/HDP/2.5.0/services/RANGER/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerWebAlertConfigAction.java > Update alert definition for Ranger Admin after kerberos changes > --- > > Key: AMBARI-17771 > URL: https://issues.apache.org/jira/browse/AMBARI-17771 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Deepak Sharma >Assignee: Gautam Borad >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17771.2.patch, AMBARI-17771.3.patch, > AMBARI-17771.patch > > > Update alert definition for Ranger Admin after kerberos changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17894) Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
[
https://issues.apache.org/jira/browse/AMBARI-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394416#comment-15394416
]
Hudson commented on AMBARI-17894:
-
FAILURE: Integrated in Ambari-trunk-Commit #5392 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5392/])
AMBARI-17894 - Adding Services After A Stack/Ambari Upgrade Shows Empty
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5261c76c62ec06af77d04bc5e0a9f128d3be12b2])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackUpgradeConfigurationMergeTest.java
*
ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hiveserver2-site.xml
> Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
>
>
> Key: AMBARI-17894
> URL: https://issues.apache.org/jira/browse/AMBARI-17894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17894.patch
>
>
> STR:
> - Install Ambari 2.2.2 with Hive on HDP 2.4.2.0 and Kerberize
> - Upgrade to Ambari 2.4.0
> - Upgrade to HDP 2.5
> - Distribute Keytabs
> - Add a new service
> At this point, the UI flags Hive as having configurations which need
> attention. The follow are all blank and are marked as required:
> {code}
> hive-site/hive.server2.authentication.ldap.url
> hiveserver2-site/hive.conf.restricted.list
> hiveserver2-site/hive.security.authenticator.manager
> hiveserver2-site/hive.security.authorization.manager
> {code}
> There are actually two problems here:
> - The Kerberos wizard interprets the stack advisor "delete" attribute and
> improperly sets config properties to blank instead of actually removing them
> - The upgrade logic is adding properties back when it should not.
> The Kerberos issue aside, we can't be adding properties back during upgrade
> stack merging when those properties were specifically removed by the stack
> advisor prior.
> For example (Ambari 2.2.2 installed with HDP 2.x)
> - Ambari 2.2.2 does not have {{foo-site/property}} for HDP 2.x
> - Ambari 2.4.0 adds {{foo-site/property}} for HDP 2.x, but instructs the
> upgrade not to add it
> - An upgrade to HDP 2.y sees that {{foo-site/property}} doesn't exist and
> thinks it's brand new and needs to be merged.
> The upgrade logic should check to see if {{foo-site/property}} is part of
> both 2.x and 2.y default configurations. If it's part of both of them and is
> not currently set, then upgrade should NOT set it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394406#comment-15394406 ] Sumit Mohanty commented on AMBARI-16027: The changes look good for https://issues.apache.org/jira/secure/attachment/12820235/AMBARI-16027.addendum.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394406#comment-15394406 ] Sumit Mohanty edited comment on AMBARI-16027 at 7/26/16 7:34 PM: - The changes look good for https://issues.apache.org/jira/secure/attachment/12820235/AMBARI-16027.addendum.patch +1. was (Author: sumitmohanty): The changes look good for https://issues.apache.org/jira/secure/attachment/12820235/AMBARI-16027.addendum.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394348#comment-15394348 ] Sriharsha Chintalapani commented on AMBARI-16027: - [~sumitmohanty] [~afernandez] added addendum patch to remove the tasks from upgrades as we don't need them anymore. > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Attachment: AMBARI-16027.addendum.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17782: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit e424b5b538537ea16f7d8cc24899c7a4ff5864a0 branch-2.4, commit 39085e705d4db0ab2332602ec5b2790e0fc2e562 > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient.option.useKeyTab (remove this property) > * atlas.jaas.KafkaClient.option.useTicketCache=true (add this property) > * atlas.jaas.KafkaClient.option.renewTicket=true (add this property) > * atlas.rest.address (add this property) > > /etc/sqoop/conf/sqoop-site.xml: > * atlas.cluster.name (remove this property) > Also, there is no 'Custom sqoop-atlas-application.properties' section in Sqoop > Test Plan: > 1. Install Ambari 2.4, HDP 2.5 along with Hive, Storm, Kafka, Sqoop and all > of their dependencies. > Verify that none of the atlas.* configs exist nor the > $HOOK-atlas-application.properties file > Ensure that hive-site and storm.yaml don't have any Atlas properties. > 2. After #1, add Atlas and verify that all of the hooks have > atlas.rest.address and atlas.cluster.name > 3. After #2, kerberize the cluster and ensure Sqoop has the right configs in > its sqoop-atlas-application.properties file. > 4. After #1, kerberize the cluster. This should add the application configs > to sqoop-atlas-application.properties in the DB, but the file will not be > saved to the local file system until Atlas is added. > After this, add Atlas service (and its dependencies), and ensure that all of > the configs in /etc/sqoop/conf/sqoop-atlas-application.properties are correct. > 5. Install Ambari 2.2.2 with HDP 2.4 along with Hive, Storm, Kafka, Sqoop, > and Atlas. Upgrade Ambari to 2.4.0 and ensure Atlas still works. > Install bits for HDP 2.5, remove Atlas, and perform either an EU/RU to HDP > 2.5. > This should remove atlas.cluster.name and atlas.rest.address from hive-site, > plus several other security-related properties from sqoop-site if the cluster > was kerberized. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17782: - Attachment: AMBARI-17782.v3.patch > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient.option.useKeyTab (remove this property) > * atlas.jaas.KafkaClient.option.useTicketCache=true (add this property) > * atlas.jaas.KafkaClient.option.renewTicket=true (add this property) > * atlas.rest.address (add this property) > > /etc/sqoop/conf/sqoop-site.xml: > * atlas.cluster.name (remove this property) > Also, there is no 'Custom sqoop-atlas-application.properties' section in Sqoop > Test Plan: > 1. Install Ambari 2.4, HDP 2.5 along with Hive, Storm, Kafka, Sqoop and all > of their dependencies. > Verify that none of the atlas.* configs exist nor the > $HOOK-atlas-application.properties file > Ensure that hive-site and storm.yaml don't have any Atlas properties. > 2. After #1, add Atlas and verify that all of the hooks have > atlas.rest.address and atlas.cluster.name > 3. After #2, kerberize the cluster and ensure Sqoop has the right configs in > its sqoop-atlas-application.properties file. > 4. After #1, kerberize the cluster. This should add the application configs > to sqoop-atlas-application.properties in the DB, but the file will not be > saved to the local file system until Atlas is added. > After this, add Atlas service (and its dependencies), and ensure that all of > the configs in /etc/sqoop/conf/sqoop-atlas-application.properties are correct. > 5. Install Ambari 2.2.2 with HDP 2.4 along with Hive, Storm, Kafka, Sqoop, > and Atlas. Upgrade Ambari to 2.4.0 and ensure Atlas still works. > Install bits for HDP 2.5, remove Atlas, and perform either an EU/RU to HDP > 2.5. > This should remove atlas.cluster.name and atlas.rest.address from hive-site, > plus several other security-related properties from sqoop-site if the cluster > was kerberized. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17782: - Status: Patch Available (was: Open) > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient.option.useKeyTab (remove this property) > * atlas.jaas.KafkaClient.option.useTicketCache=true (add this property) > * atlas.jaas.KafkaClient.option.renewTicket=true (add this property) > * atlas.rest.address (add this property) > > /etc/sqoop/conf/sqoop-site.xml: > * atlas.cluster.name (remove this property) > Also, there is no 'Custom sqoop-atlas-application.properties' section in Sqoop > Test Plan: > 1. Install Ambari 2.4, HDP 2.5 along with Hive, Storm, Kafka, Sqoop and all > of their dependencies. > Verify that none of the atlas.* configs exist nor the > $HOOK-atlas-application.properties file > Ensure that hive-site and storm.yaml don't have any Atlas properties. > 2. After #1, add Atlas and verify that all of the hooks have > atlas.rest.address and atlas.cluster.name > 3. After #2, kerberize the cluster and ensure Sqoop has the right configs in > its sqoop-atlas-application.properties file. > 4. After #1, kerberize the cluster. This should add the application configs > to sqoop-atlas-application.properties in the DB, but the file will not be > saved to the local file system until Atlas is added. > After this, add Atlas service (and its dependencies), and ensure that all of > the configs in /etc/sqoop/conf/sqoop-atlas-application.properties are correct. > 5. Install Ambari 2.2.2 with HDP 2.4 along with Hive, Storm, Kafka, Sqoop, > and Atlas. Upgrade Ambari to 2.4.0 and ensure Atlas still works. > Install bits for HDP 2.5, remove Atlas, and perform either an EU/RU to HDP > 2.5. > This should remove atlas.cluster.name and atlas.rest.address from hive-site, > plus several other security-related properties from sqoop-site if the cluster > was kerberized. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17782: - Status: Open (was: Patch Available) > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient.option.useKeyTab (remove this property) > * atlas.jaas.KafkaClient.option.useTicketCache=true (add this property) > * atlas.jaas.KafkaClient.option.renewTicket=true (add this property) > * atlas.rest.address (add this property) > > /etc/sqoop/conf/sqoop-site.xml: > * atlas.cluster.name (remove this property) > Also, there is no 'Custom sqoop-atlas-application.properties' section in Sqoop > Test Plan: > 1. Install Ambari 2.4, HDP 2.5 along with Hive, Storm, Kafka, Sqoop and all > of their dependencies. > Verify that none of the atlas.* configs exist nor the > $HOOK-atlas-application.properties file > Ensure that hive-site and storm.yaml don't have any Atlas properties. > 2. After #1, add Atlas and verify that all of the hooks have > atlas.rest.address and atlas.cluster.name > 3. After #2, kerberize the cluster and ensure Sqoop has the right configs in > its sqoop-atlas-application.properties file. > 4. After #1, kerberize the cluster. This should add the application configs > to sqoop-atlas-application.properties in the DB, but the file will not be > saved to the local file system until Atlas is added. > After this, add Atlas service (and its dependencies), and ensure that all of > the configs in /etc/sqoop/conf/sqoop-atlas-application.properties are correct. > 5. Install Ambari 2.2.2 with HDP 2.4 along with Hive, Storm, Kafka, Sqoop, > and Atlas. Upgrade Ambari to 2.4.0 and ensure Atlas still works. > Install bits for HDP 2.5, remove Atlas, and perform either an EU/RU to HDP > 2.5. > This should remove atlas.cluster.name and atlas.rest.address from hive-site, > plus several other security-related properties from sqoop-site if the cluster > was kerberized. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17782) Config changes for Atlas in HDP 2.5 related to atlas.rest.address, atlas.cluster.name, etc
[ https://issues.apache.org/jira/browse/AMBARI-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17782: - Attachment: (was: AMBARI-17782.v2.patch) > Config changes for Atlas in HDP 2.5 related to atlas.rest.address, > atlas.cluster.name, etc > -- > > Key: AMBARI-17782 > URL: https://issues.apache.org/jira/browse/AMBARI-17782 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17782.v3.patch > > > To support Atlas in HDP 2.5, make several config changes: > /etc/hive/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/hive/conf/hive-site.xml: > * atlas.cluster.name (remove this property) > * atlas.hook.hive.maxThreads (remove this property) > * atlas.hook.hive.minThreads (remove this property) > * atlas.rest.address (remove this property) > /etc/storm/conf/atlas-application.properties: > * atlas.rest.address (add this property) > > /etc/storm/conf/storm.yaml: > * atlas.cluster.name (remove this property) > > /etc/falcon/conf/atlas-application.properties: > * atlas.rest.address (add this property) > * atlas.cluster.name (this value is empty; need to set to correct value) > > /etc/sqoop/conf/atlas-application.properties: > * atlas.jaas.KafkaClient.option.keyTab (remove this property) > * atlas.jaas.KafkaClient.option.principal (remove this property) > * atlas.jaas.KafkaClient.option.storeKey (remove this property) > * atlas.jaas.KafkaClient.option.useKeyTab (remove this property) > * atlas.jaas.KafkaClient.option.useTicketCache=true (add this property) > * atlas.jaas.KafkaClient.option.renewTicket=true (add this property) > * atlas.rest.address (add this property) > > /etc/sqoop/conf/sqoop-site.xml: > * atlas.cluster.name (remove this property) > Also, there is no 'Custom sqoop-atlas-application.properties' section in Sqoop > Test Plan: > 1. Install Ambari 2.4, HDP 2.5 along with Hive, Storm, Kafka, Sqoop and all > of their dependencies. > Verify that none of the atlas.* configs exist nor the > $HOOK-atlas-application.properties file > Ensure that hive-site and storm.yaml don't have any Atlas properties. > 2. After #1, add Atlas and verify that all of the hooks have > atlas.rest.address and atlas.cluster.name > 3. After #2, kerberize the cluster and ensure Sqoop has the right configs in > its sqoop-atlas-application.properties file. > 4. After #1, kerberize the cluster. This should add the application configs > to sqoop-atlas-application.properties in the DB, but the file will not be > saved to the local file system until Atlas is added. > After this, add Atlas service (and its dependencies), and ensure that all of > the configs in /etc/sqoop/conf/sqoop-atlas-application.properties are correct. > 5. Install Ambari 2.2.2 with HDP 2.4 along with Hive, Storm, Kafka, Sqoop, > and Atlas. Upgrade Ambari to 2.4.0 and ensure Atlas still works. > Install bits for HDP 2.5, remove Atlas, and perform either an EU/RU to HDP > 2.5. > This should remove atlas.cluster.name and atlas.rest.address from hive-site, > plus several other security-related properties from sqoop-site if the cluster > was kerberized. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17859) YARN service check failed during EU from HDP-2.4.0.0 to Erie
[
https://issues.apache.org/jira/browse/AMBARI-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394265#comment-15394265
]
Hudson commented on AMBARI-17859:
-
FAILURE: Integrated in Ambari-trunk-Commit #5391 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5391/])
AMBARI-17859. YARN service check failed during EU from HDP-2.4.0.0 to
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=33c10efe45ec3488a804c7fb46170afad325cc46])
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
> YARN service check failed during EU from HDP-2.4.0.0 to Erie
>
>
> Key: AMBARI-17859
> URL: https://issues.apache.org/jira/browse/AMBARI-17859
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17859.patch
>
>
> *Steps*
> # Deploy HDP-2.4.0.0 cluster with Ambari 2.2.1.1 (secure, non-HA cluster,
> customized service users)
> # Upgrade Ambari to 2.4.0.0
> # Perform EU to 2.5.0.0-934
> *Result*
> During EU, observed YARN service check reported below errors:
> {code}
> Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py\",
> line 159, in \nServiceCheck().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py\",
> line 117, in service_check\nuser=params.smokeuser,\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> smk_rndalxit7oqf2pq3erlqg6r...@hwqe.hortonworks.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
> -timeout 30 --queue default' returned 2. Hortonworks
> #\nThis is MOTD message, added for testing in qe infra\n16/07/09
> 11:15:01 INFO impl.TimelineClientImpl: Timeline service address:
> http://host:8188/ws/v1/timeline/\n16/07/09 11:15:01 INFO
> distributedshell.Client: Initializing Client\n16/07/09 11:15:01 INFO
> distributedshell.Client: Running Client\n16/07/09 11:15:01 INFO
> client.RMProxy: Connecting to ResourceManager at
> host-5.domainlocal/10.0.113.157:8050\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got Cluster metric info from ASM,
> numNodeManagers=3\n16/07/09 11:15:03 INFO distributedshell.Client: Got
> Cluster node info from ASM\n16/07/09 11:15:03 INFO distributedshell.Client:
> Got node report from ASM for, nodeId=host:25454, nodeAddresshost:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got node report from ASM for,
> nodeId=host-5.domainlocal:25454, nodeAddresshost-5.domainlocal:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got node report from ASM for,
> nodeId=host-1.domainlocal:25454, nodeAddresshost-1.domainlocal:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Queue info, queueName=default,
> queueCurrentCapacity=0.0, queueMaxCapacity=1.0, queueApplicationCount=0,
> queueChildQueueCount=0\n16/07/09 11:15:04 INFO distributedshell.Client: User
> ACL Info for Queue, queueName=root, userAcl=SUBMIT_APPLICATIONS\n16/07/09
> 11:15:04 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=default, userAcl=SUBMIT_APPLICATIONS\n16/07/09 11:15:04 INFO
> distributedshell.Client: Max mem capability of resources in this cluster
> 10240\n16/07/09 11:15:04 INFO distributedshell.Client: Max virtual cores
> capabililty of resources in this cluster 1\n16/07/09 11:15:04 INFO
> distributedshell.Client: Copy App Master jar from local filesystem and add to
> local environment\n16/07/09 11:15:04 INFO distributedshell.Client: Set the
> environm
[jira] [Commented] (AMBARI-17880) Kerberos keytab regeneration stack advisor bug
[ https://issues.apache.org/jira/browse/AMBARI-17880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394264#comment-15394264 ] Hudson commented on AMBARI-17880: - FAILURE: Integrated in Ambari-trunk-Commit #5391 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5391/]) AMBARI-17880. Kerberos keytab regeneration stack advisor bug (Miklos (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c52d3d64599dab97c9ac5d5e0fc917bc9cdc49a0]) * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java > Kerberos keytab regeneration stack advisor bug > -- > > Key: AMBARI-17880 > URL: https://issues.apache.org/jira/browse/AMBARI-17880 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17880.patch > > > If the kerberos keytabs are regenerated via ambari then the stack advisor > also runs, but instead of deleting those properties which are recommended to > do so it sets the value to an empty string, which may lead to an inconsistent > state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: AMBARI-17694-Jul26.patch > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: AMBARI-17694-Jul26.patch > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Status: Open (was: Patch Available) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: (was: AMBARI-17694-Jul26.patch) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Status: Patch Available (was: Open) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: (was: AMBARI-17694-2.patch) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17896) Fix Falcon atlas configuration for new atlas falcon hooks
[ https://issues.apache.org/jira/browse/AMBARI-17896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17896: Attachment: AMBARI-17896-2.patch > Fix Falcon atlas configuration for new atlas falcon hooks > - > > Key: AMBARI-17896 > URL: https://issues.apache.org/jira/browse/AMBARI-17896 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Attachments: AMBARI-17896-2.patch > > > The falcon hook class name should be org.apache.atlas.falcon.hook.AtlasHook. > Falcon hook classpath should be stack_root/current/atlas-client/hook/falcon/* > There are no RU/EU issues with this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17894) Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
[
https://issues.apache.org/jira/browse/AMBARI-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17894:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
>
>
> Key: AMBARI-17894
> URL: https://issues.apache.org/jira/browse/AMBARI-17894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17894.patch
>
>
> STR:
> - Install Ambari 2.2.2 with Hive on HDP 2.4.2.0 and Kerberize
> - Upgrade to Ambari 2.4.0
> - Upgrade to HDP 2.5
> - Distribute Keytabs
> - Add a new service
> At this point, the UI flags Hive as having configurations which need
> attention. The follow are all blank and are marked as required:
> {code}
> hive-site/hive.server2.authentication.ldap.url
> hiveserver2-site/hive.conf.restricted.list
> hiveserver2-site/hive.security.authenticator.manager
> hiveserver2-site/hive.security.authorization.manager
> {code}
> There are actually two problems here:
> - The Kerberos wizard interprets the stack advisor "delete" attribute and
> improperly sets config properties to blank instead of actually removing them
> - The upgrade logic is adding properties back when it should not.
> The Kerberos issue aside, we can't be adding properties back during upgrade
> stack merging when those properties were specifically removed by the stack
> advisor prior.
> For example (Ambari 2.2.2 installed with HDP 2.x)
> - Ambari 2.2.2 does not have {{foo-site/property}} for HDP 2.x
> - Ambari 2.4.0 adds {{foo-site/property}} for HDP 2.x, but instructs the
> upgrade not to add it
> - An upgrade to HDP 2.y sees that {{foo-site/property}} doesn't exist and
> thinks it's brand new and needs to be merged.
> The upgrade logic should check to see if {{foo-site/property}} is part of
> both 2.x and 2.y default configurations. If it's part of both of them and is
> not currently set, then upgrade should NOT set it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17894) Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
[
https://issues.apache.org/jira/browse/AMBARI-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17894:
-
Status: Patch Available (was: Open)
> Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
>
>
> Key: AMBARI-17894
> URL: https://issues.apache.org/jira/browse/AMBARI-17894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17894.patch
>
>
> STR:
> - Install Ambari 2.2.2 with Hive on HDP 2.4.2.0 and Kerberize
> - Upgrade to Ambari 2.4.0
> - Upgrade to HDP 2.5
> - Distribute Keytabs
> - Add a new service
> At this point, the UI flags Hive as having configurations which need
> attention. The follow are all blank and are marked as required:
> {code}
> hive-site/hive.server2.authentication.ldap.url
> hiveserver2-site/hive.conf.restricted.list
> hiveserver2-site/hive.security.authenticator.manager
> hiveserver2-site/hive.security.authorization.manager
> {code}
> There are actually two problems here:
> - The Kerberos wizard interprets the stack advisor "delete" attribute and
> improperly sets config properties to blank instead of actually removing them
> - The upgrade logic is adding properties back when it should not.
> The Kerberos issue aside, we can't be adding properties back during upgrade
> stack merging when those properties were specifically removed by the stack
> advisor prior.
> For example (Ambari 2.2.2 installed with HDP 2.x)
> - Ambari 2.2.2 does not have {{foo-site/property}} for HDP 2.x
> - Ambari 2.4.0 adds {{foo-site/property}} for HDP 2.x, but instructs the
> upgrade not to add it
> - An upgrade to HDP 2.y sees that {{foo-site/property}} doesn't exist and
> thinks it's brand new and needs to be merged.
> The upgrade logic should check to see if {{foo-site/property}} is part of
> both 2.x and 2.y default configurations. If it's part of both of them and is
> not currently set, then upgrade should NOT set it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17894) Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
[
https://issues.apache.org/jira/browse/AMBARI-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17894:
-
Attachment: AMBARI-17894.patch
> Adding Services After A Stack/Ambari Upgrade Shows Empty Required Values
>
>
> Key: AMBARI-17894
> URL: https://issues.apache.org/jira/browse/AMBARI-17894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17894.patch
>
>
> STR:
> - Install Ambari 2.2.2 with Hive on HDP 2.4.2.0 and Kerberize
> - Upgrade to Ambari 2.4.0
> - Upgrade to HDP 2.5
> - Distribute Keytabs
> - Add a new service
> At this point, the UI flags Hive as having configurations which need
> attention. The follow are all blank and are marked as required:
> {code}
> hive-site/hive.server2.authentication.ldap.url
> hiveserver2-site/hive.conf.restricted.list
> hiveserver2-site/hive.security.authenticator.manager
> hiveserver2-site/hive.security.authorization.manager
> {code}
> There are actually two problems here:
> - The Kerberos wizard interprets the stack advisor "delete" attribute and
> improperly sets config properties to blank instead of actually removing them
> - The upgrade logic is adding properties back when it should not.
> The Kerberos issue aside, we can't be adding properties back during upgrade
> stack merging when those properties were specifically removed by the stack
> advisor prior.
> For example (Ambari 2.2.2 installed with HDP 2.x)
> - Ambari 2.2.2 does not have {{foo-site/property}} for HDP 2.x
> - Ambari 2.4.0 adds {{foo-site/property}} for HDP 2.x, but instructs the
> upgrade not to add it
> - An upgrade to HDP 2.y sees that {{foo-site/property}} doesn't exist and
> thinks it's brand new and needs to be merged.
> The upgrade logic should check to see if {{foo-site/property}} is part of
> both 2.x and 2.y default configurations. If it's part of both of them and is
> not currently set, then upgrade should NOT set it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order
[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram reassigned AMBARI-17747: -- Assignee: Nahappan Somasundaram (was: Jayush Luniya) > EU/RU Kafka should come right after ZK instead of before Atlas, fix role > command order > -- > > Key: AMBARI-17747 > URL: https://issues.apache.org/jira/browse/AMBARI-17747 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: AMBARI-17747.branch-2.4.patch, AMBARI-17747.trunk.patch > > > Atlas has a dependency on Kafka, yet EU/EU upgrades Atlas and then Kafka. > We should move Kafka right after ZK. > Also check role command order so that Atlas starts after HBASE and Kafka have > been started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17906) Atlas has Critical WEB alert after adding to a secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-17906: - Status: Patch Available (was: Open) > Atlas has Critical WEB alert after adding to a secure cluster > - > > Key: AMBARI-17906 > URL: https://issues.apache.org/jira/browse/AMBARI-17906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17906.patch > > > Deploy a secure cluster via blueprint without Atlas. > Add a new host to the cluster > Add Atlas > Atlas servcie has a critical alert -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17906) Atlas has Critical WEB alert after adding to a secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-17906: - Attachment: AMBARI-17906.patch > Atlas has Critical WEB alert after adding to a secure cluster > - > > Key: AMBARI-17906 > URL: https://issues.apache.org/jira/browse/AMBARI-17906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17906.patch > > > Deploy a secure cluster via blueprint without Atlas. > Add a new host to the cluster > Add Atlas > Atlas servcie has a critical alert -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17906) Atlas has Critical WEB alert after adding to a secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-17906: - Description: Deploy a secure cluster via blueprint without Atlas. Add a new host to the cluster Add Atlas Atlas servcie has a critical alert > Atlas has Critical WEB alert after adding to a secure cluster > - > > Key: AMBARI-17906 > URL: https://issues.apache.org/jira/browse/AMBARI-17906 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.4.0 > > > Deploy a secure cluster via blueprint without Atlas. > Add a new host to the cluster > Add Atlas > Atlas servcie has a critical alert -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17906) Atlas has Critical WEB alert after adding to a secure cluster
Dmytro Grinenko created AMBARI-17906: Summary: Atlas has Critical WEB alert after adding to a secure cluster Key: AMBARI-17906 URL: https://issues.apache.org/jira/browse/AMBARI-17906 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Dmytro Grinenko Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17771) Update alert definition for Ranger Admin after kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-17771: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Update alert definition for Ranger Admin after kerberos changes > --- > > Key: AMBARI-17771 > URL: https://issues.apache.org/jira/browse/AMBARI-17771 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Deepak Sharma >Assignee: Gautam Borad >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17771.2.patch, AMBARI-17771.3.patch, > AMBARI-17771.patch > > > Update alert definition for Ranger Admin after kerberos changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17771) Update alert definition for Ranger Admin after kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394127#comment-15394127 ] Gautam Borad commented on AMBARI-17771: --- Committed to trunk : https://github.com/apache/ambari/commit/5ebb04a2e9da16c694622354dcb8a5a749f0b0f6 Committed to branch-2.4 : https://github.com/apache/ambari/commit/749559900b65b50179c2706dc089c2be6fba9638 > Update alert definition for Ranger Admin after kerberos changes > --- > > Key: AMBARI-17771 > URL: https://issues.apache.org/jira/browse/AMBARI-17771 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Deepak Sharma >Assignee: Gautam Borad >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17771.2.patch, AMBARI-17771.3.patch, > AMBARI-17771.patch > > > Update alert definition for Ranger Admin after kerberos changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17771) Update alert definition for Ranger Admin after kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-17771: -- Status: Patch Available (was: Open) > Update alert definition for Ranger Admin after kerberos changes > --- > > Key: AMBARI-17771 > URL: https://issues.apache.org/jira/browse/AMBARI-17771 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Deepak Sharma >Assignee: Gautam Borad >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17771.2.patch, AMBARI-17771.3.patch, > AMBARI-17771.patch > > > Update alert definition for Ranger Admin after kerberos changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17895) HS2 interactive fails to start when enabling kerberos on a HA cluster with: ERROR main.ServiceLauncher - Exception: Null clientToAMToken
[ https://issues.apache.org/jira/browse/AMBARI-17895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394113#comment-15394113 ] Sumit Mohanty commented on AMBARI-17895: Tested it after applying on a locally deployed cluster. > HS2 interactive fails to start when enabling kerberos on a HA cluster with: > ERROR main.ServiceLauncher - Exception: Null clientToAMToken > > > Key: AMBARI-17895 > URL: https://issues.apache.org/jira/browse/AMBARI-17895 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17895.patch > > > HSI start must follow RM start and HSI stop must precede NM stops. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17883) Installing Components After Registering A New Repository Uses The Wrong Version
[
https://issues.apache.org/jira/browse/AMBARI-17883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394100#comment-15394100
]
Hudson commented on AMBARI-17883:
-
FAILURE: Integrated in Ambari-trunk-Commit #5390 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5390/])
AMBARI-17883. Installing Components After Registering A New Repository (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0fb78858004e62f85694b8f0f68ede511c4c2026])
* ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py
* ambari-common/src/main/python/resource_management/libraries/script/script.py
> Installing Components After Registering A New Repository Uses The Wrong
> Version
> ---
>
> Key: AMBARI-17883
> URL: https://issues.apache.org/jira/browse/AMBARI-17883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17883.patch
>
>
> STR:
> - Install HDP 2.4 with ZooKeeper
> - Register HDP 2.5 and distribute the stack to the hosts
> - Attempt to install another service, such as HDFS
> The version installed is 2.5, not 2.4:
> {code}
> 2016-07-20 14:13:10,155 - Package['unzip'] {'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2016-07-20 14:13:10,270 - Skipping installation of existing package unzip
> 2016-07-20 14:13:10,271 - Package['curl'] {'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2016-07-20 14:13:10,322 - Skipping installation of existing package curl
> 2016-07-20 14:13:10,323 - Package['hdp-select']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> 2016-07-20 14:13:10,374 - Skipping installation of existing package hdp-select
> 2016-07-20 14:13:10,520 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-07-20 14:13:10,523 - Stack Feature Version Info: stack_version=2.4,
> version=2.4.2.0-236, current_cluster_version=2.4.2.0-236 -> 2.4.2.0-236
> 2016-07-20 14:13:10,525 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-07-20 14:13:10,531 - checked_call['rpm -q --queryformat
> '%{version}-%{release}' hdp-select | sed -e 's/\.el[0-9]//g''] {'stderr': -1}
> 2016-07-20 14:13:10,547 - checked_call returned (0, '2.5.0.0-965', '')
> 2016-07-20 14:13:10,554 - Package['hadoop_2_5_0_0_965']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> {code}
> Taking a look at my hosts:
> {code}
> [root@c6401 ~]# ll /usr/hdp/
> total 12
> drwxr-xr-x 6 root root 4096 Jul 19 19:48 2.4.2.0-236
> drwxr-xr-x 13 root root 4096 Jul 20 14:13 2.5.0.0-965
> drwxr-xr-x 2 root root 4096 Jul 20 14:13 current
> {code}
> {code}
> [root@c6401 ~]# ll /usr/hdp/current/ | grep zookeeper
> lrwxrwxrwx 1 root root 30 Jul 20 14:15 zookeeper-client ->
> /usr/hdp/2.4.2.0-236/zookeeper
> lrwxrwxrwx 1 root root 30 Jul 20 14:15 zookeeper-server ->
> /usr/hdp/2.4.2.0-236/zookeeper
> {code}
> {code}
> [root@c6401 ~]# rpm -q --queryformat '%{version}-%{release}' hdp-select | sed
> -e 's/\.el[0-9]//g'
> 2.5.0.0-965
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17889) Bad error message if user has not performed ambari-server setup for jdbc driver before configuring custom DB
[
https://issues.apache.org/jira/browse/AMBARI-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394099#comment-15394099
]
Hudson commented on AMBARI-17889:
-
FAILURE: Integrated in Ambari-trunk-Commit #5390 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5390/])
AMBARI-17889. Bad error message if user has not performed ambari-server
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a50a37333668185d2eadfbe08999235f4cbbe44b])
* ambari-server/src/main/resources/custom_actions/scripts/check_host.py
> Bad error message if user has not performed ambari-server setup for jdbc
> driver before configuring custom DB
>
>
> Key: AMBARI-17889
> URL: https://issues.apache.org/jira/browse/AMBARI-17889
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-17889.patch
>
>
> While installing a cluster, I forgot to call:
> {{ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java.jar}}
> Check DB connection failed with:
> {code}
> 2016-07-13 00:56:32,751 - There was an unknown error while checking database
> connectivity: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 144, in actionexecute
> db_connection_check_structured_output =
> self.execute_db_connection_check(config, tmp_dir)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 285, in execute_db_connection_check
> jdbc_url = jdk_location + jdbc_driver_mysql_name
> TypeError: cannot concatenate 'str' and 'NoneType' objects
> 2016-07-13 00:56:32,752 - Check db_connection_check was unsuccessful. Exit
> code: 1. Message: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 506, in
> CheckHost().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 206, in actionexecute
> raise Fail(error_message)
> resource_management.core.exceptions.Fail: Check db_connection_check was
> unsuccessful. Exit code: 1. Message: cannot concatenate 'str' and 'NoneType'
> objects
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17905) HBase coprocessor classes related properties in hbase-site are empty after Ambari upgrade from 2.1.2 to 2.4.0
[
https://issues.apache.org/jira/browse/AMBARI-17905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17905:
Status: Patch Available (was: Open)
> HBase coprocessor classes related properties in hbase-site are empty after
> Ambari upgrade from 2.1.2 to 2.4.0
> -
>
> Key: AMBARI-17905
> URL: https://issues.apache.org/jira/browse/AMBARI-17905
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17905.patch
>
>
> HBase coprocessor classes related properties in hbase-site are empty after
> Ambari upgrade from 2.1.2 to 2.4.0
> HBase smoke test running RowCounter job failed with 'No registered
> coprocessor service'
> {code}
> 2016-07-22
> 02:22:36,708|beaver.machine|INFO|3805|140178050393920|MainThread|Exception in
> thread "main" org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
> org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered
> coprocessor service found for name AuthenticationService in region
> hbase:meta,,1
> {code}
> Ambari upgrade seems to have started at 23:17:28, current Ambari version as
> per UI is 2.4.0
> {code}
> 2016-07-21
> 23:17:28,148|ambaricst-rolu-ambupg|INFO|3805|140178050393920|MainThread|Starting
> ambari upgrade
> 2016-07-21
> 23:17:28,148|beaver.util|INFO|3805|140178050393920|MainThread|Downloading
> from url ->
> http://host/apache-maven-3.0.4-bin.tar.gz?AWSAccessKeyId=AKIAIDZB7JJ5YBYI23KQ&Expires=1763284021&Signature=nYkI8V24vs2xWOJtCJXLoS/D9As%3D
> 2016-07-21
> 23:17:28,327|beaver.util|INFO|3805|140178050393920|MainThread|Expected file
> size = 4873043
> {code}
> {code}
>
> hbase.coprocessor.master.classes
>
>
>
> hbase.coprocessor.region.classes
>
>
>
> hbase.coprocessor.regionserver.classes
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17905) HBase coprocessor classes related properties in hbase-site are empty after Ambari upgrade from 2.1.2 to 2.4.0
[
https://issues.apache.org/jira/browse/AMBARI-17905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17905:
Attachment: AMBARI-17905.patch
> HBase coprocessor classes related properties in hbase-site are empty after
> Ambari upgrade from 2.1.2 to 2.4.0
> -
>
> Key: AMBARI-17905
> URL: https://issues.apache.org/jira/browse/AMBARI-17905
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17905.patch
>
>
> HBase coprocessor classes related properties in hbase-site are empty after
> Ambari upgrade from 2.1.2 to 2.4.0
> HBase smoke test running RowCounter job failed with 'No registered
> coprocessor service'
> {code}
> 2016-07-22
> 02:22:36,708|beaver.machine|INFO|3805|140178050393920|MainThread|Exception in
> thread "main" org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
> org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered
> coprocessor service found for name AuthenticationService in region
> hbase:meta,,1
> {code}
> Ambari upgrade seems to have started at 23:17:28, current Ambari version as
> per UI is 2.4.0
> {code}
> 2016-07-21
> 23:17:28,148|ambaricst-rolu-ambupg|INFO|3805|140178050393920|MainThread|Starting
> ambari upgrade
> 2016-07-21
> 23:17:28,148|beaver.util|INFO|3805|140178050393920|MainThread|Downloading
> from url ->
> http://host/apache-maven-3.0.4-bin.tar.gz?AWSAccessKeyId=AKIAIDZB7JJ5YBYI23KQ&Expires=1763284021&Signature=nYkI8V24vs2xWOJtCJXLoS/D9As%3D
> 2016-07-21
> 23:17:28,327|beaver.util|INFO|3805|140178050393920|MainThread|Expected file
> size = 4873043
> {code}
> {code}
>
> hbase.coprocessor.master.classes
>
>
>
> hbase.coprocessor.region.classes
>
>
>
> hbase.coprocessor.regionserver.classes
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17905) HBase coprocessor classes related properties in hbase-site are empty after Ambari upgrade from 2.1.2 to 2.4.0
Dmytro Sen created AMBARI-17905:
---
Summary: HBase coprocessor classes related properties in
hbase-site are empty after Ambari upgrade from 2.1.2 to 2.4.0
Key: AMBARI-17905
URL: https://issues.apache.org/jira/browse/AMBARI-17905
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Blocker
Fix For: 2.4.0
HBase coprocessor classes related properties in hbase-site are empty after
Ambari upgrade from 2.1.2 to 2.4.0
HBase smoke test running RowCounter job failed with 'No registered coprocessor
service'
{code}
2016-07-22
02:22:36,708|beaver.machine|INFO|3805|140178050393920|MainThread|Exception in
thread "main" org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered
coprocessor service found for name AuthenticationService in region hbase:meta,,1
{code}
Ambari upgrade seems to have started at 23:17:28, current Ambari version as per
UI is 2.4.0
{code}
2016-07-21
23:17:28,148|ambaricst-rolu-ambupg|INFO|3805|140178050393920|MainThread|Starting
ambari upgrade
2016-07-21
23:17:28,148|beaver.util|INFO|3805|140178050393920|MainThread|Downloading from
url ->
http://host/apache-maven-3.0.4-bin.tar.gz?AWSAccessKeyId=AKIAIDZB7JJ5YBYI23KQ&Expires=1763284021&Signature=nYkI8V24vs2xWOJtCJXLoS/D9As%3D
2016-07-21
23:17:28,327|beaver.util|INFO|3805|140178050393920|MainThread|Expected file
size = 4873043
{code}
{code}
hbase.coprocessor.master.classes
hbase.coprocessor.region.classes
hbase.coprocessor.regionserver.classes
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17880) Kerberos keytab regeneration stack advisor bug
[
https://issues.apache.org/jira/browse/AMBARI-17880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miklos Gergely resolved AMBARI-17880.
-
Resolution: Fixed
Committed:
Committed to trunk
{noformat}
commit c52d3d64599dab97c9ac5d5e0fc917bc9cdc49a0
Author: Miklos Gergely
Date: Tue Jul 26 12:12:23 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit b7b1cf96c311886e018cebdc98f3666223529d10
Author: Miklos Gergely
Date: Tue Jul 26 12:13:35 2016 -0400
{noformat}
> Kerberos keytab regeneration stack advisor bug
> --
>
> Key: AMBARI-17880
> URL: https://issues.apache.org/jira/browse/AMBARI-17880
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17880.patch
>
>
> If the kerberos keytabs are regenerated via ambari then the stack advisor
> also runs, but instead of deleting those properties which are recommended to
> do so it sets the value to an empty string, which may lead to an inconsistent
> state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17859) YARN service check failed during EU from HDP-2.4.0.0 to Erie
[
https://issues.apache.org/jira/browse/AMBARI-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17859:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
de78fb4..8dcc37e branch-2.4 -> branch-2.4
0fb7885..33c10ef trunk -> trunk
> YARN service check failed during EU from HDP-2.4.0.0 to Erie
>
>
> Key: AMBARI-17859
> URL: https://issues.apache.org/jira/browse/AMBARI-17859
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17859.patch
>
>
> *Steps*
> # Deploy HDP-2.4.0.0 cluster with Ambari 2.2.1.1 (secure, non-HA cluster,
> customized service users)
> # Upgrade Ambari to 2.4.0.0
> # Perform EU to 2.5.0.0-934
> *Result*
> During EU, observed YARN service check reported below errors:
> {code}
> Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py\",
> line 159, in \nServiceCheck().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py\",
> line 117, in service_check\nuser=params.smokeuser,\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> smk_rndalxit7oqf2pq3erlqg6r...@hwqe.hortonworks.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
> -timeout 30 --queue default' returned 2. Hortonworks
> #\nThis is MOTD message, added for testing in qe infra\n16/07/09
> 11:15:01 INFO impl.TimelineClientImpl: Timeline service address:
> http://host:8188/ws/v1/timeline/\n16/07/09 11:15:01 INFO
> distributedshell.Client: Initializing Client\n16/07/09 11:15:01 INFO
> distributedshell.Client: Running Client\n16/07/09 11:15:01 INFO
> client.RMProxy: Connecting to ResourceManager at
> host-5.domainlocal/10.0.113.157:8050\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got Cluster metric info from ASM,
> numNodeManagers=3\n16/07/09 11:15:03 INFO distributedshell.Client: Got
> Cluster node info from ASM\n16/07/09 11:15:03 INFO distributedshell.Client:
> Got node report from ASM for, nodeId=host:25454, nodeAddresshost:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got node report from ASM for,
> nodeId=host-5.domainlocal:25454, nodeAddresshost-5.domainlocal:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Got node report from ASM for,
> nodeId=host-1.domainlocal:25454, nodeAddresshost-1.domainlocal:8042,
> nodeRackName/default-rack, nodeNumContainers0\n16/07/09 11:15:03 INFO
> distributedshell.Client: Queue info, queueName=default,
> queueCurrentCapacity=0.0, queueMaxCapacity=1.0, queueApplicationCount=0,
> queueChildQueueCount=0\n16/07/09 11:15:04 INFO distributedshell.Client: User
> ACL Info for Queue, queueName=root, userAcl=SUBMIT_APPLICATIONS\n16/07/09
> 11:15:04 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=default, userAcl=SUBMIT_APPLICATIONS\n16/07/09 11:15:04 INFO
> distributedshell.Client: Max mem capability of resources in this cluster
> 10240\n16/07/09 11:15:04 INFO distributedshell.Client: Max virtual cores
> capabililty of resources in this cluster 1\n16/07/09 11:15:04 INFO
> distributedshell.Client: Copy App Master jar from local filesystem and add to
> local environment\n16/07/09 11:15:04 INFO distributedshell.Client: Set the
> environment for the application master\n16/07/09 11:15:04 INFO
> distributedshell.Client: Setting up app master command\n16/07/09 11:15:04
> INFO distributedshell.Client: Completed setting up app master com
[jira] [Created] (AMBARI-17904) Downgrade Schedules Manual & Configuration Tasks For Components Which Didn't Upgrade
Nate Cole created AMBARI-17904:
--
Summary: Downgrade Schedules Manual & Configuration Tasks For
Components Which Didn't Upgrade
Key: AMBARI-17904
URL: https://issues.apache.org/jira/browse/AMBARI-17904
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
Fix For: 2.4.0
STR:
- Install HDP 2.4 with Storm and start an EU to 2.5
- On the first manual task, click downgrade right away
You'll notice that in addition to the 2 or 3 "normal" downgrade tasks, Storm is
also scheduled. There are 2 manual tasks which are scheduled for SUPERVISOR and
DRPC_SERVER.
It looks like the cause of this is a bug in the {{TaskWrapperBuilder}} which
schedules tasks for {{MANUAL}} and {{CONFIGURE}} regardless of whether any
hosts resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393947#comment-15393947
]
Hudson commented on AMBARI-17900:
-
FAILURE: Integrated in Ambari-trunk-Commit #5389 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5389/])
AMBARI-17900. Disabling Alert Definition causes JS error (onechiporenko)
(onechiporenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=277f7d2e1e87e8471432c0d5a66a418487f2e026])
* ambari-web/app/views/main/alerts/alert_definition/alert_definition_summary.js
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17883) Installing Components After Registering A New Repository Uses The Wrong Version
[
https://issues.apache.org/jira/browse/AMBARI-17883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-17883:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Installing Components After Registering A New Repository Uses The Wrong
> Version
> ---
>
> Key: AMBARI-17883
> URL: https://issues.apache.org/jira/browse/AMBARI-17883
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17883.patch
>
>
> STR:
> - Install HDP 2.4 with ZooKeeper
> - Register HDP 2.5 and distribute the stack to the hosts
> - Attempt to install another service, such as HDFS
> The version installed is 2.5, not 2.4:
> {code}
> 2016-07-20 14:13:10,155 - Package['unzip'] {'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2016-07-20 14:13:10,270 - Skipping installation of existing package unzip
> 2016-07-20 14:13:10,271 - Package['curl'] {'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2016-07-20 14:13:10,322 - Skipping installation of existing package curl
> 2016-07-20 14:13:10,323 - Package['hdp-select']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> 2016-07-20 14:13:10,374 - Skipping installation of existing package hdp-select
> 2016-07-20 14:13:10,520 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-07-20 14:13:10,523 - Stack Feature Version Info: stack_version=2.4,
> version=2.4.2.0-236, current_cluster_version=2.4.2.0-236 -> 2.4.2.0-236
> 2016-07-20 14:13:10,525 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-07-20 14:13:10,531 - checked_call['rpm -q --queryformat
> '%{version}-%{release}' hdp-select | sed -e 's/\.el[0-9]//g''] {'stderr': -1}
> 2016-07-20 14:13:10,547 - checked_call returned (0, '2.5.0.0-965', '')
> 2016-07-20 14:13:10,554 - Package['hadoop_2_5_0_0_965']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> {code}
> Taking a look at my hosts:
> {code}
> [root@c6401 ~]# ll /usr/hdp/
> total 12
> drwxr-xr-x 6 root root 4096 Jul 19 19:48 2.4.2.0-236
> drwxr-xr-x 13 root root 4096 Jul 20 14:13 2.5.0.0-965
> drwxr-xr-x 2 root root 4096 Jul 20 14:13 current
> {code}
> {code}
> [root@c6401 ~]# ll /usr/hdp/current/ | grep zookeeper
> lrwxrwxrwx 1 root root 30 Jul 20 14:15 zookeeper-client ->
> /usr/hdp/2.4.2.0-236/zookeeper
> lrwxrwxrwx 1 root root 30 Jul 20 14:15 zookeeper-server ->
> /usr/hdp/2.4.2.0-236/zookeeper
> {code}
> {code}
> [root@c6401 ~]# rpm -q --queryformat '%{version}-%{release}' hdp-select | sed
> -e 's/\.el[0-9]//g'
> 2.5.0.0-965
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17771) Update alert definition for Ranger Admin after kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-17771: -- Attachment: AMBARI-17771.3.patch > Update alert definition for Ranger Admin after kerberos changes > --- > > Key: AMBARI-17771 > URL: https://issues.apache.org/jira/browse/AMBARI-17771 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Deepak Sharma >Assignee: Gautam Borad >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17771.2.patch, AMBARI-17771.3.patch, > AMBARI-17771.patch > > > Update alert definition for Ranger Admin after kerberos changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17901) Make HDFS operations resilient to namenode safemode
[ https://issues.apache.org/jira/browse/AMBARI-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393883#comment-15393883 ] Sumit Mohanty commented on AMBARI-17901: Along with retry - as it exists for EU, Amabri should have the ability to check (perhaps a custom command) if NN has exited the safe mode so that any Wizard can use to perform an informed wait. This long with live logs from NN through LogSearch will make it visible to the end user as to what the progress. > Make HDFS operations resilient to namenode safemode > --- > > Key: AMBARI-17901 > URL: https://issues.apache.org/jira/browse/AMBARI-17901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that > carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) > should be guarded with retry logic that would retry the operation until a > given timeout before giving up and bailing out. > To determine which HDFS operations are retry able might be as easy as just > looking the returned status/error code or the type of the exception (e.g. > "RetriableException") though this needs to be verified if it's consistent > with both the webhdfs and hdfsresource jar. > This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 > when starting all services after Enabling HA. > Retry count and timeout should be clarified, as sometimes it may take a long > time for namenode to exit safemode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17903) Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0
[ https://issues.apache.org/jira/browse/AMBARI-17903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17903: Status: Patch Available (was: Open) > Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0 > - > > Key: AMBARI-17903 > URL: https://issues.apache.org/jira/browse/AMBARI-17903 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17903.patch > > > STR: > 1) Install old version (Add ranger) > 2) Enable Rangers Plugins (Hbase ranger plugin was enabled) > 2) Make ambari only upgrade > 3) Run Hbase service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17903) Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0
Dmytro Sen created AMBARI-17903: --- Summary: Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0 Key: AMBARI-17903 URL: https://issues.apache.org/jira/browse/AMBARI-17903 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: 2.4.0 Attachments: AMBARI-17903.patch STR: 1) Install old version (Add ranger) 2) Enable Rangers Plugins (Hbase ranger plugin was enabled) 2) Make ambari only upgrade 3) Run Hbase service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17903) Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0
[ https://issues.apache.org/jira/browse/AMBARI-17903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17903: Attachment: AMBARI-17903.patch > Check HBase is failed after Upgrade from 2.1.2 to 2.4.0.0 > - > > Key: AMBARI-17903 > URL: https://issues.apache.org/jira/browse/AMBARI-17903 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17903.patch > > > STR: > 1) Install old version (Add ranger) > 2) Enable Rangers Plugins (Hbase ranger plugin was enabled) > 2) Make ambari only upgrade > 3) Run Hbase service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17902) Config changes to support external solr and internal solr for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-17902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-17902: - Attachment: AMBARI-17902.patch > Config changes to support external solr and internal solr for Ranger > > > Key: AMBARI-17902 > URL: https://issues.apache.org/jira/browse/AMBARI-17902 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17902.patch > > > Ranger Service needs to support the following two scenarios in case when > audit to solr is enabled and solrCloud is used as destination. > External Solr > * If Audit to Solr is Enabled and Solr Cloud == true and Kerberos is Enabled > ** If is_external_solr == true > *** If is_external_solr_kerberized == true > Then recommend ranger.is.solr.kerberised as true. > Ambari Internal Solr > * If Audit to Solr is Enabled and Solr Cloud == true > ** If is_external_solr == false and Kerberos is Enabled > Then directly recommend ranger.is.solr.kerberised as true. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17901) Make HDFS operations resilient to namenode safemode
[ https://issues.apache.org/jira/browse/AMBARI-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17901: --- Assignee: Sandor Magyari > Make HDFS operations resilient to namenode safemode > --- > > Key: AMBARI-17901 > URL: https://issues.apache.org/jira/browse/AMBARI-17901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that > carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) > should be guarded with retry logic that would retry the operation until a > given timeout before giving up and bailing out. > To determine which HDFS operations are retry able might be as easy as just > looking the returned status/error code or the type of the exception (e.g. > "RetriableException") though this needs to be verified if it's consistent > with both the webhdfs and hdfsresource jar. > This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 > when starting all services after Enabling HA. > Retry count and timeout should be clarified, as sometimes it may take a long > time for namenode to exit safemode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17902) Config changes to support external solr and internal solr for Ranger
Mugdha Varadkar created AMBARI-17902: Summary: Config changes to support external solr and internal solr for Ranger Key: AMBARI-17902 URL: https://issues.apache.org/jira/browse/AMBARI-17902 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Critical Fix For: 2.4.0 Ranger Service needs to support the following two scenarios in case when audit to solr is enabled and solrCloud is used as destination. External Solr * If Audit to Solr is Enabled and Solr Cloud == true and Kerberos is Enabled ** If is_external_solr == true *** If is_external_solr_kerberized == true Then recommend ranger.is.solr.kerberised as true. Ambari Internal Solr * If Audit to Solr is Enabled and Solr Cloud == true ** If is_external_solr == false and Kerberos is Enabled Then directly recommend ranger.is.solr.kerberised as true. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17901) Make HDFS operations resilient to namenode safemode
[ https://issues.apache.org/jira/browse/AMBARI-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-17901: Description: HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) should be guarded with retry logic that would retry the operation until a given timeout before giving up and bailing out. To determine which HDFS operations are retry able might be as easy as just looking the returned status/error code or the type of the exception (e.g. "RetriableException") though this needs to be verified if it's consistent with both the webhdfs and hdfsresource jar. This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 when starting all services after Enabling HA. Retry count and timeout should be clarified, as sometimes it may take a long time for namenode to exit safemode. was: HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) should be guarded with retry logic that would retry the operation until a given timeout before giving up and bailing out. To determine which HDFS operations are retry able might be as easy as just looking the returned status/error code or the type of the exception (e.g. "RetriableException") though this needs to be verified if it's consistent with both the webhdfs and hdfsresource jar. This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 when starting all services after Enabling HA. > Make HDFS operations resilient to namenode safemode > --- > > Key: AMBARI-17901 > URL: https://issues.apache.org/jira/browse/AMBARI-17901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari > Fix For: 2.5.0 > > > HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that > carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) > should be guarded with retry logic that would retry the operation until a > given timeout before giving up and bailing out. > To determine which HDFS operations are retry able might be as easy as just > looking the returned status/error code or the type of the exception (e.g. > "RetriableException") though this needs to be verified if it's consistent > with both the webhdfs and hdfsresource jar. > This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 > when starting all services after Enabling HA. > Retry count and timeout should be clarified, as sometimes it may take a long > time for namenode to exit safemode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17901) Make HDFS operations resilient to namenode safemode
Sandor Magyari created AMBARI-17901: --- Summary: Make HDFS operations resilient to namenode safemode Key: AMBARI-17901 URL: https://issues.apache.org/jira/browse/AMBARI-17901 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Sandor Magyari Fix For: 2.5.0 HdfsResourceJar and HdfsResourceWebHDFS (WebHDFSUtil) are the classes that carry out the HDFS operations. All retry able operations (e.g. SETPERMISSION) should be guarded with retry logic that would retry the operation until a given timeout before giving up and bailing out. To determine which HDFS operations are retry able might be as easy as just looking the returned status/error code or the type of the exception (e.g. "RetriableException") though this needs to be verified if it's consistent with both the webhdfs and hdfsresource jar. This problem came up in https://issues.apache.org/jira/browse/AMBARI-17182 when starting all services after Enabling HA. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17889) Bad error message if user has not performed ambari-server setup for jdbc driver before configuring custom DB
[
https://issues.apache.org/jira/browse/AMBARI-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17889:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Bad error message if user has not performed ambari-server setup for jdbc
> driver before configuring custom DB
>
>
> Key: AMBARI-17889
> URL: https://issues.apache.org/jira/browse/AMBARI-17889
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-17889.patch
>
>
> While installing a cluster, I forgot to call:
> {{ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java.jar}}
> Check DB connection failed with:
> {code}
> 2016-07-13 00:56:32,751 - There was an unknown error while checking database
> connectivity: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 144, in actionexecute
> db_connection_check_structured_output =
> self.execute_db_connection_check(config, tmp_dir)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 285, in execute_db_connection_check
> jdbc_url = jdk_location + jdbc_driver_mysql_name
> TypeError: cannot concatenate 'str' and 'NoneType' objects
> 2016-07-13 00:56:32,752 - Check db_connection_check was unsuccessful. Exit
> code: 1. Message: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 506, in
> CheckHost().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 206, in actionexecute
> raise Fail(error_message)
> resource_management.core.exceptions.Fail: Check db_connection_check was
> unsuccessful. Exit code: 1. Message: cannot concatenate 'str' and 'NoneType'
> objects
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17882) Add new macros for collections
[ https://issues.apache.org/jira/browse/AMBARI-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-17882: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add new macros for collections > -- > > Key: AMBARI-17882 > URL: https://issues.apache.org/jira/browse/AMBARI-17882 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: trunk > > Attachments: AMBARI-17882.patch > > > ||Macros Name||Description||Has Alias for tests|| > |someByKey|A computed property that returns true of some collection's item > has property with needed value. > Needed value is stored in the another property|✔| > |everyByKey|A computed property that returns true of all collection's items > have property with needed value. > Needed value is stored in the another property|✔| > |filterByKey|A computed property that returns array with collection's items > that have needed property value. > Needed value is stored in the another property|✔| > |findByKey|A computed property that returns first collection's item that has > needed property value. > Needed value is stored in the another property|✔| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17882) Add new macros for collections
[
https://issues.apache.org/jira/browse/AMBARI-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393813#comment-15393813
]
Oleg Nechiporenko commented on AMBARI-17882:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [01:19 min]
[INFO] Ambari Server .. FAILURE [ 01:27 h]
{noformat}
> Add new macros for collections
> --
>
> Key: AMBARI-17882
> URL: https://issues.apache.org/jira/browse/AMBARI-17882
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: trunk
>
> Attachments: AMBARI-17882.patch
>
>
> ||Macros Name||Description||Has Alias for tests||
> |someByKey|A computed property that returns true of some collection's item
> has property with needed value.
> Needed value is stored in the another property|✔|
> |everyByKey|A computed property that returns true of all collection's items
> have property with needed value.
> Needed value is stored in the another property|✔|
> |filterByKey|A computed property that returns array with collection's items
> that have needed property value.
> Needed value is stored in the another property|✔|
> |findByKey|A computed property that returns first collection's item that has
> needed property value.
> Needed value is stored in the another property|✔|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17877) Some configs with empty value shown on "Customize Service" page are not saved in the configuration type
[ https://issues.apache.org/jira/browse/AMBARI-17877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-17877: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Some configs with empty value shown on "Customize Service" page are not saved > in the configuration type > --- > > Key: AMBARI-17877 > URL: https://issues.apache.org/jira/browse/AMBARI-17877 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17877.patch > > > *STR:* > # Start installer wizard and select HDP-2.5 stack and storm as a service > # On Customize Services page nimbus.impersonation.authorizer and > nimbus.impersonation.acl are shown with empty values > # On deploying cluster, properties are not saved in storm-site > *Expected Result:* Properties like nimbus.impersonation.authorizer and > nimbus.impersonation.acl does not have value tag defined in their stack > definition. Such properties are received with value as null from API. Any > property with null value should not be shown on "Customize Services" page > unless stack advisor sets another value to the property > *Actual Result:* Properties with null value are shown as having empty string > value on "Customize Services" page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17877) Some configs with empty value shown on "Customize Service" page are not saved in the configuration type
[
https://issues.apache.org/jira/browse/AMBARI-17877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393812#comment-15393812
]
Oleg Nechiporenko commented on AMBARI-17877:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [01:19 min]
[INFO] Ambari Server .. FAILURE [ 01:25 h]
{noformat}
> Some configs with empty value shown on "Customize Service" page are not saved
> in the configuration type
> ---
>
> Key: AMBARI-17877
> URL: https://issues.apache.org/jira/browse/AMBARI-17877
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17877.patch
>
>
> *STR:*
> # Start installer wizard and select HDP-2.5 stack and storm as a service
> # On Customize Services page nimbus.impersonation.authorizer and
> nimbus.impersonation.acl are shown with empty values
> # On deploying cluster, properties are not saved in storm-site
> *Expected Result:* Properties like nimbus.impersonation.authorizer and
> nimbus.impersonation.acl does not have value tag defined in their stack
> definition. Such properties are received with value as null from API. Any
> property with null value should not be shown on "Customize Services" page
> unless stack advisor sets another value to the property
> *Actual Result:* Properties with null value are shown as having empty string
> value on "Customize Services" page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393811#comment-15393811
]
Oleg Nechiporenko commented on AMBARI-17900:
Committed to trunk and 2.4.
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393806#comment-15393806
]
Andrii Babiichuk commented on AMBARI-17900:
---
+1 for the patch
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393804#comment-15393804
]
Oleg Nechiporenko commented on AMBARI-17900:
29404 tests complete (28 seconds)
154 tests pending
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-17900:
---
Attachment: AMBARI-17900.patch
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17900) Disabling Alert Definition causes JS error
[
https://issues.apache.org/jira/browse/AMBARI-17900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-17900:
---
Status: Patch Available (was: Open)
Patch added
> Disabling Alert Definition causes JS error
> --
>
> Key: AMBARI-17900
> URL: https://issues.apache.org/jira/browse/AMBARI-17900
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17900.patch
>
>
> * Install cluster HDFS
> * Stop HDFS
> * Go to alert definition "DataNode Web UI" page
> * Click on "Enabled" (to disable it)
> * Confirm
> *AR* JS error appears
> {noformat}Uncaught TypeError: Cannot read property 'count' of
> undefined{noformat}
> *ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17899) Login flow break when only ldap auth is enabled
Hayat Behlim created AMBARI-17899: - Summary: Login flow break when only ldap auth is enabled Key: AMBARI-17899 URL: https://issues.apache.org/jira/browse/AMBARI-17899 Project: Ambari Issue Type: Bug Components: logsearch Affects Versions: 2.4.0 Reporter: Hayat Behlim Assignee: Hayat Behlim Fix For: 2.4.0 *Actual :* When property logsearch.auth.ldap.enable=true and other authentication methods are disabled then user can login with any username and password. *Excepted* User should login only for valid ldap users. #set properties value to reproduce this issue logsearch.auth.file.enable=false logsearch.auth.ldap.enable=true logsearch.auth.simple.enable=false logsearch.auth.external_auth.enable=false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17900) Disabling Alert Definition causes JS error
Oleg Nechiporenko created AMBARI-17900:
--
Summary: Disabling Alert Definition causes JS error
Key: AMBARI-17900
URL: https://issues.apache.org/jira/browse/AMBARI-17900
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
Fix For: 2.4.0
* Install cluster HDFS
* Stop HDFS
* Go to alert definition "DataNode Web UI" page
* Click on "Enabled" (to disable it)
* Confirm
*AR* JS error appears
{noformat}Uncaught TypeError: Cannot read property 'count' of
undefined{noformat}
*ER* JS error doesn't appear
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17893) HBase OOM while booting
[
https://issues.apache.org/jira/browse/AMBARI-17893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393767#comment-15393767
]
Hudson commented on AMBARI-17893:
-
FAILURE: Integrated in Ambari-trunk-Commit #5388 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5388/])
AMBARI-17893. HBase OOM while booting.(vbrodetskyi) (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bcef91c8d985c134c04a923491d7ff3e2c6f915f])
*
ambari-server/src/main/resources/stacks/HDP/2.2/services/HBASE/configuration/hbase-env.xml
*
ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/configuration/hbase-env.xml
> HBase OOM while booting
> ---
>
> Key: AMBARI-17893
> URL: https://issues.apache.org/jira/browse/AMBARI-17893
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17893.patch
>
>
> Caused by: java.lang.OutOfMemoryError: Direct buffer memory
> at java.nio.Bits.reserveMemory(Bits.java:658)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> org.apache.hadoop.hbase.util.ByteBufferArray.(ByteBufferArray.java:65)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.ByteBufferIOEngine.(ByteBufferIOEngine.java:47)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getIOEngineFromName(BucketCache.java:307)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.(BucketCache.java:217)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:614)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:553)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:637)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:231)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:561)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:410)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2507)
> This issue has been resolved by adding below config entry in hbase-env.
> export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS
> {% if hbase_max_direct_memory_size %}
> -XX:MaxDirectMemorySize={{hbase_max_direct_memory_size}}m
> {% endif %}
> "
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17889) Bad error message if user has not performed ambari-server setup for jdbc driver before configuring custom DB
[
https://issues.apache.org/jira/browse/AMBARI-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17889:
---
Attachment: (was: AMBARI-17889.patch)
> Bad error message if user has not performed ambari-server setup for jdbc
> driver before configuring custom DB
>
>
> Key: AMBARI-17889
> URL: https://issues.apache.org/jira/browse/AMBARI-17889
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-17889.patch
>
>
> While installing a cluster, I forgot to call:
> {{ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java.jar}}
> Check DB connection failed with:
> {code}
> 2016-07-13 00:56:32,751 - There was an unknown error while checking database
> connectivity: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 144, in actionexecute
> db_connection_check_structured_output =
> self.execute_db_connection_check(config, tmp_dir)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 285, in execute_db_connection_check
> jdbc_url = jdk_location + jdbc_driver_mysql_name
> TypeError: cannot concatenate 'str' and 'NoneType' objects
> 2016-07-13 00:56:32,752 - Check db_connection_check was unsuccessful. Exit
> code: 1. Message: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 506, in
> CheckHost().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 206, in actionexecute
> raise Fail(error_message)
> resource_management.core.exceptions.Fail: Check db_connection_check was
> unsuccessful. Exit code: 1. Message: cannot concatenate 'str' and 'NoneType'
> objects
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17889) Bad error message if user has not performed ambari-server setup for jdbc driver before configuring custom DB
[
https://issues.apache.org/jira/browse/AMBARI-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17889:
---
Attachment: AMBARI-17889.patch
> Bad error message if user has not performed ambari-server setup for jdbc
> driver before configuring custom DB
>
>
> Key: AMBARI-17889
> URL: https://issues.apache.org/jira/browse/AMBARI-17889
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-17889.patch
>
>
> While installing a cluster, I forgot to call:
> {{ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/usr/share/java/mysql-connector-java.jar}}
> Check DB connection failed with:
> {code}
> 2016-07-13 00:56:32,751 - There was an unknown error while checking database
> connectivity: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 144, in actionexecute
> db_connection_check_structured_output =
> self.execute_db_connection_check(config, tmp_dir)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 285, in execute_db_connection_check
> jdbc_url = jdk_location + jdbc_driver_mysql_name
> TypeError: cannot concatenate 'str' and 'NoneType' objects
> 2016-07-13 00:56:32,752 - Check db_connection_check was unsuccessful. Exit
> code: 1. Message: cannot concatenate 'str' and 'NoneType' objects
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 506, in
> CheckHost().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py",
> line 206, in actionexecute
> raise Fail(error_message)
> resource_management.core.exceptions.Fail: Check db_connection_check was
> unsuccessful. Exit code: 1. Message: cannot concatenate 'str' and 'NoneType'
> objects
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393726#comment-15393726
]
Hudson commented on AMBARI-17041:
-
ABORTED: Integrated in Ambari-trunk-Commit #5387 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5387/])
AMBARI-17041. Support password type for custom properties (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2fb19c7b1a0497a40df8d11e7d426190836d6a24])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* ambari-web/app/messages.js
* ambari-web/app/models/configs/objects/service_config_property.js
*
ambari-server/src/main/java/org/apache/ambari/server/controller/ConfigurationResponse.java
*
ambari-server/src/main/java/org/apache/ambari/server/utils/SecretReference.java
* ambari-web/test/mixins/common/configs/configs_saver_test.js
* ambari-web/app/utils/config.js
* ambari-web/app/templates/common/configs/addPropertyWindow.hbs
* ambari-web/app/views/common/configs/service_configs_by_category_view.js
* ambari-web/app/mixins/common/configs/configs_saver.js
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Fix For: 2.5.0
>
> Attachments: AMBARI-17041-July14.patch, AMBARI-17041-July15.patch,
> AMBARI-17041-July20.patch, AMBARI-17041-July21-ES6.patch,
> AMBARI-17041-July21-updated.patch, AMBARI-17041-July22.patch,
> AMBARI-17041-trunk-July08.patch, AMBARI-17041-trunk-Jun29.patch,
> AMBARI-17041-trunk.patch, add_property_pop_up.tiff,
> ambari_web_failed_to_execute_test.png,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, property_type_schema.tiff,
> schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17881) Cover configurations theme with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-17881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393727#comment-15393727 ] Hudson commented on AMBARI-17881: - ABORTED: Integrated in Ambari-trunk-Commit #5387 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5387/]) AMBARI-17881 Cover configurations theme with unit tests. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=08644fa7cd043cb1f3ee6052b382f96d266b028e]) * ambari-web/test/utils/configs/theme/theme_test.js * ambari-web/app/utils/configs/theme/theme.js * ambari-web/app/assets/test/tests.js > Cover configurations theme with unit tests > -- > > Key: AMBARI-17881 > URL: https://issues.apache.org/jira/browse/AMBARI-17881 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: trunk > > Attachments: AMBARI-17881.patch > > > Cover following files: > * /ambari-web/app/utils/configs/theme/theme.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17893) HBase OOM while booting
[
https://issues.apache.org/jira/browse/AMBARI-17893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17893:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> HBase OOM while booting
> ---
>
> Key: AMBARI-17893
> URL: https://issues.apache.org/jira/browse/AMBARI-17893
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17893.patch
>
>
> Caused by: java.lang.OutOfMemoryError: Direct buffer memory
> at java.nio.Bits.reserveMemory(Bits.java:658)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at
> org.apache.hadoop.hbase.util.ByteBufferArray.(ByteBufferArray.java:65)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.ByteBufferIOEngine.(ByteBufferIOEngine.java:47)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getIOEngineFromName(BucketCache.java:307)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.(BucketCache.java:217)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:614)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:553)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:637)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:231)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:561)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:410)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2507)
> This issue has been resolved by adding below config entry in hbase-env.
> export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS
> {% if hbase_max_direct_memory_size %}
> -XX:MaxDirectMemorySize={{hbase_max_direct_memory_size}}m
> {% endif %}
> "
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17788) Refactor spooler code in OutputHDFSFile to be reusable for OutputS3File
[
https://issues.apache.org/jira/browse/AMBARI-17788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393636#comment-15393636
]
Hadoop QA commented on AMBARI-17788:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12820104/AMBARI-17788-3.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8155//console
This message is automatically generated.
> Refactor spooler code in OutputHDFSFile to be reusable for OutputS3File
> ---
>
> Key: AMBARI-17788
> URL: https://issues.apache.org/jira/browse/AMBARI-17788
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Attachments: AMBARI-17788-3.patch, AMBARI-17788.patch
>
>
> AMBARI-17785 proposed to enhance logsearch capabilities to periodically
> upload logs to S3, by using a spooling mechanism. [~mdharmesh] pointed out
> that such a facility already exists in the HDFS file copy handling. Looking
> at the code, there is a lot of similarity that can be reused in both cases.
> This task is to extract the common mechanisms and parameterize them so that
> it will make it easier to reuse and also help have similar improvements to
> spooling logic if any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393635#comment-15393635 ] zhangxiaolu commented on AMBARI-17850: -- ok, repatch again.thank you. > HttpPropertyProviderTest.java cannot pass > - > > Key: AMBARI-17850 > URL: https://issues.apache.org/jira/browse/AMBARI-17850 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Labels: severe > Fix For: 2.1.1 > > Attachments: > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-17850: - Attachment: AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > HttpPropertyProviderTest.java cannot pass > - > > Key: AMBARI-17850 > URL: https://issues.apache.org/jira/browse/AMBARI-17850 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Labels: severe > Fix For: 2.1.1 > > Attachments: > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-17850: - Attachment: (was: AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch) > HttpPropertyProviderTest.java cannot pass > - > > Key: AMBARI-17850 > URL: https://issues.apache.org/jira/browse/AMBARI-17850 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Labels: severe > Fix For: 2.1.1 > > Attachments: > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[
https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393598#comment-15393598
]
Hadoop QA commented on AMBARI-17850:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12820128/AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.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/8154//console
This message is automatically generated.
> HttpPropertyProviderTest.java cannot pass
> -
>
> Key: AMBARI-17850
> URL: https://issues.apache.org/jira/browse/AMBARI-17850
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: zhangxiaolu
> Labels: severe
> Fix For: 2.1.1
>
> Attachments:
> AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14384) Ambari Metrics doesn't use SPNEGO to authenticate
[ https://issues.apache.org/jira/browse/AMBARI-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393506#comment-15393506 ] Qin Liu commented on AMBARI-14384: -- AMBARI-17898 is created as a subtask of this task. > Ambari Metrics doesn't use SPNEGO to authenticate > - > > Key: AMBARI-14384 > URL: https://issues.apache.org/jira/browse/AMBARI-14384 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.1.2 >Reporter: Ward Viaene > > * Kerberos enabled cluster > * SPNEGO enabled on hadoop APIs > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... > The same problem appears to be happening on the sinks: > * > ambari/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java > ** No SPNEGO support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-17850: - Attachment: (was: AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch) > HttpPropertyProviderTest.java cannot pass > - > > Key: AMBARI-17850 > URL: https://issues.apache.org/jira/browse/AMBARI-17850 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Labels: severe > Fix For: 2.1.1 > > Attachments: > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
Qin Liu created AMBARI-17898: Summary: Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor Key: AMBARI-17898 URL: https://issues.apache.org/jira/browse/AMBARI-17898 Project: Ambari Issue Type: Improvement Components: ambari-metrics Affects Versions: 2.2.0 Reporter: Qin Liu Assignee: Qin Liu This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to authenticate". In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does not support Kerberos HTTP SPNEGO authentication. /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: http://metrics-collector:6188/ws/v1/timeline/metrics 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to server. HTTP Error 401: Authentication required 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13401) Fail to start services since cannot check/create users
[
https://issues.apache.org/jira/browse/AMBARI-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393476#comment-15393476
]
zhangxiaolu commented on AMBARI-13401:
--
thank you very much. I reset ambari-server and the problem has resolved, thank
you.
> Fail to start services since cannot check/create users
> --
>
> Key: AMBARI-13401
> URL: https://issues.apache.org/jira/browse/AMBARI-13401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
> Environment: centos6.5
>Reporter: zhangxiaolu
> Attachments: Screen Shot 2016-03-22 at 10.26.40 AM.png, Screen Shot
> 2016-03-22 at 10.27.23 AM.png, command-3308.json
>
>
> Installed Ambari 2.2.0
> HDP 2.3.2.0-2950
> Some services started, but ZKFC, Kafka, Resource Manager, AMS, are no longer
> starting.
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 35, in
> BeforeAnyHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 30, in hook
> setup_users()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
> line 76, in setup_users
> ignore_failures = params.ignore_groupsusers_create
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 152, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 118, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 44, in action_create
> if not self.user:
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 93, in user
> return pwd.getpwnam(self.resource.username)
> TypeError: getpwnam() argument 1 must be string, not None
> Error: Error: Unable to run the custom hook script ['/usr/bin/python2.6',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
> 'ANY', '/var/lib/ambari-agent/data/command-404.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
> '/var/lib/ambari-agent/data/structured-out-404.json', 'INFO',
> '/var/lib/ambari-agent/data/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17850) HttpPropertyProviderTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-17850: - Attachment: AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > HttpPropertyProviderTest.java cannot pass > - > > Key: AMBARI-17850 > URL: https://issues.apache.org/jira/browse/AMBARI-17850 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Labels: severe > Fix For: 2.1.1 > > Attachments: > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch, > > AMBARI-17850-HttpPropertyProviderTest-testReadResourceManager-Cannot-pass.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
