[jira] [Created] (AMBARI-16698) Log Search UI uses color codes for only upper case log levels.
Dharmesh Makwana created AMBARI-16698: - Summary: Log Search UI uses color codes for only upper case log levels. Key: AMBARI-16698 URL: https://issues.apache.org/jira/browse/AMBARI-16698 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Dharmesh Makwana Priority: Minor Fix For: 2.4.0 Log level color code doesn't show up, if log levels are not in upper case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16697) Remote Cluster: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-16697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-16697: - Status: Patch Available (was: Open) > Remote Cluster: UX edits #1 > --- > > Key: AMBARI-16697 > URL: https://issues.apache.org/jira/browse/AMBARI-16697 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16697_trunk.patch, remote-cluster-ui-edits-v1.pptx > > > Usability and UX edits. See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16697) Remote Cluster: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-16697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-16697: - Attachment: AMBARI-16697_trunk.patch > Remote Cluster: UX edits #1 > --- > > Key: AMBARI-16697 > URL: https://issues.apache.org/jira/browse/AMBARI-16697 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16697_trunk.patch, remote-cluster-ui-edits-v1.pptx > > > Usability and UX edits. See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16697) Remote Cluster: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-16697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-16697: - Attachment: remote-cluster-ui-edits-v1.pptx > Remote Cluster: UX edits #1 > --- > > Key: AMBARI-16697 > URL: https://issues.apache.org/jira/browse/AMBARI-16697 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.4.0 > > Attachments: remote-cluster-ui-edits-v1.pptx > > > Usability and UX edits. See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16697) Remote Cluster: UX edits #1
Pallav Kulshreshtha created AMBARI-16697: Summary: Remote Cluster: UX edits #1 Key: AMBARI-16697 URL: https://issues.apache.org/jira/browse/AMBARI-16697 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.0 Reporter: Pallav Kulshreshtha Assignee: Pallav Kulshreshtha Priority: Critical Fix For: 2.4.0 Usability and UX edits. See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16686) Support grafana dashboards to be defined based on stack
[ https://issues.apache.org/jira/browse/AMBARI-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285966#comment-15285966 ] Hudson commented on AMBARI-16686: - FAILURE: Integrated in Ambari-trunk-Commit #4855 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4855/]) AMBARI-16686. Support grafana dashboards to be defined based on stack. (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e2a1a5f8ae61cfb82834efaacb827ad7177aeecb]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-timelineserver.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-timelineserver.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hive-hiverserver2.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hdfs-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hdfs-datanodes.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-llapdaemon-heatmaps.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-system-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hive-hiverserver2.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-nodemanagers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hive-hivemetastore.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-resourcemanagers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-system-servers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-llapdaemon-overview.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hbase-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-llapdaemon-daemons.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hbase-misc.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hdfs-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-queues.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-system-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-queues.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hbase-performance.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-jobhistoryserver.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hive-hivemetastore.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-jobhistoryserver.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-hive-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-system-servers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-home.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-resourcemanagers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-performance.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/grafana-yarn-applicati
[jira] [Commented] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[
https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285964#comment-15285964
]
Josh Elser commented on AMBARI-16171:
-
Reviewboard is linked (if you didn't see the email about it already).
Also, trying again with the upgrade testing locally:
{noformat}
Exception in thread "main" org.apache.ambari.server.AmbariException
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:308)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider$ClusterTypeRegistration.instanceExists(ArtifactResourceProvider.java:711)
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider.validateParent(ArtifactResourceProvider.java:403)
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider.access$200(ArtifactResourceProvider.java:62)
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider$2.invoke(ArtifactResourceProvider.java:301)
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider$2.invoke(ArtifactResourceProvider.java:297)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.getResources(AbstractResourceProvider.java:307)
at
org.apache.ambari.server.controller.internal.ArtifactResourceProvider.getResources(ArtifactResourceProvider.java:208)
at
org.apache.ambari.server.controller.KerberosHelperImpl.getKerberosDescriptor(KerberosHelperImpl.java:1068)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.updatePhoenixConfigs(UpgradeCatalog240.java:2081)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDMLUpdates(UpgradeCatalog240.java:337)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:666)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
... 1 more
{noformat}
I got past one exception already -- had to add the following to the
{{updatePhoenixConfigs()}} method:
{code}
final ViewRegistry viewRegistry = injector.getInstance(ViewRegistry.class);
ViewRegistry.initInstance(viewRegistry);
{code}
But, to be quite honest, I'm really not sure where to start with this
exception. Some direction would be great :)
> Changes to Phoenix QueryServer Kerberos configuration
> -
>
> Key: AMBARI-16171
> URL: https://issues.apache.org/jira/browse/AMBARI-16171
> Project: Ambari
> Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
> Attachments: AMBARI-16171.001.patch, AMBARI-16171.002.patch,
> AMBARI-16171.003.patch
>
>
> The up-coming version of Phoenix will contain some new functionality to
> support Kerberos authentication of clients via SPNEGO with the Phoenix Query
> Server (PQS).
> Presently, Ambari will configure PQS to use the hbase service keytab which
> will result in the SPNEGO authentication failing as the RFC requires that the
> "primary" component of the Kerberos principal for the server is "HTTP". Thus,
> we need to ensure that we switch PQS over to use the spnego.service.keytab as
> the keytab and "HTTP/_HOST@REALM" as the principal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16687) Configuration Tasks Are Being Skipped During Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285837#comment-15285837 ] Hudson commented on AMBARI-16687: - FAILURE: Integrated in Ambari-trunk-Commit #4854 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4854/]) AMBARI-16687 - Configuration Tasks Are Being Skipped During Upgrade (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1c60f63504be0f72878a8395ccefb0165d0c996e]) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml * ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/config-upgrade.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-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.3/upgrades/config-upgrade.xml * ambari-server/src/main/java/org/apache/ambari/server/stack/StackDefinitionDirectory.java * ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradeValidityTest.java * ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test_partial.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java * ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml > Configuration Tasks Are Being Skipped During Upgrade > > > Key: AMBARI-16687 > URL: https://issues.apache.org/jira/browse/AMBARI-16687 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Attachments: AMBARI-16687.patch > > > During an upgrade from HDP 2.x to 2.y, all of the configuration tasks are > being shown as skipped. This is due to AMBARI-15222 where the configuration > packs were being calculated incorrectly resulting in empty maps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16696) Enabling/Disabling interactive query should sustain browser refreshes
[
https://issues.apache.org/jira/browse/AMBARI-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-16696:
Status: Patch Available (was: Open)
Verified manually that the patch addresses the issue on a cluster
Verified that all ambari-web unit tests works:
27817 tests complete (31 seconds)
154 tests pending
> Enabling/Disabling interactive query should sustain browser refreshes
> -
>
> Key: AMBARI-16696
> URL: https://issues.apache.org/jira/browse/AMBARI-16696
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.4.0
>
> Attachments: AMBARI-16696.patch
>
>
> *STR:*
> # Enable interactive query and save the hive configs
> # This will create requests that can be tracked in background ops
> # While a task "Restart LLAP" or "Install Components" is ongoing, Refresh
> the browser
> *Expected Result:* The ongoing request should be completed and subsequent
> requests ("Start HiveServer2 Interactive") should be triggered
> *Actual Result:* The ongoing request is completed but the subsequent request
> is not triggered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16696) Enabling/Disabling interactive query should sustain browser refreshes
[
https://issues.apache.org/jira/browse/AMBARI-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-16696:
Attachment: AMBARI-16696.patch
> Enabling/Disabling interactive query should sustain browser refreshes
> -
>
> Key: AMBARI-16696
> URL: https://issues.apache.org/jira/browse/AMBARI-16696
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.4.0
>
> Attachments: AMBARI-16696.patch
>
>
> *STR:*
> # Enable interactive query and save the hive configs
> # This will create requests that can be tracked in background ops
> # While a task "Restart LLAP" or "Install Components" is ongoing, Refresh
> the browser
> *Expected Result:* The ongoing request should be completed and subsequent
> requests ("Start HiveServer2 Interactive") should be triggered
> *Actual Result:* The ongoing request is completed but the subsequent request
> is not triggered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16686) Support grafana dashboards to be defined based on stack
[ https://issues.apache.org/jira/browse/AMBARI-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-16686: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.4 and trunk. > Support grafana dashboards to be defined based on stack > --- > > Key: AMBARI-16686 > URL: https://issues.apache.org/jira/browse/AMBARI-16686 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.4.0 > > Attachments: AMBARI-16686.patch > > > Grafana dashboard definition should be based on the stack that is deployed by > Ambari. > Currently we create same dashboard definitions for all stacks which might not > have the supported services defined. > The dashboards need to be classified per stack basis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16696) Enabling/Disabling interactive query should sustain browser refreshes
[
https://issues.apache.org/jira/browse/AMBARI-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-16696:
Description:
*STR:*
# Enable interactive query and save the hive configs
# This will create requests that can be tracked in background ops
# While a task "Restart LLAP" or "Install Components" is ongoing, Refresh the
browser
*Expected Result:* The ongoing request should be completed and subsequent
requests ("Start HiveServer2 Interactive") should be triggered
*Actual Result:* The ongoing request is completed but the subsequent request is
not triggered.
> Enabling/Disabling interactive query should sustain browser refreshes
> -
>
> Key: AMBARI-16696
> URL: https://issues.apache.org/jira/browse/AMBARI-16696
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.4.0
>
>
> *STR:*
> # Enable interactive query and save the hive configs
> # This will create requests that can be tracked in background ops
> # While a task "Restart LLAP" or "Install Components" is ongoing, Refresh
> the browser
> *Expected Result:* The ongoing request should be completed and subsequent
> requests ("Start HiveServer2 Interactive") should be triggered
> *Actual Result:* The ongoing request is completed but the subsequent request
> is not triggered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16696) Enabling/Disabling interactive query should sustain browser refreshes
Jaimin D Jetly created AMBARI-16696: --- Summary: Enabling/Disabling interactive query should sustain browser refreshes Key: AMBARI-16696 URL: https://issues.apache.org/jira/browse/AMBARI-16696 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16671) clean up import * for MAHOUT service
[ https://issues.apache.org/jira/browse/AMBARI-16671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16671: --- Fix Version/s: (was: trunk) 3.0.0 > clean up import * for MAHOUT service > > > Key: AMBARI-16671 > URL: https://issues.apache.org/jira/browse/AMBARI-16671 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16101) clean up import * at common-services level
[ https://issues.apache.org/jira/browse/AMBARI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16101: --- Fix Version/s: (was: ambari-2.4.0) 3.0.0 > clean up import * at common-services level > -- > > Key: AMBARI-16101 > URL: https://issues.apache.org/jira/browse/AMBARI-16101 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This JIRA and subtasks will clean up import * from resource_management and > replace it for specific imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16671) clean up import * for MAHOUT service
[ https://issues.apache.org/jira/browse/AMBARI-16671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16671: --- Affects Version/s: 2.4.0 > clean up import * for MAHOUT service > > > Key: AMBARI-16671 > URL: https://issues.apache.org/jira/browse/AMBARI-16671 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16695) HDFS Alerts: add minimum values to AMS alerts
[
https://issues.apache.org/jira/browse/AMBARI-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-16695:
-
Attachment: AMBARI-16695.patch
> HDFS Alerts: add minimum values to AMS alerts
> -
>
> Key: AMBARI-16695
> URL: https://issues.apache.org/jira/browse/AMBARI-16695
> Project: Ambari
> Issue Type: Improvement
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Attachments: AMBARI-16695.patch
>
>
> There are new HDFS alerts that watch growth rates. Some (like RPC) have
> "minimum" values, meaning we ignore growth until we are past a certain value
> (like latency in seconds).
> There are a few other alerts that I think also need minimums. Or maybe need
> higher warning thresholds. Or both...
> ==
> NameNode Heap Usage (Daily) increase_nn_heap_usage_daily
> I'm getting these WARNINGS with a Heap of < 100MB.
> {code}
> The variance for this alert is 25MB which is 30% of the 82MB average (16MB is
> the limit).
> {code}
>
> HDFS Storage Capacity Usage (Weekly)
> namenode_increase_in_storage_capacity_usage_weekly
> I'm getting these WARNINGS when only using such a small amount of storage...
> {code}
> The variance for this alert is 21,328B which is 20% of the 107,758B average
> (10,776B is the limit)
> {code}
> Here is what is used...
> {code}
> Disk Usage (DFS Used) 112.0 KB / 428.1 GB (0.00%)
> Disk Usage (Non DFS Used) 32.0 GB / 428.1 GB (7.47%)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16695) HDFS Alerts: add minimum values to AMS alerts
[
https://issues.apache.org/jira/browse/AMBARI-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-16695:
-
Status: Patch Available (was: Open)
> HDFS Alerts: add minimum values to AMS alerts
> -
>
> Key: AMBARI-16695
> URL: https://issues.apache.org/jira/browse/AMBARI-16695
> Project: Ambari
> Issue Type: Improvement
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Attachments: AMBARI-16695.patch
>
>
> There are new HDFS alerts that watch growth rates. Some (like RPC) have
> "minimum" values, meaning we ignore growth until we are past a certain value
> (like latency in seconds).
> There are a few other alerts that I think also need minimums. Or maybe need
> higher warning thresholds. Or both...
> ==
> NameNode Heap Usage (Daily) increase_nn_heap_usage_daily
> I'm getting these WARNINGS with a Heap of < 100MB.
> {code}
> The variance for this alert is 25MB which is 30% of the 82MB average (16MB is
> the limit).
> {code}
>
> HDFS Storage Capacity Usage (Weekly)
> namenode_increase_in_storage_capacity_usage_weekly
> I'm getting these WARNINGS when only using such a small amount of storage...
> {code}
> The variance for this alert is 21,328B which is 20% of the 107,758B average
> (10,776B is the limit)
> {code}
> Here is what is used...
> {code}
> Disk Usage (DFS Used) 112.0 KB / 428.1 GB (0.00%)
> Disk Usage (Non DFS Used) 32.0 GB / 428.1 GB (7.47%)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16695) HDFS Alerts: add minimum values to AMS alerts
[
https://issues.apache.org/jira/browse/AMBARI-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285739#comment-15285739
]
Siddharth Wagle commented on AMBARI-16695:
--
|| Alert || Existing Default thresholds (warn/crit) || Minimum value ||
| increase_nn_heap_usage_daily | 20 / 50 | 100 MB |
| increase_nn_heap_usage_weekly | 20 / 50 | 1 GB |
| namenode_increase_in_storage_capacity_usage_daily | 30 / 50 | 100 MB |
| namenode_increase_in_storage_capacity_usage_weekly | 10 / 20 | 1 GB |
Effectively we will not alert if user adds < 100 MB every day and fills up the
cluster. I still think it make common sense to have these.
> HDFS Alerts: add minimum values to AMS alerts
> -
>
> Key: AMBARI-16695
> URL: https://issues.apache.org/jira/browse/AMBARI-16695
> Project: Ambari
> Issue Type: Improvement
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>
> There are new HDFS alerts that watch growth rates. Some (like RPC) have
> "minimum" values, meaning we ignore growth until we are past a certain value
> (like latency in seconds).
> There are a few other alerts that I think also need minimums. Or maybe need
> higher warning thresholds. Or both...
> ==
> NameNode Heap Usage (Daily) increase_nn_heap_usage_daily
> I'm getting these WARNINGS with a Heap of < 100MB.
> {code}
> The variance for this alert is 25MB which is 30% of the 82MB average (16MB is
> the limit).
> {code}
>
> HDFS Storage Capacity Usage (Weekly)
> namenode_increase_in_storage_capacity_usage_weekly
> I'm getting these WARNINGS when only using such a small amount of storage...
> {code}
> The variance for this alert is 21,328B which is 20% of the 107,758B average
> (10,776B is the limit)
> {code}
> Here is what is used...
> {code}
> Disk Usage (DFS Used) 112.0 KB / 428.1 GB (0.00%)
> Disk Usage (Non DFS Used) 32.0 GB / 428.1 GB (7.47%)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16695) HDFS Alerts: add minimum values to AMS alerts
Siddharth Wagle created AMBARI-16695:
Summary: HDFS Alerts: add minimum values to AMS alerts
Key: AMBARI-16695
URL: https://issues.apache.org/jira/browse/AMBARI-16695
Project: Ambari
Issue Type: Improvement
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
There are new HDFS alerts that watch growth rates. Some (like RPC) have
"minimum" values, meaning we ignore growth until we are past a certain value
(like latency in seconds).
There are a few other alerts that I think also need minimums. Or maybe need
higher warning thresholds. Or both...
==
NameNode Heap Usage (Daily) increase_nn_heap_usage_daily
I'm getting these WARNINGS with a Heap of < 100MB.
{code}
The variance for this alert is 25MB which is 30% of the 82MB average (16MB is
the limit).
{code}
HDFS Storage Capacity Usage (Weekly)
namenode_increase_in_storage_capacity_usage_weekly
I'm getting these WARNINGS when only using such a small amount of storage...
{code}
The variance for this alert is 21,328B which is 20% of the 107,758B average
(10,776B is the limit)
{code}
Here is what is used...
{code}
Disk Usage (DFS Used) 112.0 KB / 428.1 GB (0.00%)
Disk Usage (Non DFS Used) 32.0 GB / 428.1 GB (7.47%)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16694) Remove unused parameters from hawq-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16694: Assignee: bhuvnesh chaudhary Fix Version/s: 2.4.1 2.4.0 Status: Patch Available (was: Open) > Remove unused parameters from hawq-site.xml > --- > > Key: AMBARI-16694 > URL: https://issues.apache.org/jira/browse/AMBARI-16694 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0, 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0, 2.4.1 > > Attachments: AMBARI-16694.patch > > > Remove the below unused parameters from hawq-site.xml > - hawq_re_cgroup_hierarchy_name > - hawq_re_cgroup_mount_point > - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16694) Remove unused parameters from hawq-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16694: Attachment: AMBARI-16694.patch > Remove unused parameters from hawq-site.xml > --- > > Key: AMBARI-16694 > URL: https://issues.apache.org/jira/browse/AMBARI-16694 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0, 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0, 2.4.1 > > Attachments: AMBARI-16694.patch > > > Remove the below unused parameters from hawq-site.xml > - hawq_re_cgroup_hierarchy_name > - hawq_re_cgroup_mount_point > - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16694) Remove unused parameters from hawq-site.xml
bhuvnesh chaudhary created AMBARI-16694: --- Summary: Remove unused parameters from hawq-site.xml Key: AMBARI-16694 URL: https://issues.apache.org/jira/browse/AMBARI-16694 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.2.0, 2.4.0 Reporter: bhuvnesh chaudhary Remove the below unused parameters from hawq-site.xml - hawq_re_cgroup_hierarchy_name - hawq_re_cgroup_mount_point - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16688) Ambari users page is not showing type for users
[ https://issues.apache.org/jira/browse/AMBARI-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285667#comment-15285667 ] Hudson commented on AMBARI-16688: - FAILURE: Integrated in Ambari-trunk-Commit #4853 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4853/]) AMBARI-16688: Ambari users page is not showing type for users (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b2ece8c2bee477d0aab81ff35ce2e6032a639ef8]) * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/User.js > Ambari users page is not showing type for users > --- > > Key: AMBARI-16688 > URL: https://issues.apache.org/jira/browse/AMBARI-16688 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-16688.patch > > > Login to ambari > Navigate to Users page > Add few users > Verify type is displayed for each User > Actual: Type is displayed as blank for users currently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15966: - Assignee: Jaimin D Jetly (was: Yusaku Sako) > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16693) Atlas Server script error during upgrade.
[
https://issues.apache.org/jira/browse/AMBARI-16693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-16693:
---
Status: Patch Available (was: In Progress)
> Atlas Server script error during upgrade.
> -
>
> Key: AMBARI-16693
> URL: https://issues.apache.org/jira/browse/AMBARI-16693
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> An error {{kafka_broker_hosts' was not found in configurations dictionary!}}
> is seen during upgrade ...
> {code}
> {
> "href" :
> "http://172.22.64.238:8080/api/v1/clusters/cl1/requests/59/tasks/597";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "STOP",
> "command_detail" : "ATLAS_SERVER STOP",
> "end_time" : 1463369271424,
> "error_log" : "/var/lib/ambari-agent/data/errors-597.txt",
> "exit_code" : 1,
> "host_name" : "os-r6-swuvps-upg-sanity-211-5.openstacklocal",
> "id" : 597,
> "output_log" : "/var/lib/ambari-agent/data/output-597.txt",
> "request_id" : 59,
> "role" : "ATLAS_SERVER",
> "stage_id" : 0,
> "start_time" : 1463369268252,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
> line 165, in \nMetadataServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 254, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
> line 82, in stop\nimport params\n File
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py\",
> line 139, in \nif not len(kafka_broker_hosts) == 0:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'kafka_broker_hosts' was not found in configurations dictionary!",
> "stdout" : "\n\nCommand failed after 1 tries\n",
> "structured_out" : { }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285377#comment-15285377 ] Hudson commented on AMBARI-16684: - FAILURE: Integrated in Ambari-trunk-Commit #4852 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4852/]) AMBARI-16684. Ranger Tagsync component (added in HDP-2.5) is shown under (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=93a045df49b48de52cbd39821e89cfd65e49d923]) * ambari-web/app/templates/main/service/services/ranger.hbs * ambari-web/app/views/main/service/services/ranger.js * ambari-web/test/views/main/service/services/ranger_test.js * ambari-web/app/controllers/wizard/step8_controller.js > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16693) Atlas Server script error during upgrade.
Tom Beerbower created AMBARI-16693:
--
Summary: Atlas Server script error during upgrade.
Key: AMBARI-16693
URL: https://issues.apache.org/jira/browse/AMBARI-16693
Project: Ambari
Issue Type: Bug
Reporter: Tom Beerbower
Assignee: Tom Beerbower
An error {{kafka_broker_hosts' was not found in configurations dictionary!}} is
seen during upgrade ...
{code}
{
"href" :
"http://172.22.64.238:8080/api/v1/clusters/cl1/requests/59/tasks/597";,
"Tasks" : {
"attempt_cnt" : 1,
"cluster_name" : "cl1",
"command" : "STOP",
"command_detail" : "ATLAS_SERVER STOP",
"end_time" : 1463369271424,
"error_log" : "/var/lib/ambari-agent/data/errors-597.txt",
"exit_code" : 1,
"host_name" : "os-r6-swuvps-upg-sanity-211-5.openstacklocal",
"id" : 597,
"output_log" : "/var/lib/ambari-agent/data/output-597.txt",
"request_id" : 59,
"role" : "ATLAS_SERVER",
"stage_id" : 0,
"start_time" : 1463369268252,
"status" : "FAILED",
"stderr" : "Traceback (most recent call last):\n File
\"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
line 165, in \nMetadataServer().execute()\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
line 254, in execute\nmethod(env)\n File
\"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
line 82, in stop\nimport params\n File
\"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py\",
line 139, in \nif not len(kafka_broker_hosts) == 0:\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
self.name + \"' was not found in configurations
dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
parameter 'kafka_broker_hosts' was not found in configurations dictionary!",
"stdout" : "\n\nCommand failed after 1 tries\n",
"structured_out" : { }
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16692) Ambari Upgrade should clean older RCA Database tables
[ https://issues.apache.org/jira/browse/AMBARI-16692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajit Kumar updated AMBARI-16692: Attachment: rb43126.patch > Ambari Upgrade should clean older RCA Database tables > - > > Key: AMBARI-16692 > URL: https://issues.apache.org/jira/browse/AMBARI-16692 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Ajit Kumar >Assignee: Ajit Kumar > Fix For: 2.4.0 > > Attachments: rb43126.patch > > > RCA Database tables is not used anymore. This older, un-necessary data causes > many Ambari DB queries to return more slowly than necessary. If the database > gets large enough, it can have significant impact on the way ambari-server > functions. > The Ambari Server upgrade process should detect the presence of these older, > deprecated tables, and automate the process of cleaning up this data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16692) Ambari Upgrade should clean older RCA Database tables
[ https://issues.apache.org/jira/browse/AMBARI-16692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajit Kumar updated AMBARI-16692: Status: Patch Available (was: Open) > Ambari Upgrade should clean older RCA Database tables > - > > Key: AMBARI-16692 > URL: https://issues.apache.org/jira/browse/AMBARI-16692 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Ajit Kumar >Assignee: Ajit Kumar > Fix For: 2.4.0 > > Attachments: rb43126.patch > > > RCA Database tables is not used anymore. This older, un-necessary data causes > many Ambari DB queries to return more slowly than necessary. If the database > gets large enough, it can have significant impact on the way ambari-server > functions. > The Ambari Server upgrade process should detect the presence of these older, > deprecated tables, and automate the process of cleaning up this data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16692) Ambari Upgrade should clean older RCA Database tables
Ajit Kumar created AMBARI-16692: --- Summary: Ambari Upgrade should clean older RCA Database tables Key: AMBARI-16692 URL: https://issues.apache.org/jira/browse/AMBARI-16692 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Ajit Kumar Assignee: Ajit Kumar Fix For: 2.4.0 RCA Database tables is not used anymore. This older, un-necessary data causes many Ambari DB queries to return more slowly than necessary. If the database gets large enough, it can have significant impact on the way ambari-server functions. The Ambari Server upgrade process should detect the presence of these older, deprecated tables, and automate the process of cleaning up this data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16691) Atlas Integration : Extend Ambari with settings for Atlas environment configuration
Tom Beerbower created AMBARI-16691:
--
Summary: Atlas Integration : Extend Ambari with settings for Atlas
environment configuration
Key: AMBARI-16691
URL: https://issues.apache.org/jira/browse/AMBARI-16691
Project: Ambari
Issue Type: Bug
Reporter: Tom Beerbower
Assignee: Tom Beerbower
In ATLAS-616, we uncovered problems with Atlas web service when testing queries
at scale. The investigation revealed a fix possible with tuning some GC
parameters. ATLAS-616 suggests the GC values in documentation.
Default these settings in Ambari.
The values we have recommended are all to be set in {{atlas-env.sh}} config
file. They are:
Common for all JDKs:
{code}
#export ATLAS_SERVER_OPTS="-server -XX:SoftRefLRUPolicyMSPerMB=0
-XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled -XX:+PrintTenuringDistribution
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=dumps/atlas_server.hprof
-Xloggc:logs/gc-worker.log -verbose:gc -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1m -XX:+PrintGCDetails
-XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps"
{code}
For JDK7:
{code}
#export ATLAS_SERVER_HEAP="-Xms15360m -Xmx15360m -XX:MaxNewSize=3072m
-XX:PermSize=100M -XX:MaxPermSize=512m"
{code}
For JDK8:
{code}
#export ATLAS_SERVER_HEAP="-Xms15360m -Xmx15360m -XX:MaxNewSize=5120m
-XX:MetaspaceSize=100M -XX:MaxMetaspaceSize=512m"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16690) Atlas Integration : Change default expanded web app directory
[ https://issues.apache.org/jira/browse/AMBARI-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-16690: --- Status: Patch Available (was: In Progress) > Atlas Integration : Change default expanded web app directory > - > > Key: AMBARI-16690 > URL: https://issues.apache.org/jira/browse/AMBARI-16690 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > The Atlas web app is currently expanded to /var/lib/atlas. It should be in > /usr/hdp/.../atlas-server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16689) Atlas Integration : Set atlas.kafka.auto.commit.enable to false
[ https://issues.apache.org/jira/browse/AMBARI-16689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-16689: --- Status: Patch Available (was: In Progress) > Atlas Integration : Set atlas.kafka.auto.commit.enable to false > --- > > Key: AMBARI-16689 > URL: https://issues.apache.org/jira/browse/AMBARI-16689 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > As part of ATLAS-629, atlas-application.properties includes the following > property atlas.kafka.auto.commit.enable=false. Needs to be set as part of > Ambari installation as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16687) Configuration Tasks Are Being Skipped During Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-16687: - Attachment: AMBARI-16687.patch > Configuration Tasks Are Being Skipped During Upgrade > > > Key: AMBARI-16687 > URL: https://issues.apache.org/jira/browse/AMBARI-16687 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Attachments: AMBARI-16687.patch > > > During an upgrade from HDP 2.x to 2.y, all of the configuration tasks are > being shown as skipped. This is due to AMBARI-15222 where the configuration > packs were being calculated incorrectly resulting in empty maps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16687) Configuration Tasks Are Being Skipped During Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-16687: - Status: Patch Available (was: Open) > Configuration Tasks Are Being Skipped During Upgrade > > > Key: AMBARI-16687 > URL: https://issues.apache.org/jira/browse/AMBARI-16687 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Attachments: AMBARI-16687.patch > > > During an upgrade from HDP 2.x to 2.y, all of the configuration tasks are > being shown as skipped. This is due to AMBARI-15222 where the configuration > packs were being calculated incorrectly resulting in empty maps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16690) Atlas Integration : Change default expanded web app directory
Tom Beerbower created AMBARI-16690: -- Summary: Atlas Integration : Change default expanded web app directory Key: AMBARI-16690 URL: https://issues.apache.org/jira/browse/AMBARI-16690 Project: Ambari Issue Type: Bug Reporter: Tom Beerbower Assignee: Tom Beerbower The Atlas web app is currently expanded to /var/lib/atlas. It should be in /usr/hdp/.../atlas-server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16689) Atlas Integration : Set atlas.kafka.auto.commit.enable to false
Tom Beerbower created AMBARI-16689: -- Summary: Atlas Integration : Set atlas.kafka.auto.commit.enable to false Key: AMBARI-16689 URL: https://issues.apache.org/jira/browse/AMBARI-16689 Project: Ambari Issue Type: Bug Reporter: Tom Beerbower Assignee: Tom Beerbower As part of ATLAS-629, atlas-application.properties includes the following property atlas.kafka.auto.commit.enable=false. Needs to be set as part of Ambari installation as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285183#comment-15285183 ] Robert Levas commented on AMBARI-16171: --- [~elserj], before committing we technically need to submit a code review at reviews.apache.org. We then need to +1's commit. If I submit the review, I really can't give you my +1... So see if you can create an account (or maybe you have one and create the review). > Changes to Phoenix QueryServer Kerberos configuration > - > > Key: AMBARI-16171 > URL: https://issues.apache.org/jira/browse/AMBARI-16171 > Project: Ambari > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Josh Elser > Attachments: AMBARI-16171.001.patch, AMBARI-16171.002.patch, > AMBARI-16171.003.patch > > > The up-coming version of Phoenix will contain some new functionality to > support Kerberos authentication of clients via SPNEGO with the Phoenix Query > Server (PQS). > Presently, Ambari will configure PQS to use the hbase service keytab which > will result in the SPNEGO authentication failing as the RFC requires that the > "primary" component of the Kerberos principal for the server is "HTTP". Thus, > we need to ensure that we switch PQS over to use the spnego.service.keytab as > the keytab and "HTTP/_HOST@REALM" as the principal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16662) use schematool from hive2
[ https://issues.apache.org/jira/browse/AMBARI-16662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285155#comment-15285155 ] Hudson commented on AMBARI-16662: - FAILURE: Integrated in Ambari-trunk-Commit #4851 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4851/]) AMBARI-16662. use schematool from hive2.(vbrodetskyi) (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=48767597873a5465e4fc095b22c11d7e9a597a49]) * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * 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.5/services/HIVE/configuration/hive-site.xml > use schematool from hive2 > - > > Key: AMBARI-16662 > URL: https://issues.apache.org/jira/browse/AMBARI-16662 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16662.patch > > > hive2 has some changes to the metastore schema, but it is compatible with > hive1. > We should run the schematool from hive2 instead of hive1 so that the schema > is compatible for both versions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16677) Sticky bit keeps getting changed back to 777 after restart causing security checks to fail
[ https://issues.apache.org/jira/browse/AMBARI-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285154#comment-15285154 ] Hudson commented on AMBARI-16677: - FAILURE: Integrated in Ambari-trunk-Commit #4851 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4851/]) AMBARI-16677. Sticky bit keeps getting changed back to 777 after restart (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b9b634ac4737b01ef90d3f0d79dae47cb3e03b8f]) * ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py * ambari-agent/conf/unix/install-helper.sh * ambari-server/src/main/python/bootstrap.py * ambari-server/src/test/python/TestBootstrap.py > Sticky bit keeps getting changed back to 777 after restart causing security > checks to fail > -- > > Key: AMBARI-16677 > URL: https://issues.apache.org/jira/browse/AMBARI-16677 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16677.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16666) AMS Service check fails because collector takes too long to start up.
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285151#comment-15285151 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Ambari-trunk-Commit #4851 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4851/]) AMBARI-1 : AMS Service check fails because collector takes too long (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=08d61373fa40077d76e09fa61de9b1c58de830e1]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py > AMS Service check fails because collector takes too long to start up. > - > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-1.patch > > > Change embedded mode zk quorum to hostname from localhost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16440) Flush metrics to collector if metric system is stopped gracefully in the Sink daemon
[ https://issues.apache.org/jira/browse/AMBARI-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285152#comment-15285152 ] Hudson commented on AMBARI-16440: - FAILURE: Integrated in Ambari-trunk-Commit #4851 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4851/]) AMBARI-16440 : Flush metrics to collector if metric system is stopped (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b33bebb5d81d95bbb53734d14c617d53de3f9555]) * ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java > Flush metrics to collector if metric system is stopped gracefully in the Sink > daemon > > > Key: AMBARI-16440 > URL: https://issues.apache.org/jira/browse/AMBARI-16440 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16440.patch > > > HBase Regionserver daemons shuts down and restarts the Metric System for > every 5 minutes to make sure there is no growth of metrics. This causes AMS > Hadoop sink to lose metrics intermittently, which was buffered during that > time. This leads to holes in data and negative rates in graphs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16683) Replace '*' with hdp version in lzo packages
[
https://issues.apache.org/jira/browse/AMBARI-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285153#comment-15285153
]
Hudson commented on AMBARI-16683:
-
FAILURE: Integrated in Ambari-trunk-Commit #4851 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4851/])
AMBARI-16683. Replace '*' to hdp version in lzo packages (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b9ec3e68c1ce80625fbc91be1c7ad5501ea0eac1])
*
ambari-common/src/main/python/resource_management/libraries/functions/get_lzo_packages.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/install_params.py
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
Revert "AMBARI-16683. Replace '*' to hdp version in lzo packages (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=acccd3acb2c2dcbd0347538be29d64366fb220c4])
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
*
ambari-common/src/main/python/resource_management/libraries/functions/get_lzo_packages.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/install_params.py
> Replace '*' with hdp version in lzo packages
>
>
> Key: AMBARI-16683
> URL: https://issues.apache.org/jira/browse/AMBARI-16683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.4.0
>
> Attachments: AMBARI-16683.patch
>
>
> As i understood(according to discussion with Andrew O) we had some jira for
> '*' to hdp version replacement in all packages. But here it was not replaced:
> {code}
> def get_lzo_packages(stack_version_unformatted):
> lzo_packages = []
>
> if OSCheck.is_redhat_family() or OSCheck.is_suse_family():
> lzo_packages += ["lzo", "hadoop-lzo-native"]
> elif OSCheck.is_ubuntu_family():
> lzo_packages += ["liblzo2-2"]
> if stack_version_unformatted and
> check_stack_feature(StackFeature.ROLLING_UPGRADE, stack_version_unformatted):
> lzo_packages += ["hadooplzo_*"]
> else:
> lzo_packages += ["hadoop-lzo"]
> return lzo_packages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16688) Ambari users page is not showing type for users
[ https://issues.apache.org/jira/browse/AMBARI-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-16688: -- Status: Patch Available (was: Open) > Ambari users page is not showing type for users > --- > > Key: AMBARI-16688 > URL: https://issues.apache.org/jira/browse/AMBARI-16688 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-16688.patch > > > Login to ambari > Navigate to Users page > Add few users > Verify type is displayed for each User > Actual: Type is displayed as blank for users currently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16688) Ambari users page is not showing type for users
[ https://issues.apache.org/jira/browse/AMBARI-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-16688: -- Attachment: AMBARI-16688.patch > Ambari users page is not showing type for users > --- > > Key: AMBARI-16688 > URL: https://issues.apache.org/jira/browse/AMBARI-16688 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-16688.patch > > > Login to ambari > Navigate to Users page > Add few users > Verify type is displayed for each User > Actual: Type is displayed as blank for users currently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16688) Ambari users page is not showing type for users
Richard Zang created AMBARI-16688: - Summary: Ambari users page is not showing type for users Key: AMBARI-16688 URL: https://issues.apache.org/jira/browse/AMBARI-16688 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.4.0 Login to ambari Navigate to Users page Add few users Verify type is displayed for each User Actual: Type is displayed as blank for users currently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-16684: - Resolution: Resolved Status: Resolved (was: Patch Available) committed to trunk and branch-2.4.0 > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16686) Support grafana dashboards to be defined based on stack
[ https://issues.apache.org/jira/browse/AMBARI-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-16686: - Attachment: AMBARI-16686.patch > Support grafana dashboards to be defined based on stack > --- > > Key: AMBARI-16686 > URL: https://issues.apache.org/jira/browse/AMBARI-16686 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.4.0 > > Attachments: AMBARI-16686.patch > > > Grafana dashboard definition should be based on the stack that is deployed by > Ambari. > Currently we create same dashboard definitions for all stacks which might not > have the supported services defined. > The dashboards need to be classified per stack basis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16686) Support grafana dashboards to be defined based on stack
[ https://issues.apache.org/jira/browse/AMBARI-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-16686: - Status: Patch Available (was: Open) > Support grafana dashboards to be defined based on stack > --- > > Key: AMBARI-16686 > URL: https://issues.apache.org/jira/browse/AMBARI-16686 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.4.0 > > Attachments: AMBARI-16686.patch > > > Grafana dashboard definition should be based on the stack that is deployed by > Ambari. > Currently we create same dashboard definitions for all stacks which might not > have the supported services defined. > The dashboards need to be classified per stack basis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16687) Configuration Tasks Are Being Skipped During Upgrade
Jonathan Hurley created AMBARI-16687: Summary: Configuration Tasks Are Being Skipped During Upgrade Key: AMBARI-16687 URL: https://issues.apache.org/jira/browse/AMBARI-16687 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Blocker During an upgrade from HDP 2.x to 2.y, all of the configuration tasks are being shown as skipped. This is due to AMBARI-15222 where the configuration packs were being calculated incorrectly resulting in empty maps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16410) Ambari Should Suspend Alerts Notifications During Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-16410. -- Resolution: Fixed > Ambari Should Suspend Alerts Notifications During Upgrade > - > > Key: AMBARI-16410 > URL: https://issues.apache.org/jira/browse/AMBARI-16410 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.4.0 > > > Ambari reports alerts and triggers notifications during a stack upgrade. In > most cases, alert notifications should be suppressed during the upgrade to > prevent false positives. > However, some alerts, such as those which don't related to the cluster, > should remain fully operational: > - Host disk space > - Upgrade not finalized > - Ambari Server Performance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16686) Support grafana dashboards to be defined based on stack
Siddharth Wagle created AMBARI-16686: Summary: Support grafana dashboards to be defined based on stack Key: AMBARI-16686 URL: https://issues.apache.org/jira/browse/AMBARI-16686 Project: Ambari Issue Type: Improvement Components: ambari-metrics Affects Versions: 2.2.2 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 2.4.0 Grafana dashboard definition should be based on the stack that is deployed by Ambari. Currently we create same dashboard definitions for all stacks which might not have the supported services defined. The dashboards need to be classified per stack basis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284922#comment-15284922 ] Hudson commented on AMBARI-16682: - FAILURE: Integrated in Ambari-trunk-Commit #4850 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4850/]) AMBARI-16682 After deleting Kerberos (while enabled), Kerberos tab still (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd475a9a0ee33007a2759ef6bb68e17f8a69d671]) * ambari-web/test/controllers/main/service/item_test.js * ambari-web/app/messages.js * ambari-web/app/controllers/main/service/item.js > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16685) Kerberos page: Cancel clear config values
[
https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284842#comment-15284842
]
Hadoop QA commented on AMBARI-16685:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804201/AMBARI-16685.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6860//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6860//console
This message is automatically generated.
> Kerberos page: Cancel clear config values
> -
>
> Key: AMBARI-16685
> URL: https://issues.apache.org/jira/browse/AMBARI-16685
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-16685.patch, kerberos_page.png
>
>
> *Steps to reproduce:*
> # Enable Kerberos service
> # Go to Admin -> Kerberos page
> # Click "Edit"
> # Hit Cancel button
> *Actual result:*
> All configs have empty values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16666) AMS Service check fails because collector takes too long to start up.
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-1: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.4 and trunk. > AMS Service check fails because collector takes too long to start up. > - > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-1.patch > > > Change embedded mode zk quorum to hostname from localhost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16440) Flush metrics to collector if metric system is stopped gracefully in the Sink daemon
[ https://issues.apache.org/jira/browse/AMBARI-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16440: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.4 and trunk. > Flush metrics to collector if metric system is stopped gracefully in the Sink > daemon > > > Key: AMBARI-16440 > URL: https://issues.apache.org/jira/browse/AMBARI-16440 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16440.patch > > > HBase Regionserver daemons shuts down and restarts the Metric System for > every 5 minutes to make sure there is no growth of metrics. This causes AMS > Hadoop sink to lose metrics intermittently, which was buffered during that > time. This leads to holes in data and negative rates in graphs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[
https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284823#comment-15284823
]
Hadoop QA commented on AMBARI-16684:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804198/AMBARI-16684.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6859//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6859//console
This message is automatically generated.
> Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when
> installed HDP-2.2
> -
>
> Key: AMBARI-16684
> URL: https://issues.apache.org/jira/browse/AMBARI-16684
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16684.patch
>
>
> Hide Ranger Tagsync row from summary page if component is not included in
> installed stack
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Status: Patch Available (was: Open) > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284814#comment-15284814 ] Aleksandr Kovalenko commented on AMBARI-16685: -- +1 for the patch > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284809#comment-15284809 ] Andrii Tkach commented on AMBARI-16684: --- +1 for the patch > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284812#comment-15284812 ] Andrii Tkach commented on AMBARI-16685: --- 27815 tests complete (25 seconds) 154 tests pending > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-16175. Resolution: Fixed > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284811#comment-15284811 ] Juanjo Marron commented on AMBARI-16175: Committed to trunk by Jayush: https://github.com/apache/ambari/commit/84bd9ca44b57a7a0157fb7fe394e3e42f1809bd6 > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Attachment: AMBARI-16685.patch > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Attachment: kerberos_page.png > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16685) Kerberos page: Cancel clear config values
Andrii Tkach created AMBARI-16685: - Summary: Kerberos page: Cancel clear config values Key: AMBARI-16685 URL: https://issues.apache.org/jira/browse/AMBARI-16685 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 Attachments: kerberos_page.png *Steps to reproduce:* # Enable Kerberos service # Go to Admin -> Kerberos page # Click "Edit" # Hit Cancel button *Actual result:* All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Fix Version/s: (was: trunk) 3.0.0 Affects Version/s: 2.4.0 Status: In Progress (was: Patch Available) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16669.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Status: Patch Available (was: In Progress) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16669.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-16684: - Status: Patch Available (was: Open) > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16408) clean up import * for HBase service scripts
[ https://issues.apache.org/jira/browse/AMBARI-16408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16408: --- Status: Patch Available (was: In Progress) > clean up import * for HBase service scripts > --- > > Key: AMBARI-16408 > URL: https://issues.apache.org/jira/browse/AMBARI-16408 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16408.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16645) clean up import * for Kerberos service
[ https://issues.apache.org/jira/browse/AMBARI-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16645: --- Status: Patch Available (was: In Progress) > clean up import * for Kerberos service > -- > > Key: AMBARI-16645 > URL: https://issues.apache.org/jira/browse/AMBARI-16645 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0, 2.2.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16645.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16408) clean up import * for HBase service scripts
[ https://issues.apache.org/jira/browse/AMBARI-16408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16408: --- Fix Version/s: (was: trunk) 3.0.0 Affects Version/s: 2.4.0 Status: In Progress (was: Patch Available) > clean up import * for HBase service scripts > --- > > Key: AMBARI-16408 > URL: https://issues.apache.org/jira/browse/AMBARI-16408 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16408.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16645) clean up import * for Kerberos service
[ https://issues.apache.org/jira/browse/AMBARI-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16645: --- Fix Version/s: (was: trunk) 3.0.0 Affects Version/s: 2.4.0 Status: In Progress (was: Patch Available) > clean up import * for Kerberos service > -- > > Key: AMBARI-16645 > URL: https://issues.apache.org/jira/browse/AMBARI-16645 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0, 2.2.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16645.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-16684: - Attachment: AMBARI-16684.patch > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16189) clean up import * for Hive service
[ https://issues.apache.org/jira/browse/AMBARI-16189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16189: --- Status: Patch Available (was: In Progress) > clean up import * for Hive service > -- > > Key: AMBARI-16189 > URL: https://issues.apache.org/jira/browse/AMBARI-16189 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16189.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16362) clean up import * for HDFS service
[ https://issues.apache.org/jira/browse/AMBARI-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16362: --- Status: Patch Available (was: In Progress) > clean up import * for HDFS service > -- > > Key: AMBARI-16362 > URL: https://issues.apache.org/jira/browse/AMBARI-16362 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.3.0, 2.2.0, 2.4.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16362.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16362) clean up import * for HDFS service
[ https://issues.apache.org/jira/browse/AMBARI-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16362: --- Fix Version/s: (was: trunk) 3.0.0 Affects Version/s: 2.4.0 2.3.0 Status: In Progress (was: Patch Available) > clean up import * for HDFS service > -- > > Key: AMBARI-16362 > URL: https://issues.apache.org/jira/browse/AMBARI-16362 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.3.0, 2.2.0, 2.4.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16362.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16189) clean up import * for Hive service
[ https://issues.apache.org/jira/browse/AMBARI-16189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16189: --- Fix Version/s: (was: trunk) 3.0.0 Affects Version/s: (was: 2.1.1) 2.4.0 2.2.0 Status: In Progress (was: Patch Available) > clean up import * for Hive service > -- > > Key: AMBARI-16189 > URL: https://issues.apache.org/jira/browse/AMBARI-16189 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16189.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Fix Version/s: (was: 2.4.0) 3.0.0 Affects Version/s: (was: 2.1.1) 2.4.0 2.2.0 Status: In Progress (was: Patch Available) > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
Aleksandr Kovalenko created AMBARI-16684: Summary: Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2 Key: AMBARI-16684 URL: https://issues.apache.org/jira/browse/AMBARI-16684 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Fix For: 2.4.0 Hide Ranger Tagsync row from summary page if component is not included in installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko reassigned AMBARI-16684: Assignee: Aleksandr Kovalenko > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16683) Replace '*' with hdp version in lzo packages
[
https://issues.apache.org/jira/browse/AMBARI-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-16683:
---
Summary: Replace '*' with hdp version in lzo packages (was: Replace '*' to
hdp version in lzo packages)
> Replace '*' with hdp version in lzo packages
>
>
> Key: AMBARI-16683
> URL: https://issues.apache.org/jira/browse/AMBARI-16683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.4.0
>
> Attachments: AMBARI-16683.patch
>
>
> As i understood(according to discussion with Andrew O) we had some jira for
> '*' to hdp version replacement in all packages. But here it was not replaced:
> {code}
> def get_lzo_packages(stack_version_unformatted):
> lzo_packages = []
>
> if OSCheck.is_redhat_family() or OSCheck.is_suse_family():
> lzo_packages += ["lzo", "hadoop-lzo-native"]
> elif OSCheck.is_ubuntu_family():
> lzo_packages += ["liblzo2-2"]
> if stack_version_unformatted and
> check_stack_feature(StackFeature.ROLLING_UPGRADE, stack_version_unformatted):
> lzo_packages += ["hadooplzo_*"]
> else:
> lzo_packages += ["hadoop-lzo"]
> return lzo_packages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16683) Replace '*' to hdp version in lzo packages
[
https://issues.apache.org/jira/browse/AMBARI-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-16683:
---
Status: Patch Available (was: Open)
> Replace '*' to hdp version in lzo packages
> --
>
> Key: AMBARI-16683
> URL: https://issues.apache.org/jira/browse/AMBARI-16683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.4.0
>
> Attachments: AMBARI-16683.patch
>
>
> As i understood(according to discussion with Andrew O) we had some jira for
> '*' to hdp version replacement in all packages. But here it was not replaced:
> {code}
> def get_lzo_packages(stack_version_unformatted):
> lzo_packages = []
>
> if OSCheck.is_redhat_family() or OSCheck.is_suse_family():
> lzo_packages += ["lzo", "hadoop-lzo-native"]
> elif OSCheck.is_ubuntu_family():
> lzo_packages += ["liblzo2-2"]
> if stack_version_unformatted and
> check_stack_feature(StackFeature.ROLLING_UPGRADE, stack_version_unformatted):
> lzo_packages += ["hadooplzo_*"]
> else:
> lzo_packages += ["hadoop-lzo"]
> return lzo_packages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16683) Replace '*' to hdp version in lzo packages
[
https://issues.apache.org/jira/browse/AMBARI-16683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-16683:
---
Attachment: AMBARI-16683.patch
> Replace '*' to hdp version in lzo packages
> --
>
> Key: AMBARI-16683
> URL: https://issues.apache.org/jira/browse/AMBARI-16683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.4.0
>
> Attachments: AMBARI-16683.patch
>
>
> As i understood(according to discussion with Andrew O) we had some jira for
> '*' to hdp version replacement in all packages. But here it was not replaced:
> {code}
> def get_lzo_packages(stack_version_unformatted):
> lzo_packages = []
>
> if OSCheck.is_redhat_family() or OSCheck.is_suse_family():
> lzo_packages += ["lzo", "hadoop-lzo-native"]
> elif OSCheck.is_ubuntu_family():
> lzo_packages += ["liblzo2-2"]
> if stack_version_unformatted and
> check_stack_feature(StackFeature.ROLLING_UPGRADE, stack_version_unformatted):
> lzo_packages += ["hadooplzo_*"]
> else:
> lzo_packages += ["hadoop-lzo"]
> return lzo_packages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16683) Replace '*' to hdp version in lzo packages
Vitaly Brodetskyi created AMBARI-16683:
--
Summary: Replace '*' to hdp version in lzo packages
Key: AMBARI-16683
URL: https://issues.apache.org/jira/browse/AMBARI-16683
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Fix For: 2.4.0
As i understood(according to discussion with Andrew O) we had some jira for '*'
to hdp version replacement in all packages. But here it was not replaced:
{code}
def get_lzo_packages(stack_version_unformatted):
lzo_packages = []
if OSCheck.is_redhat_family() or OSCheck.is_suse_family():
lzo_packages += ["lzo", "hadoop-lzo-native"]
elif OSCheck.is_ubuntu_family():
lzo_packages += ["liblzo2-2"]
if stack_version_unformatted and
check_stack_feature(StackFeature.ROLLING_UPGRADE, stack_version_unformatted):
lzo_packages += ["hadooplzo_*"]
else:
lzo_packages += ["hadoop-lzo"]
return lzo_packages
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16662) use schematool from hive2
[ https://issues.apache.org/jira/browse/AMBARI-16662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-16662: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > use schematool from hive2 > - > > Key: AMBARI-16662 > URL: https://issues.apache.org/jira/browse/AMBARI-16662 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16662.patch > > > hive2 has some changes to the metastore schema, but it is compatible with > hive1. > We should run the schematool from hive2 instead of hive1 so that the schema > is compatible for both versions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16425) Hive view : Upload Table throws exception when 'stored as' is set to 'INPUTFORMAT'
[ https://issues.apache.org/jira/browse/AMBARI-16425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284747#comment-15284747 ] Hudson commented on AMBARI-16425: - FAILURE: Integrated in Ambari-trunk-Commit #4849 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4849/]) AMBARI-16425. Upload Table throws exception when 'stored as' is set to (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f4569bb4a0473418ccebd40af80d49e531ac44ef]) * contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/upload-table.js > Hive view : Upload Table throws exception when 'stored as' is set to > 'INPUTFORMAT' > -- > > Key: AMBARI-16425 > URL: https://issues.apache.org/jira/browse/AMBARI-16425 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.4.0 > > Attachments: AMBARI-16425_trunk.patch > > > This is not supported as of yet but was appearing in UI options list. So this > should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16266) Upload Table- Error on uploading csv with 1 row
[ https://issues.apache.org/jira/browse/AMBARI-16266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284748#comment-15284748 ] Hudson commented on AMBARI-16266: - FAILURE: Integrated in Ambari-trunk-Commit #4849 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4849/]) AMBARI-16266. [Hive View]Upload Table- Error on uploading csv with 1 row (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c431ef36a22e1daf14671885122c02092142d04e]) * contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/upload-table.js * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/ParseOptions.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/UploadService.java * contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/DataParserJSONTest.java * contrib/views/hive/src/main/resources/ui/hive-web/app/templates/upload-table.hbs * contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/DataParserXMLTest.java * contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/DataParserCSVTest.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/TableInput.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/Parser.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/UploadFromHdfsInput.java > Upload Table- Error on uploading csv with 1 row > --- > > Key: AMBARI-16266 > URL: https://issues.apache.org/jira/browse/AMBARI-16266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.4.0 > > Attachments: AMBARI-16266_trunk.patch, AMBARI-16266_trunk_2.patch, > AMBARI-16266_trunk_3.patch > > > Exception on uploading csv with 1 row > First row is considered as header by default. > = > 28 Apr 2016 06:44:35,001 INFO qtp-ambari-client-20554 BaseService:360 - > isFirstRowHeader : true, inputFileType : CSV > 28 Apr 2016 06:44:35,003 ERROR qtp-ambari-client-20554 BaseService:112 - > Exception occurred while generating preview for local file > java.util.NoSuchElementException: No rows in the file. > at > org.apache.ambari.view.hive.resources.uploads.parsers.Parser.parsePreview(Parser.java:108) > at > org.apache.ambari.view.hive.resources.uploads.parsers.DataParser.parsePreview(DataParser.java:55) > at > org.apache.ambari.view.hive.resources.uploads.UploadService.generatePreview(UploadService.java:364) > at > org.apache.ambari.view.hive.resources.uploads.UploadService.uploadForPreview(UploadService.java:109) > at sun.reflect.GeneratedMethodAccessor1179.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16681) UI : the minimum and maximum bound values for ''% cluster capacity'' are superimposed at minimum display value.
[ https://issues.apache.org/jira/browse/AMBARI-16681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284746#comment-15284746 ] Hudson commented on AMBARI-16681: - FAILURE: Integrated in Ambari-trunk-Commit #4849 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4849/]) AMBARI-16681 UI : the minimum and maximum bound values for ''% cluster (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5b1f2a6ccb9c2fc7c5a44eb3f48b28e8ff6ba2dc]) * ambari-web/app/controllers/wizard/step7/assign_master_controller.js * ambari-web/test/controllers/wizard/step7/assign_master_controller_test.js > UI : the minimum and maximum bound values for ''% cluster capacity'' are > superimposed at minimum display value. > --- > > Key: AMBARI-16681 > URL: https://issues.apache.org/jira/browse/AMBARI-16681 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16681.patch > > > Labels for widget '% of Cluster Capacity' after enabling 'Enable Interactive > Query' becomes shifted to the left sometimes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284737#comment-15284737 ] Andrii Tkach commented on AMBARI-16682: --- committed to trunk and branch-2.4 > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Resolution: Fixed Status: Resolved (was: Patch Available) > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[
https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284735#comment-15284735
]
Hadoop QA commented on AMBARI-16682:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804187/AMBARI-16682.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6858//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6858//console
This message is automatically generated.
> After deleting Kerberos (while enabled), Kerberos tab still shows it as
> enabled
> ---
>
> Key: AMBARI-16682
> URL: https://issues.apache.org/jira/browse/AMBARI-16682
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02
> PM.png
>
>
> This was not observed as part of the system test
> While testing the new delete feature, I observed this
> 1) enable Kerberos
> 2) Delete Kerberos from UI
> 3) The kerberos tab still shows it enabled
> How should Kerberos deletion be handled?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284729#comment-15284729 ] Aleksandr Kovalenko commented on AMBARI-16682: -- +1 for the patch > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284721#comment-15284721 ] Andrii Tkach commented on AMBARI-16682: --- 27817 tests complete (26 seconds) 154 tests pending > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Status: Patch Available (was: Open) > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Attachment: AMBARI-16682.patch > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Attachment: Screen Shot 2016-05-10 at 2.41.02 PM.png > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-10 at 2.41.02 PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated AMBARI-16171: Status: Patch Available (was: Open) > Changes to Phoenix QueryServer Kerberos configuration > - > > Key: AMBARI-16171 > URL: https://issues.apache.org/jira/browse/AMBARI-16171 > Project: Ambari > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Josh Elser > Attachments: AMBARI-16171.001.patch, AMBARI-16171.002.patch, > AMBARI-16171.003.patch > > > The up-coming version of Phoenix will contain some new functionality to > support Kerberos authentication of clients via SPNEGO with the Phoenix Query > Server (PQS). > Presently, Ambari will configure PQS to use the hbase service keytab which > will result in the SPNEGO authentication failing as the RFC requires that the > "primary" component of the Kerberos principal for the server is "HTTP". Thus, > we need to ensure that we switch PQS over to use the spnego.service.keytab as > the keytab and "HTTP/_HOST@REALM" as the principal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
Andrii Tkach created AMBARI-16682: - Summary: After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled Key: AMBARI-16682 URL: https://issues.apache.org/jira/browse/AMBARI-16682 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 This was not observed as part of the system test While testing the new delete feature, I observed this 1) enable Kerberos 2) Delete Kerberos from UI 3) The kerberos tab still shows it enabled How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
