[jira] [Commented] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141004#comment-16141004 ] Hudson commented on AMBARI-21793: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7936 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7936/]) AMBARI-21793. Add support for variables used by Knox topology template (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=787fe0f7e56cd56d3daf5e40e56647f06b3fe890]) * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.3.0/package/scripts/params_linux.py > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140999#comment-16140999 ] Hudson commented on AMBARI-21793: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #57 (See [https://builds.apache.org/job/Ambari-branch-2.6/57/]) AMBARI-21793. Add support for variables used by Knox topology template (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a21dc6d89a8243a34bf5fdc9df089bdfcaf40443]) * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21811) Password properties should be masked in Ambari for Nifi
[ https://issues.apache.org/jira/browse/AMBARI-21811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuldeep Kulkarni updated AMBARI-21811: -- Description: Please find attached screenshot. nifi.security.keyPasswd nifi.security.keystorePasswd nifi.security.truststorePasswd Password fields should be masked. was: Please find attached screenshot. Password fields should be masked. > Password properties should be masked in Ambari for Nifi > --- > > Key: AMBARI-21811 > URL: https://issues.apache.org/jira/browse/AMBARI-21811 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Environment: Ambari-2.5.1.0 For HDF (Management pack has been > installed) >Reporter: Kuldeep Kulkarni > Attachments: Screen Shot 2017-08-24 at 5.21.15 PM.png > > > Please find attached screenshot. > nifi.security.keyPasswd > nifi.security.keystorePasswd > nifi.security.truststorePasswd > Password fields should be masked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21811) Password properties should be masked in Ambari for Nifi
[ https://issues.apache.org/jira/browse/AMBARI-21811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuldeep Kulkarni updated AMBARI-21811: -- Attachment: Screen Shot 2017-08-24 at 5.21.15 PM.png > Password properties should be masked in Ambari for Nifi > --- > > Key: AMBARI-21811 > URL: https://issues.apache.org/jira/browse/AMBARI-21811 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Environment: Ambari-2.5.1.0 For HDF (Management pack has been > installed) >Reporter: Kuldeep Kulkarni > Attachments: Screen Shot 2017-08-24 at 5.21.15 PM.png > > > Please find attached screenshot. > Password fields should be masked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21810) Create Utility Script to support Solr Collection Data Retention/Purging/Archiving
[
https://issues.apache.org/jira/browse/AMBARI-21810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140988#comment-16140988
]
Hadoop QA commented on AMBARI-21810:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883630/AMBARI-21810.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-infra/ambari-infra-solr-client.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12061//console
This message is automatically generated.
> Create Utility Script to support Solr Collection Data
> Retention/Purging/Archiving
> -
>
> Key: AMBARI-21810
> URL: https://issues.apache.org/jira/browse/AMBARI-21810
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
>Affects Versions: 2.6.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.6.0
>
> Attachments: AMBARI-21810.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21811) Password properties should be masked in Ambari for Nifi
Kuldeep Kulkarni created AMBARI-21811: - Summary: Password properties should be masked in Ambari for Nifi Key: AMBARI-21811 URL: https://issues.apache.org/jira/browse/AMBARI-21811 Project: Ambari Issue Type: Bug Components: ambari-web Environment: Ambari-2.5.1.0 For HDF (Management pack has been installed) Reporter: Kuldeep Kulkarni Please find attached screenshot. Password fields should be masked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140952#comment-16140952 ] Sumit Mohanty commented on AMBARI-21793: LGTM, +1 > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21810) Create Utility Script to support Solr Collection Data Retention/Purging/Archiving
[ https://issues.apache.org/jira/browse/AMBARI-21810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21810: Attachment: AMBARI-21810.patch > Create Utility Script to support Solr Collection Data > Retention/Purging/Archiving > - > > Key: AMBARI-21810 > URL: https://issues.apache.org/jira/browse/AMBARI-21810 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.6.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21810.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21810) Create Utility Script to support Solr Collection Data Retention/Purging/Archiving
[ https://issues.apache.org/jira/browse/AMBARI-21810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21810: Status: Patch Available (was: In Progress) > Create Utility Script to support Solr Collection Data > Retention/Purging/Archiving > - > > Key: AMBARI-21810 > URL: https://issues.apache.org/jira/browse/AMBARI-21810 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.6.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21810.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21793: --- Fix Version/s: 2.6.0 > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21810) Create Utility Script to support Solr Collection Data Retention/Purging/Archiving
Miklos Gergely created AMBARI-21810: --- Summary: Create Utility Script to support Solr Collection Data Retention/Purging/Archiving Key: AMBARI-21810 URL: https://issues.apache.org/jira/browse/AMBARI-21810 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.6.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21511) Grafana setup fails if password is too short
[
https://issues.apache.org/jira/browse/AMBARI-21511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140938#comment-16140938
]
Hudson commented on AMBARI-21511:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7935 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7935/])
AMBARI-21511 : Grafana setup fails if password is too short. (avijayan)
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b290ce068a14b153449840f00ba809ee256c22e2])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
> Grafana setup fails if password is too short
>
>
> Key: AMBARI-21511
> URL: https://issues.apache.org/jira/browse/AMBARI-21511
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 3.0.0
>
> Attachments: AMBARI-21511.patch
>
>
> STR:
> # Create cluster
> # Add Ambari Metrics with 1-char password
> Result: Grafana Start was marked a failure due to "New password too short"
> error. Grafana was actually started, but datasource and dashboards were not
> created, since the script failed in preceding step.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 83, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_grafana_admin_pwd()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 262, in create_grafana_admin_pwd
> "PUT request status: %s %s \n%s" % (response.status, response.reason,
> data))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana password
> creation failed. PUT request status: 400 Bad Request
> {"message":"New password too short"}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account
[ https://issues.apache.org/jira/browse/AMBARI-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14163: Description: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. was: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. > zookeeper session timeout for hbase should take zookeeper tickTime into > account > --- > > Key: AMBARI-14163 > URL: https://issues.apache.org/jira/browse/AMBARI-14163 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value > of 1 min 40 seconds. > The change was accepted. > However, such timeout is not reachable (it is > 20 times tickTime). > Ambari should detect such scenario and warn user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21511) Grafana setup fails if password is too short
[
https://issues.apache.org/jira/browse/AMBARI-21511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21511:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk.
> Grafana setup fails if password is too short
>
>
> Key: AMBARI-21511
> URL: https://issues.apache.org/jira/browse/AMBARI-21511
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 3.0.0
>
> Attachments: AMBARI-21511.patch
>
>
> STR:
> # Create cluster
> # Add Ambari Metrics with 1-char password
> Result: Grafana Start was marked a failure due to "New password too short"
> error. Grafana was actually started, but datasource and dashboards were not
> created, since the script failed in preceding step.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 83, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_grafana_admin_pwd()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 262, in create_grafana_admin_pwd
> "PUT request status: %s %s \n%s" % (response.status, response.reason,
> data))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana password
> creation failed. PUT request status: 400 Bad Request
> {"message":"New password too short"}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package
[ https://issues.apache.org/jira/browse/AMBARI-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14160: Description: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. was: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. > Ambari Slider View should pick up multiple versions of the same app package > --- > > Key: AMBARI-14160 > URL: https://issues.apache.org/jira/browse/AMBARI-14160 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > I was validating some fix for Slider hbase with Gour. > A new Slider hbase app package was built and moved to under: > /var/lib/ambari-server/resources/apps > We tried naming the new app package ending with -ted.zip -999.zip > After 'ambari-server restart', the new app package was not picked up by > Ambari. > Ambari Slider View should be able to accommodate more than one version of app > package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21511) Grafana setup fails if password is too short
[
https://issues.apache.org/jira/browse/AMBARI-21511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21511:
---
Fix Version/s: (was: 2.6.0)
3.0.0
> Grafana setup fails if password is too short
>
>
> Key: AMBARI-21511
> URL: https://issues.apache.org/jira/browse/AMBARI-21511
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 3.0.0
>
> Attachments: AMBARI-21511.patch
>
>
> STR:
> # Create cluster
> # Add Ambari Metrics with 1-char password
> Result: Grafana Start was marked a failure due to "New password too short"
> error. Grafana was actually started, but datasource and dashboards were not
> created, since the script failed in preceding step.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 83, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_grafana_admin_pwd()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 262, in create_grafana_admin_pwd
> "PUT request status: %s %s \n%s" % (response.status, response.reason,
> data))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana password
> creation failed. PUT request status: 400 Bad Request
> {"message":"New password too short"}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21602) Pre-configure services when Kerberos is enabled to reduce number of core service restarts when services are added
[ https://issues.apache.org/jira/browse/AMBARI-21602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140775#comment-16140775 ] Hudson commented on AMBARI-21602: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7934 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7934/]) AMBARI-21602. Pre-configure services when Kerberos is enabled to reduce (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4bce57823da7d972df9e422e3f920ebbc60362f3]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionDirectory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRendererTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/UsedIdentities.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionManager.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorUpdateHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/RemovableIdentities.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.8/kerberos_preconfigure.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareEnableKerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareDisableKerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackVersionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRequest.java * (add) ambari-server/src/main/resources/stacks/HDP/2.6/kerberos_preconfigure.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/DeleteIdentityHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceDirectory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ConfigurationDirectory.java * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PreconfigureServiceType.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * (edit)
[jira] [Resolved] (AMBARI-21808) Create registry failing with unique constraint violation after a failed registry request
[ https://issues.apache.org/jira/browse/AMBARI-21808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-21808. Resolution: Fixed > Create registry failing with unique constraint violation after a failed > registry request > > > Key: AMBARI-21808 > URL: https://issues.apache.org/jira/browse/AMBARI-21808 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 3.0.0 > > > Aug 2017 20:59:12,903 ERROR [ambari-client-thread-131] ContainerResponse:419 > - The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse > Persistence Services - 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key > value violates unique constraint "uq_registry_name" > Error Code: 0 > Call: INSERT INTO registries (id, registry_name, registry_type, registry_uri) > VALUES (?, ?, ?, ?) > bind => [4 parameters bound] > Issue - Database entry is made before validating the url for its existence. > Fix - Add url validation check before calling addRegistries functionality -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21809) Pre-configure services during stack upgrade if Kerberos is enabled to reduce number of core service restarts when services are added
Robert Levas created AMBARI-21809: - Summary: Pre-configure services during stack upgrade if Kerberos is enabled to reduce number of core service restarts when services are added Key: AMBARI-21809 URL: https://issues.apache.org/jira/browse/AMBARI-21809 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.6.0 Pre-configure (certain) services during a stack upgrade to HDP 2.6, when Kerberos is enabled, to reduce number of core service restarts when services are added. Services to pre-configure include: * Knox * Beacon While upgrading the stack (EU or RU), processing the relevant Kerberos descriptor to find services marked to be _pre-configured_. When a tagged service is encountered, process it if it is not installed. Apply only configuration changes for existing configuration types. This will set at least the core-site changes related to proxyuser and auth-to-local rules properties. By doing this, if a tagged service is later installed, the settings will already be in place in the existing service configs and thus the existing services will not need to be restarted. Caveats: * Default values for the uninstalled, tagged, services will be assumed * The stack advisor will be used to suggest locations of components - used to build the clusterHostInfo structure that may be used to derive property values. Note: This processing is to occur when upgrading the stack from HDP 2.5 to HDP 2.6. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21602) Pre-configure services when Kerberos is enabled to reduce number of core service restarts when services are added
[
https://issues.apache.org/jira/browse/AMBARI-21602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21602:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 4bce57823da7d972df9e422e3f920ebbc60362f3
Author: Robert Levas
Date: Thu Aug 24 17:01:12 2017 -0400
{noformat}
Committed to branch-2.6
{noformat}
commit e6641558cfff0b06a8ad0c0a41610433f96f1335
Author: Robert Levas
Date: Thu Aug 24 16:06:56 2017 -0400
{noformat}
> Pre-configure services when Kerberos is enabled to reduce number of core
> service restarts when services are added
> -
>
> Key: AMBARI-21602
> URL: https://issues.apache.org/jira/browse/AMBARI-21602
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.6.0
>
> Attachments: AMBARI-21602_branch-2.6_01.patch,
> AMBARI-21602_branch-2.6_02.patch, AMBARI-21602_trunk_01.patch,
> AMBARI-21602_trunk_02.patch
>
>
> Pre-configure (certain) services when Kerberos is enabled to reduce number of
> core service restarts when services are added.
> While processing the Kerberos descriptor, include services marked to be
> _pre-configured_. When a tagged service is encountered, process it weather
> it is installed or not. However if it is not installed, only apply
> configuration changes for existing configuration types. This will set at
> least the core-site changes related to proxyuser and auth-to-local rules
> properties. By doing this, if a tagged service is later installed, the
> settings will already be in place in the existing service configs and thus
> the existing services will not need to be restarted.
> Caveats:
> * Default values for the uninstalled, tagged, services will be assumed
> * The stack advisor will be used to suggest locations of components - used to
> build the clusterHostInfo structure that may be used to derive property
> values.
> Note: This processing is to occur when Kerberos is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140687#comment-16140687
]
Hudson commented on AMBARI-21627:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #56 (See
[https://builds.apache.org/job/Ambari-branch-2.6/56/])
AMBARI-21627. Cross-stack upgrade from IOP to HDP, ranger audit (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e845f41a7f4ba59d48d5ba45cbf25bb530fb24f2])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.addendum.patch, AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140685#comment-16140685
]
Hudson commented on AMBARI-21807:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #56 (See
[https://builds.apache.org/job/Ambari-branch-2.6/56/])
AMBARI-21807. 'Move Hive Metastore' wizard is stuck while configuring (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e27a214285c62bc43f11e3026de912410bc47ddc])
* (edit) ambari-web/app/controllers/main/service/reassign/step1_controller.js
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21602) Pre-configure services when Kerberos is enabled to reduce number of core service restarts when services are added
[ https://issues.apache.org/jira/browse/AMBARI-21602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140686#comment-16140686 ] Hudson commented on AMBARI-21602: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #56 (See [https://builds.apache.org/job/Ambari-branch-2.6/56/]) AMBARI-21602. Pre-configure services when Kerberos is enabled to reduce (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e6641558cfff0b06a8ad0c0a41610433f96f1335]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/FixAuthToLocalMappingActionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareEnableKerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ConfigurationDirectory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionDirectory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.8/kerberos_preconfigure.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java * (add) ambari-server/src/main/resources/stacks/HDP/2.6/kerberos_preconfigure.json * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackVersionResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * (edit) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorUpdateHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceDirectory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PreconfigureServiceType.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FixAuthToLocalMappingAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareDisableKerberosServerAction.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java > Pre-configure services when Kerberos is enabled to reduce number of core > service restarts when services are added > - > >
[jira] [Commented] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140648#comment-16140648
]
Hudson commented on AMBARI-21807:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7933 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7933/])
AMBARI-21807. 'Move Hive Metastore' wizard is stuck while configuring (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f5f9a7581df7e4eb880f3da7f6248a29d332b3b7])
* (edit) ambari-web/app/controllers/main/service/reassign/step1_controller.js
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21808) Create registry failing with unique constraint violation after a failed registry request
Madhuvanthi Radhakrishnan created AMBARI-21808: -- Summary: Create registry failing with unique constraint violation after a failed registry request Key: AMBARI-21808 URL: https://issues.apache.org/jira/browse/AMBARI-21808 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 Aug 2017 20:59:12,903 ERROR [ambari-client-thread-131] ContainerResponse:419 - The RuntimeException could not be mapped to a response, re-throwing to the HTTP container javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "uq_registry_name" Error Code: 0 Call: INSERT INTO registries (id, registry_name, registry_type, registry_uri) VALUES (?, ?, ?, ?) bind => [4 parameters bound] Issue - Database entry is made before validating the url for its existence. Fix - Add url validation check before calling addRegistries functionality -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140626#comment-16140626 ] Hudson commented on AMBARI-21076: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #55 (See [https://builds.apache.org/job/Ambari-branch-2.6/55/]) AMBARI-21076. Move superset as an independent project. (Nishant Bangarwa (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=343e5928e9973502673e35c05088c5836796712b]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/role_command_order.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/status_params.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SUPERSET/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/quicklinks/quicklinks.json * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/quicklinks/quicklinks.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-superset-env.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/templates/superset.sh * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/role_command_order.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SUPERSET/kerberos.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/service_check.py * (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/themes/theme.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/themes/theme.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/superset.py > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21784) Ambari server logs consistency check warning after service delete with ConfigGroup present
[
https://issues.apache.org/jira/browse/AMBARI-21784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140627#comment-16140627
]
Hudson commented on AMBARI-21784:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #55 (See
[https://builds.apache.org/job/Ambari-branch-2.6/55/])
AMBARI-21784. Ambari server logs consistency check warning after service
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=04b4013e205590ec02d089d1d05b91496f9364d9])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupFactory.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigGroupTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ConfigGroupResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ConfigGroupResourceProvider.java
> Ambari server logs consistency check warning after service delete with
> ConfigGroup present
> --
>
> Key: AMBARI-21784
> URL: https://issues.apache.org/jira/browse/AMBARI-21784
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.6.0
>
> Attachments: AMBARI-21784.patch
>
>
> Ambari server log is constantly populated with 'Config inconsistency exists:
> unknown configType=solr-site' even after Solr deletion due to existence of
> config group.
> {code}
> 22 Aug 2017 19:00:20,094 ERROR [ambari-hearbeat-monitor] HostImpl:1085 -
> Config inconsistency exists: unknown configType=solr-site
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-21807:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch committed to trunk and branch-2.6
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140605#comment-16140605
]
Jaimin Jetly commented on AMBARI-21807:
---
Note that this issue affects Move master wizard for "Hive Server", "Hive
Metastore" and "Oozie Server" When existing MySQL server (not ambari deployed)
is being used
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140593#comment-16140593 ] Hudson commented on AMBARI-21076: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7932 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7932/]) AMBARI-21076. Move superset as an independent project. (Nishant Bangarwa (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b96c77a8f9dfd021aa4a0b2f825dc2e270f79050]) * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/templates/superset.sh * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/superset.py * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/themes/theme.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/role_command_order.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/themes/theme.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-superset-env.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/quicklinks/quicklinks.json * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/role_command_order.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SUPERSET/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SUPERSET/metainfo.xml * (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/status_params.py > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-21807:
--
Status: Patch Available (was: Open)
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly reassigned AMBARI-21807:
-
Assignee: Jaimin Jetly
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140590#comment-16140590
]
Hadoop QA commented on AMBARI-21806:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883560/AMBARI-21806.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12060//console
This message is automatically generated.
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21806.patch
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-21807:
--
Attachment: AMBARI-21807.patch
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21807.patch
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21793) Add support for variables used by Knox topology template
[
https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140582#comment-16140582
]
Hadoop QA commented on AMBARI-21793:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883578/AMBARI-21793.001.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12059//console
This message is automatically generated.
> Add support for variables used by Knox topology template
>
>
> Key: AMBARI-21793
> URL: https://issues.apache.org/jira/browse/AMBARI-21793
> Project: Ambari
> Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Attachments: AMBARI-21793.001.patch
>
>
> Currently Knox template within Ambari uses some hardcoded values such as http
> schemes, this bug is to add variables which would would make Knox template
> within Ambari more dynamic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
Vivek Sharma created AMBARI-21807:
-
Summary: 'Move Hive Metastore' wizard is stuck while configuring
MYSQL_SERVER
Key: AMBARI-21807
URL: https://issues.apache.org/jira/browse/AMBARI-21807
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.2
Reporter: Vivek Sharma
Priority: Blocker
Fix For: 2.5.2
*STR*
* Tried to move Hive Metastore host from host-4 to host-7
The UI is stuck with below JS error
{code}
Uncaught TypeError: Cannot read property 'get' of undefined
at Class.configureMySqlServer (app.js:33617)
at Class.runTask (app.js:76614)
at Class.loadTasks (app.js:76497)
at Class.initStep (app.js:76308)
at Class.loadStep (app.js:76291)
at Class.loadStep (app.js:33218)
at Class.newFunc [as loadStep] (vendor.js:2608)
at Class.didInsertElement (app.js:212098)
at Class.newFunc [as didInsertElement] (vendor.js:2608)
at Class.trigger (vendor.js:15180)
{code}
Looks like the issue is because this call returns 'undefined'
{code}
App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
undefined
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21807) 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
[
https://issues.apache.org/jira/browse/AMBARI-21807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Sharma updated AMBARI-21807:
--
Fix Version/s: (was: 2.5.2)
2.6.0
> 'Move Hive Metastore' wizard is stuck while configuring MYSQL_SERVER
>
>
> Key: AMBARI-21807
> URL: https://issues.apache.org/jira/browse/AMBARI-21807
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Priority: Blocker
> Fix For: 2.6.0
>
>
> *STR*
> * Tried to move Hive Metastore host from host-4 to host-7
> The UI is stuck with below JS error
> {code}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.configureMySqlServer (app.js:33617)
> at Class.runTask (app.js:76614)
> at Class.loadTasks (app.js:76497)
> at Class.initStep (app.js:76308)
> at Class.loadStep (app.js:76291)
> at Class.loadStep (app.js:33218)
> at Class.newFunc [as loadStep] (vendor.js:2608)
> at Class.didInsertElement (app.js:212098)
> at Class.newFunc [as didInsertElement] (vendor.js:2608)
> at Class.trigger (vendor.js:15180)
> {code}
> Looks like the issue is because this call returns 'undefined'
> {code}
> App.HostComponent.find().findProperty('componentName', 'MYSQL_SERVER')
> undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21784) Ambari server logs consistency check warning after service delete with ConfigGroup present
[
https://issues.apache.org/jira/browse/AMBARI-21784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21784:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.6
> Ambari server logs consistency check warning after service delete with
> ConfigGroup present
> --
>
> Key: AMBARI-21784
> URL: https://issues.apache.org/jira/browse/AMBARI-21784
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.6.0
>
> Attachments: AMBARI-21784.patch
>
>
> Ambari server log is constantly populated with 'Config inconsistency exists:
> unknown configType=solr-site' even after Solr deletion due to existence of
> config group.
> {code}
> 22 Aug 2017 19:00:20,094 ERROR [ambari-hearbeat-monitor] HostImpl:1085 -
> Config inconsistency exists: unknown configType=solr-site
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21076: - Component/s: ambari-server > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21076: - Fix Version/s: 2.6.0 > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21076: - Fix Version/s: trunk > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21076: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP
[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21076: - Affects Version/s: 2.5.1 trunk > Move superset as a top-level module in HDP > -- > > Key: AMBARI-21076 > URL: https://issues.apache.org/jira/browse/AMBARI-21076 > Project: Ambari > Issue Type: Task >Affects Versions: trunk, 2.5.1 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch, > AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch > > > Superset is a generic UI which can work with multiple data stores e.g HIVE, > DRUID and any other dataStore that supports SQLALCHEMY dialects. > Currently superset is installed as a master component under Druid. > This task is to move superset out of Druid so that it can be installed and > managed independent of Druid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP
[
https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140556#comment-16140556
]
Swapan Shridhar commented on AMBARI-21076:
--
trunk:
{code}
commit b96c77a8f9dfd021aa4a0b2f825dc2e270f79050
Author: Swapan Shridhar
Date: Thu Aug 24 12:13:10 2017 -0700
AMBARI-21076. Move superset as an independent project. (Nishant Bangarwa
via Swapan Shridhar).
{code}
branch-2.6:
{code}
commit 343e5928e9973502673e35c05088c5836796712b
Author: Swapan Shridhar
Date: Thu Aug 24 12:24:43 2017 -0700
AMBARI-21076. Move superset as an independent project. (Nishant Bangarwa
via Swapan Shridhar).
{code}
> Move superset as a top-level module in HDP
> --
>
> Key: AMBARI-21076
> URL: https://issues.apache.org/jira/browse/AMBARI-21076
> Project: Ambari
> Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch,
> AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch
>
>
> Superset is a generic UI which can work with multiple data stores e.g HIVE,
> DRUID and any other dataStore that supports SQLALCHEMY dialects.
> Currently superset is installed as a master component under Druid.
> This task is to move superset out of Druid so that it can be installed and
> managed independent of Druid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21793: --- Status: Patch Available (was: Open) > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21793: --- Attachment: AMBARI-21793.001.patch > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140400#comment-16140400
]
Hudson commented on AMBARI-21569:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #54 (See
[https://builds.apache.org/job/Ambari-branch-2.6/54/])
AMBARI-21569.Users randomly getting "HDFS020 Could not write file" (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4b047c37a7771ffa2bf7a1f2ab1d09d1d464e34e])
* (edit) contrib/views/hive20/src/main/resources/ui/yarn.lock
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsUtil.java
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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)
> 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.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Commented] (AMBARI-21797) Patch / Maint UI Minor Style Adjustments
[
https://issues.apache.org/jira/browse/AMBARI-21797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140401#comment-16140401
]
Hudson commented on AMBARI-21797:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #54 (See
[https://builds.apache.org/job/Ambari-branch-2.6/54/])
AMBARI-21797. Patch / Maint UI Minor Style Adjustments (alexantonenko)
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8e68463dc6ce2660c71b83846cd38ac4f16ffbdb])
* (edit)
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/styles/stack_versions.less
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
> Patch / Maint UI Minor Style Adjustments
>
>
> Key: AMBARI-21797
> URL: https://issues.apache.org/jira/browse/AMBARI-21797
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21797.patch
>
>
> The new UI for {{PATCH}} / {{MAINT}} repositories needs some adjustments to
> clean it up.
> - The "INSTALL" header on the repository is not flat when installing the repo
> for the first time. It appears as a button.
> - The text for installing the repository and showing upgrade progress is not
> padded enough and is too close to the edges.
> - The icon for revert is all squished and doesn't have a tooltip
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21801) No Hosts are Targeted For MAINT VDF If Available Services is Empty
[
https://issues.apache.org/jira/browse/AMBARI-21801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140340#comment-16140340
]
Hudson commented on AMBARI-21801:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7931 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7931/])
AMBARI-21801 - No Hosts are Targeted For MAINT VDF If Available Services
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=76f0dafbd561f3052bc0d90045fcfdcba93beb3a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
> No Hosts are Targeted For MAINT VDF If Available Services is Empty
> --
>
> Key: AMBARI-21801
> URL: https://issues.apache.org/jira/browse/AMBARI-21801
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21801.patch
>
>
> When trying to distribute a MAINT repository which doesn't have available
> services, such as the one below, no hosts are targeted and the installation
> doesn't do anything.
> The fix is to use the {{ClusterSummary}} from the VDF which includes a mashup
> of the cluster's services and those listed in the VDF's manifest and
> available services structure.
> {code}
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="version_definition.xsd">
>
> MAINT
> HDP-2.6
> 2.6.2.0
> 193
> 2.6.[0-2]+.[0-9]+
> http://example.com
> HDP-2.6.2.0-193-MAINT
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> release-version="2.6.0.3"/>
>
>
>
>
>
>
> 2_6_2_0_*
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-2.6.2.0-193
> HDP-2.6
> HDP
> true
>
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-UTILS-1.1.0.21
> HDP-UTILS-1.1.0.21
> HDP-UTILS
> false
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140334#comment-16140334
]
Hudson commented on AMBARI-21569:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1831 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1831/])
Revert "AMBARI-21569.Users randomly getting "HDFS020 Could not write (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=27e00dde15b0d4e1c3701158521268623ff1be0d])
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java
* (edit) contrib/views/hive20/src/main/resources/ui/yarn.lock
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsUtil.java
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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)
> 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.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Updated] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21806:
-
Attachment: AMBARI-21806.patch
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21806.patch
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21806:
-
Status: Patch Available (was: Open)
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
Jonathan Hurley created AMBARI-21806:
Summary: Repository Entities Which Can't Be Removed Should Be
Hide-able
Key: AMBARI-21806
URL: https://issues.apache.org/jira/browse/AMBARI-21806
Project: Ambari
Issue Type: Task
Affects Versions: 2.6.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.6.0
Many tables have begun referencing {{repo_version}} since a simple {{version}}
string is no longer sufficient to properly identify a repository. However, we
allow a {{RepsitoryVersionEntity}} to be removed if it is in the following
states:
- {{INIT}}
- {{INSTALL_FAILED}}
- {{OUT_OF_SYNC}}
The issue with removing the entities is that this would also force us to remove
things like upgrades, service component versions, etc. Here are some options:
# Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
but for other states we'd need to keep it in the DB for history and perhaps add
a {{hidden}} column. This would keep the referential integrity.
# Allow the removal of repository versions, but warn that it will also remove
things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21782) Service Accounts page shows no data for stack services after Ambari is upgraded on IOP cluster
[ https://issues.apache.org/jira/browse/AMBARI-21782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21782: - Resolution: Fixed Status: Resolved (was: Patch Available) > Service Accounts page shows no data for stack services after Ambari is > upgraded on IOP cluster > -- > > Key: AMBARI-21782 > URL: https://issues.apache.org/jira/browse/AMBARI-21782 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Vivek Sharma >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21782.patch > > > *STR* > # Install BI-4.2.0 with Ambari-2.2.0 (all services are installed) > # Upgrade Ambari to 2.5.2.0-274 > # Go to Service Accounts page > *Result:* > No entry is present for any of the stack services. The only entry is for AMS > This appears a UI issue where we are unable to get the list of services and > their user accounts if their stack is still BI > *Note*: After the cluster is Express Upgraded from BI-4.2.0 to HDP-2.6.2, the > entries in Service Accounts page show up fine -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21801) No Hosts are Targeted For MAINT VDF If Available Services is Empty
[
https://issues.apache.org/jira/browse/AMBARI-21801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21801:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> No Hosts are Targeted For MAINT VDF If Available Services is Empty
> --
>
> Key: AMBARI-21801
> URL: https://issues.apache.org/jira/browse/AMBARI-21801
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21801.patch
>
>
> When trying to distribute a MAINT repository which doesn't have available
> services, such as the one below, no hosts are targeted and the installation
> doesn't do anything.
> The fix is to use the {{ClusterSummary}} from the VDF which includes a mashup
> of the cluster's services and those listed in the VDF's manifest and
> available services structure.
> {code}
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="version_definition.xsd">
>
> MAINT
> HDP-2.6
> 2.6.2.0
> 193
> 2.6.[0-2]+.[0-9]+
> http://example.com
> HDP-2.6.2.0-193-MAINT
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> release-version="2.6.0.3"/>
>
>
>
>
>
>
> 2_6_2_0_*
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-2.6.2.0-193
> HDP-2.6
> HDP
> true
>
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-UTILS-1.1.0.21
> HDP-UTILS-1.1.0.21
> HDP-UTILS
> false
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21801) No Hosts are Targeted For MAINT VDF If Available Services is Empty
[
https://issues.apache.org/jira/browse/AMBARI-21801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21801:
-
Attachment: AMBARI-21801.patch
> No Hosts are Targeted For MAINT VDF If Available Services is Empty
> --
>
> Key: AMBARI-21801
> URL: https://issues.apache.org/jira/browse/AMBARI-21801
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21801.patch
>
>
> When trying to distribute a MAINT repository which doesn't have available
> services, such as the one below, no hosts are targeted and the installation
> doesn't do anything.
> The fix is to use the {{ClusterSummary}} from the VDF which includes a mashup
> of the cluster's services and those listed in the VDF's manifest and
> available services structure.
> {code}
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="version_definition.xsd">
>
> MAINT
> HDP-2.6
> 2.6.2.0
> 193
> 2.6.[0-2]+.[0-9]+
> http://example.com
> HDP-2.6.2.0-193-MAINT
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> release-version="2.6.0.3"/>
>
>
>
>
>
>
> 2_6_2_0_*
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-2.6.2.0-193
> HDP-2.6
> HDP
> true
>
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-UTILS-1.1.0.21
> HDP-UTILS-1.1.0.21
> HDP-UTILS
> false
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21801) No Hosts are Targeted For MAINT VDF If Available Services is Empty
[
https://issues.apache.org/jira/browse/AMBARI-21801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21801:
-
Status: Patch Available (was: Open)
> No Hosts are Targeted For MAINT VDF If Available Services is Empty
> --
>
> Key: AMBARI-21801
> URL: https://issues.apache.org/jira/browse/AMBARI-21801
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21801.patch
>
>
> When trying to distribute a MAINT repository which doesn't have available
> services, such as the one below, no hosts are targeted and the installation
> doesn't do anything.
> The fix is to use the {{ClusterSummary}} from the VDF which includes a mashup
> of the cluster's services and those listed in the VDF's manifest and
> available services structure.
> {code}
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="version_definition.xsd">
>
> MAINT
> HDP-2.6
> 2.6.2.0
> 193
> 2.6.[0-2]+.[0-9]+
> http://example.com
> HDP-2.6.2.0-193-MAINT
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> release-version="2.6.0.3"/>
>
>
>
>
>
>
> 2_6_2_0_*
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-2.6.2.0-193
> HDP-2.6
> HDP
> true
>
>
>
> http://repo.ambari.apache.org/hdp/centos6/HDP-UTILS-1.1.0.21
> HDP-UTILS-1.1.0.21
> HDP-UTILS
> false
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21569:
---
Fix Version/s: (was: 2.5.3)
2.6.0
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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)
> 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.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
>
[jira] [Created] (AMBARI-21805) Add Docker as a managed service in HDP stack
Eric Yang created AMBARI-21805:
--
Summary: Add Docker as a managed service in HDP stack
Key: AMBARI-21805
URL: https://issues.apache.org/jira/browse/AMBARI-21805
Project: Ambari
Issue Type: New Feature
Components: ambari-server
Reporter: Eric Yang
New feature in YARN 3 enables to deploy docker containers in Hadoop cluster.
Ambari can automate Docker installation to make the integrate seamless.
Docker-ce can be installed on all slave nodes, and master node can install
Docker Registry, and run Docker Registry2 in a docker container.
Installation instruction for docker:
https://docs.docker.com/engine/installation/linux/docker-ce/centos/
Docker Registry can mount HDFS as storage for docker registry data:
{code}
docker run -d -p 5000:5000 --name registry -v /mnt/hdfs/apps:/var/lib/registry
registry:2
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140132#comment-16140132
]
Hudson commented on AMBARI-21798:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1830 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1830/])
AMBARI-21798. Oozie server crashes post migration after regen kerberos (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2eed29264cb06084bd4a4348e71421d419b22716])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog252Test.java
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21804) Add configurable management endpoints to Log Search
Olivér Szabó created AMBARI-21804: - Summary: Add configurable management endpoints to Log Search Key: AMBARI-21804 URL: https://issues.apache.org/jira/browse/AMBARI-21804 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21800) Some services had issue coming up after express upgrade on IOP clusters
[ https://issues.apache.org/jira/browse/AMBARI-21800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140098#comment-16140098 ] Hudson commented on AMBARI-21800: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #52 (See [https://builds.apache.org/job/Ambari-branch-2.6/52/]) AMBARI-21800. Some services had issue coming up after express upgrade on (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d1659f1794d54d1f8172ed5a48af54ba8d860bd]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleCommandOrderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stageplanner/TestStagePlanner.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleGraphTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java > Some services had issue coming up after express upgrade on IOP clusters > --- > > Key: AMBARI-21800 > URL: https://issues.apache.org/jira/browse/AMBARI-21800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21800.patch > > > Some services had an issue coming up after express upgrade on IOP clusters. > Express upgrade was successful as per Ambari UI. > It seems like something is wrong with RCO post-upgrade where the older stack > version RCO gets recached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21798:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 60632536aa6fbcee96580c24d6e2d7f67dd184fa
Author: Robert Levas
Date: Thu Aug 24 09:06:06 2017 -0400
{noformat}
Committed to branch-2.6
{noformat}
commit 42e1b1007f88aeeab9bc77e81896648bfe9a24b3
Author: Robert Levas
Date: Thu Aug 24 09:14:43 2017 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit 2eed29264cb06084bd4a4348e71421d419b22716
Author: Robert Levas
Date: Thu Aug 24 10:25:45 2017 -0400
{noformat}
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140071#comment-16140071
]
Sumit Mohanty commented on AMBARI-18574:
The patch, as such, looks good. Not sure if its intentional but with this
change when Ambari is upgraded the property will show up in HBase config and
require HBase restart. In general, HBase restart is not as problematic as HDFS
but most users do not like to restart any service after Ambari upgrade. So if
you want to avoid HBase restart after Ambari upgrade and rather "fix" this as
part of a stack upgrade then you should set {{}} and make upgrade pack changes to add the config when stack is
upgraded.
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140057#comment-16140057
]
Hudson commented on AMBARI-21798:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7930 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7930/])
AMBARI-21798. Oozie server crashes post migration after regen kerberos (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=60632536aa6fbcee96580c24d6e2d7f67dd184fa])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog252Test.java
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140053#comment-16140053
]
Hudson commented on AMBARI-21798:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #51 (See
[https://builds.apache.org/job/Ambari-branch-2.6/51/])
AMBARI-21798. Oozie server crashes post migration after regen kerberos (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=42e1b1007f88aeeab9bc77e81896648bfe9a24b3])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog252Test.java
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21802) Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode
[
https://issues.apache.org/jira/browse/AMBARI-21802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140039#comment-16140039
]
Hadoop QA commented on AMBARI-21802:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883524/AMBARI-21802_trunk_v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12058//console
This message is automatically generated.
> Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS
> mode
> --
>
> Key: AMBARI-21802
> URL: https://issues.apache.org/jira/browse/AMBARI-21802
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-21802_trunk_v1.patch
>
>
> Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS
> mode
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21798:
--
Priority: Blocker (was: Major)
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21803) Implement STOMP endpoint to provide alert definitions
[ https://issues.apache.org/jira/browse/AMBARI-21803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21803: --- Attachment: AMBARI-21803.patch > Implement STOMP endpoint to provide alert definitions > - > > Key: AMBARI-21803 > URL: https://issues.apache.org/jira/browse/AMBARI-21803 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21803.patch > > > Add endpoint in Ambari Server for agent to query / subscribe to alert > definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21803) Implement STOMP endpoint to provide alert definitions
Doroszlai, Attila created AMBARI-21803: -- Summary: Implement STOMP endpoint to provide alert definitions Key: AMBARI-21803 URL: https://issues.apache.org/jira/browse/AMBARI-21803 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Priority: Critical Fix For: 3.0.0 Add endpoint in Ambari Server for agent to query / subscribe to alert definitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21790) Log Search: hdfs audit log fields are not mapped
[ https://issues.apache.org/jira/browse/AMBARI-21790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139873#comment-16139873 ] Hudson commented on AMBARI-21790: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7929 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7929/]) AMBARI-21790. Log Search: hdfs audit log fields are not mapped (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=65ddaed63e427d404f90d74afaea8537ce5cb51c]) * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/MapFieldNameDescriptorImpl.java > Log Search: hdfs audit log fields are not mapped > > > Key: AMBARI-21790 > URL: https://issues.apache.org/jira/browse/AMBARI-21790 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21802) Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode
[ https://issues.apache.org/jira/browse/AMBARI-21802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21802: - Attachment: AMBARI-21802_trunk_v1.patch > Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS > mode > -- > > Key: AMBARI-21802 > URL: https://issues.apache.org/jira/browse/AMBARI-21802 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21802_trunk_v1.patch > > > Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS > mode -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21802) Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode
[ https://issues.apache.org/jira/browse/AMBARI-21802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21802: - Status: Patch Available (was: Open) > Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS > mode > -- > > Key: AMBARI-21802 > URL: https://issues.apache.org/jira/browse/AMBARI-21802 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > > Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS > mode -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21802) Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode
Prabhjyot Singh created AMBARI-21802: Summary: Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode Key: AMBARI-21802 URL: https://issues.apache.org/jira/browse/AMBARI-21802 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh Zeppelin's secure cookie should only be set when zeppelin is running in HTTPS mode -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21737) Ambari should expose whether a service is able to rolling-restart instead of hard coding service name
[
https://issues.apache.org/jira/browse/AMBARI-21737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139870#comment-16139870
]
Hadoop QA commented on AMBARI-21737:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882283/AMBARI-21737.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12057//console
This message is automatically generated.
> Ambari should expose whether a service is able to rolling-restart instead of
> hard coding service name
> -
>
> Key: AMBARI-21737
> URL: https://issues.apache.org/jira/browse/AMBARI-21737
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Attachments: AMBARI-21737.patch
>
>
> Add a new property rollingRestartSupported to component in the metainfo.xml
> file. This property can be used to decide whether the component supports
> rolling restart.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
[
https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139869#comment-16139869
]
Hadoop QA commented on AMBARI-21798:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883467/AMBARI-21798_branch-2.5_01.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12056//console
This message is automatically generated.
> Oozie server crashes post migration after regen kerberos keytabs and restart
> all services
> -
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-21798_branch-2.5_01.patch,
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com]
> E0550: Could not normalize host name [${host}], Could not resolve host
> [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host
> name [${host}], Could not resolve host [${host}], ${host}: Name or service
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property is now
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts":
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}} ( done via UI, this will kick
> off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139867#comment-16139867
]
Hadoop QA commented on AMBARI-18574:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883477/AMBARI-18574.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12055//console
This message is automatically generated.
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21790) Log Search: hdfs audit log fields are not mapped
[
https://issues.apache.org/jira/browse/AMBARI-21790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-21790.
---
Resolution: Fixed
committed to trunk
{code:java}
commit 65ddaed63e427d404f90d74afaea8537ce5cb51c
Author: oleewere
Date: Wed Aug 23 18:17:58 2017 +0200
AMBARI-21790. Log Search: hdfs audit log fields are not mapped (oleewere)
{code}
> Log Search: hdfs audit log fields are not mapped
>
>
> Key: AMBARI-21790
> URL: https://issues.apache.org/jira/browse/AMBARI-21790
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
