[jira] [Updated] (AMBARI-25086) Upgrading Using a Modified Default Version Repository Fails on Some Services
[ https://issues.apache.org/jira/browse/AMBARI-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25086: Labels: pull-request-available (was: ) > Upgrading Using a Modified Default Version Repository Fails on Some Services > > > Key: AMBARI-25086 > URL: https://issues.apache.org/jira/browse/AMBARI-25086 > Project: Ambari > Issue Type: Task >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > When performing a stack upgrade, if the user chooses the "Default Version > Definition" option and just modifies the default URLs, the backing VDF which > is created and stored in the database contains which do not support > upgrading. > Before the upgrade, if any of these services are in maintenance mode (such as > Ambari Infra), they will prevent the upgrade from starting. > During the actual upgrade, this will cause problems on finalization as those > services/components have not participated, yet the VDF indicates that they > should have. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25086) Upgrading Using a Modified Default Version Repository Fails on Some Services
[ https://issues.apache.org/jira/browse/AMBARI-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-25086: - Summary: Upgrading Using a Modified Default Version Repository Fails on Some Services (was: Trying to upgrade to 3.1 using the Default Version Definition fails) > Upgrading Using a Modified Default Version Repository Fails on Some Services > > > Key: AMBARI-25086 > URL: https://issues.apache.org/jira/browse/AMBARI-25086 > Project: Ambari > Issue Type: Task >Affects Versions: 2.7.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Fix For: 2.8.0 > > > When performing a stack upgrade, if the user chooses the "Default Version > Definition" option and just modifies the default URLs, the backing VDF which > is created and stored in the database contains which do not support > upgrading. > Before the upgrade, if any of these services are in maintenance mode (such as > Ambari Infra), they will prevent the upgrade from starting. > During the actual upgrade, this will cause problems on finalization as those > services/components have not participated, yet the VDF indicates that they > should have. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25088) Enable Kerberos fails when Ambari server is not on a registered host
[
https://issues.apache.org/jira/browse/AMBARI-25088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-25088:
--
Status: Patch Available (was: In Progress)
> Enable Kerberos fails when Ambari server is not on a registered host
>
>
> Key: AMBARI-25088
> URL: https://issues.apache.org/jira/browse/AMBARI-25088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Enable Kerberos fails when Ambari server is not on a registered host.
> The following error is seen in /var/log/ambari-server.log
> {noformat}
> 2019-01-03 15:28:34,238 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c7401.ambari.apache.org
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c7401.ambari.apache.org
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:190)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:174)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy134.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1722)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.getActiveIdentities(KerberosHelperImpl.java:1797)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.calculateServiceIdentities(KerberosServerAction.java:512)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:456)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This is caused when Ambari tried to find the host-specific configuration
> values when processing the Kerberos identities and the host is not registered
> for the relevant cluster. This can happen when the Ambari server Kerberos
> identity is being processed when the Ambari server host is not registered
> with the cluster.
> To solve this, host specific configuration values should not be obtained for
> the non-registered Ambari server host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25088) Enable Kerberos fails when Ambari server is not on a registered host
[
https://issues.apache.org/jira/browse/AMBARI-25088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25088:
Labels: pull-request-available (was: )
> Enable Kerberos fails when Ambari server is not on a registered host
>
>
> Key: AMBARI-25088
> URL: https://issues.apache.org/jira/browse/AMBARI-25088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Enable Kerberos fails when Ambari server is not on a registered host.
> The following error is seen in /var/log/ambari-server.log
> {noformat}
> 2019-01-03 15:28:34,238 WARN [Server Action Executor Worker 39]
> ServerActionExecutor:471 - Task #39 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c7401.ambari.apache.org
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c7401.ambari.apache.org
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:190)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:174)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy134.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1722)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.getActiveIdentities(KerberosHelperImpl.java:1797)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.calculateServiceIdentities(KerberosServerAction.java:512)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:456)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This is caused when Ambari tried to find the host-specific configuration
> values when processing the Kerberos identities and the host is not registered
> for the relevant cluster. This can happen when the Ambari server Kerberos
> identity is being processed when the Ambari server host is not registered
> with the cluster.
> To solve this, host specific configuration values should not be obtained for
> the non-registered Ambari server host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-25080) Unable to install Hive service
[
https://issues.apache.org/jira/browse/AMBARI-25080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-25080.
---
Resolution: Duplicate
Fix Version/s: 2.8.0
> Unable to install Hive service
> --
>
> Key: AMBARI-25080
> URL: https://issues.apache.org/jira/browse/AMBARI-25080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.8.0
>
>
> Steps to reproduce the issue:
> 1. Install Ambari 2.7.1 and HDP3.0.1 with basic services
> 2. Enable the Kerberos for cluster.
> 3. Now try to add the Hive service. service installation would fail.
> 4. Finish the wizard and now try to start the service but it fails with below
> exception.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_metastore.py",
> line 55, in start
> refresh_yarn()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 402, in refresh_yarn
> Execute(params.yarn_kinit_cmd, user = params.yarn_user)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/yarn.service.keytab
> yarn/c2111-node3.hdp@hwx.com;' returned 1. kinit: Client
> 'yarn/c2111-node3.hdp@hwx.com' not found in Kerberos database while
> getting initial credentials
> {noformat}
> Basically during the installation stage one of the task fails with below
> exception and because of that it does not complete all the tasks that were
> part of the installation.
> {noformat}
> 2019-01-02 22:36:32,560 INFO [Server Action Executor Worker 102]
> KerberosServerAction:432 - Processing identities...
> 2019-01-02 22:36:32,649 WARN [Server Action Executor Worker 102]
> ServerActionExecutor:471 - Task #102 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c2111-node1.hdp.com
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c2111-node1.hdp.com
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:189)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:173)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2354)
> at sun.reflect.GeneratedMethodAccessor605.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy131.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1727)
> at
[jira] [Assigned] (AMBARI-25080) Unable to install Hive service
[
https://issues.apache.org/jira/browse/AMBARI-25080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reassigned AMBARI-25080:
-
Assignee: Robert Levas
> Unable to install Hive service
> --
>
> Key: AMBARI-25080
> URL: https://issues.apache.org/jira/browse/AMBARI-25080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Major
>
> Steps to reproduce the issue:
> 1. Install Ambari 2.7.1 and HDP3.0.1 with basic services
> 2. Enable the Kerberos for cluster.
> 3. Now try to add the Hive service. service installation would fail.
> 4. Finish the wizard and now try to start the service but it fails with below
> exception.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_metastore.py",
> line 55, in start
> refresh_yarn()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 402, in refresh_yarn
> Execute(params.yarn_kinit_cmd, user = params.yarn_user)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/yarn.service.keytab
> yarn/c2111-node3.hdp@hwx.com;' returned 1. kinit: Client
> 'yarn/c2111-node3.hdp@hwx.com' not found in Kerberos database while
> getting initial credentials
> {noformat}
> Basically during the installation stage one of the task fails with below
> exception and because of that it does not complete all the tasks that were
> part of the installation.
> {noformat}
> 2019-01-02 22:36:32,560 INFO [Server Action Executor Worker 102]
> KerberosServerAction:432 - Processing identities...
> 2019-01-02 22:36:32,649 WARN [Server Action Executor Worker 102]
> ServerActionExecutor:471 - Task #102 failed to complete execution due to
> thrown exception: org.apache.ambari.server.HostNotFoundException:Host not
> found, hostname=c2111-node1.hdp.com
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=c2111-node1.hdp.com
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:189)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:173)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2354)
> at sun.reflect.GeneratedMethodAccessor605.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy131.findConfigurationTagsWithOverrides(Unknown
> Source)
> at
> org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1727)
> at
> org.apache.ambari.server.controller.KerberosHelperI
[jira] [Created] (AMBARI-25088) Enable Kerberos fails when Ambari server is not on a registered host
Robert Levas created AMBARI-25088:
-
Summary: Enable Kerberos fails when Ambari server is not on a
registered host
Key: AMBARI-25088
URL: https://issues.apache.org/jira/browse/AMBARI-25088
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: amarnath reddy pappu
Assignee: Robert Levas
Fix For: 2.8.0
Enable Kerberos fails when Ambari server is not on a registered host.
The following error is seen in /var/log/ambari-server.log
{noformat}
2019-01-03 15:28:34,238 WARN [Server Action Executor Worker 39]
ServerActionExecutor:471 - Task #39 failed to complete execution due to thrown
exception: org.apache.ambari.server.HostNotFoundException:Host not found,
hostname=c7401.ambari.apache.org
org.apache.ambari.server.HostNotFoundException: Host not found,
hostname=c7401.ambari.apache.org
at
org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:190)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:174)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2431)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
at com.sun.proxy.$Proxy134.findConfigurationTagsWithOverrides(Unknown
Source)
at
org.apache.ambari.server.state.ConfigHelper.calculateExistingConfigurations(ConfigHelper.java:2158)
at
org.apache.ambari.server.controller.KerberosHelperImpl.calculateConfigurations(KerberosHelperImpl.java:1722)
at
org.apache.ambari.server.controller.KerberosHelperImpl.getActiveIdentities(KerberosHelperImpl.java:1797)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.calculateServiceIdentities(KerberosServerAction.java:512)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:456)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
at java.lang.Thread.run(Thread.java:745)
{noformat}
This is caused when Ambari tried to find the host-specific configuration values
when processing the Kerberos identities and the host is not registered for the
relevant cluster. This can happen when the Ambari server Kerberos identity is
being processed when the Ambari server host is not registered with the cluster.
To solve this, host specific configuration values should not be obtained for
the non-registered Ambari server host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25087) Heartbeat lost - Heartbeat building is taking time
amarnath reddy pappu created AMBARI-25087:
-
Summary: Heartbeat lost - Heartbeat building is taking time
Key: AMBARI-25087
URL: https://issues.apache.org/jira/browse/AMBARI-25087
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: amarnath reddy pappu
In the past has reported several issues where they complained about Agents
loosing the heartbeat but re-starting the agent is fixing the issue.
In the logs it shows that building heart beat message and sending to request is
taking close to 40-50seconds.
{noformat}
INFO 2018-12-17 22:30:48,746 Controller.py:304 - Heartbeat (response id = 82)
with server is running...
INFO 2018-12-17 22:30:48,851 Controller.py:311 - Building heartbeat message
INFO 2018-12-17 22:31:29,374 logger.py:75 - Testing the JVM's JCE policy to see
it if supports an unlimited key length.
INFO 2018-12-17 22:31:30,017 Hardware.py:188 - Some mount points were ignored:
/run, /dev/shm, /run/lock, /sys/fs/cgroup, /run/user/2008, /run/user/202,
/run/user/2002, /run/user/2001, /run/user/203, /run/user/2007, /run/user/2019
INFO 2018-12-17 22:31:51,672 Controller.py:333 - Heartbeat response received
(id = 83)
INFO 2018-12-17 22:28:44,155 Controller.py:311 - Building heartbeat message
INFO 2018-12-17 22:29:14,883 logger.py:75 - Testing the JVM's JCE policy to see
it if supports an unlimited key length.
INFO 2018-12-17 22:29:17,051 Hardware.py:188 - Some mount points were ignored:
/run, /dev/shm, /run/lock, /sys/fs/cgroup, /run/user/2008, /run/user/202,
/run/user/2002, /run/user/2001, /run/user/203, /run/user/2007, /run/user/2019
{noformat}
We have generated multiple thread dumps to see what is happening while thread
is waiting at that point. in multiple dumps thread is kept waiting at below log
line.
{noformat}
# ThreadID: 139846973957888
File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap
self.__bootstrap_inner()
File: "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 501, in run
self.registerAndHeartbeat()
File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 529, in
registerAndHeartbeat
self.heartbeatWithServer()
File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 313, in
heartbeatWithServer
data = json.dumps(self.heartbeat.build(self.responseId, send_state,
self.hasMappedComponents))
File: "/usr/lib/ambari-agent/lib/ambari_agent/Heartbeat.py", line 83, in build
logger.debug("Heartbeat: %s", pformat(heartbeat))
File: "/usr/lib/python2.7/pprint.py", line 63, in pformat
return PrettyPrinter(indent=indent, width=width, depth=depth).pformat(object)
File: "/usr/lib/python2.7/pprint.py", line 122, in pformat
self._format(object, sio, 0, 0, {}, 0)
File: "/usr/lib/python2.7/pprint.py", line 164, in _format
allowance + 1, context, level)
{noformat}
So for some reason pformat is taking lot of time ( 30-35 seconds ) to format
the message ( Have not enabled the DEBUG logging)
{noformat}
if int(id) == 0:
componentsMapped = False
logger.debug("Building Heartbeat: {responseId = %s, timestamp = %s, "
"commandsInProgress = %s, componentsMapped = %s,"
"recoveryTimestamp = %s}",
str(id), str(timestamp), repr(commandsInProgress),
repr(componentsMapped), str(recovery_timestamp))
logger.debug("Heartbeat: %s", pformat(heartbeat))
hostInfo = HostInfo(self.config)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25087) Heartbeat lost - Heartbeat building is taking time
[
https://issues.apache.org/jira/browse/AMBARI-25087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733398#comment-16733398
]
amarnath reddy pappu commented on AMBARI-25087:
---
Following change has fixed the issue - at least was unable to reproduce it
after the change
{noformat}
diff --git a/ambari-agent/src/main/python/ambari_agent/Heartbeat.py
b/ambari-agent/src/main/python/ambari_agent/Heartbeat.py
index d7c0325..11ad652 100644
--- a/ambari-agent/src/main/python/ambari_agent/Heartbeat.py
+++ b/ambari-agent/src/main/python/ambari_agent/Heartbeat.py
@@ -75,12 +75,12 @@ class Heartbeat:
if int(id) == 0:
componentsMapped = False
-logger.debug("Building Heartbeat: {responseId = %s, timestamp = %s, "
-"commandsInProgress = %s, componentsMapped = %s,"
-"recoveryTimestamp = %s}",
-str(id), str(timestamp), repr(commandsInProgress),
repr(componentsMapped), str(recovery_timestamp))
-
-logger.debug("Heartbeat: %s", pformat(heartbeat))
+if logger.isEnabledFor(logging.DEBUG):
+ logger.debug("Building Heartbeat: {responseId = %s, timestamp = %s, "
+ "commandsInProgress = %s, componentsMapped = %s, "
+ "recoveryTimestamp = %s}",
+ id, timestamp, commandsInProgress, componentsMapped,
recovery_timestamp)
+ logger.debug("Heartbeat: %s", pformat(heartbeat))
{noformat}
> Heartbeat lost - Heartbeat building is taking time
> --
>
> Key: AMBARI-25087
> URL: https://issues.apache.org/jira/browse/AMBARI-25087
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
>
> In the past has reported several issues where they complained about
> Agents loosing the heartbeat but re-starting the agent is fixing the issue.
> In the logs it shows that building heart beat message and sending to request
> is taking close to 40-50seconds.
> {noformat}
> INFO 2018-12-17 22:30:48,746 Controller.py:304 - Heartbeat (response id = 82)
> with server is running...
> INFO 2018-12-17 22:30:48,851 Controller.py:311 - Building heartbeat message
> INFO 2018-12-17 22:31:29,374 logger.py:75 - Testing the JVM's JCE policy to
> see it if supports an unlimited key length.
> INFO 2018-12-17 22:31:30,017 Hardware.py:188 - Some mount points were
> ignored: /run, /dev/shm, /run/lock, /sys/fs/cgroup, /run/user/2008,
> /run/user/202, /run/user/2002, /run/user/2001, /run/user/203, /run/user/2007,
> /run/user/2019
> INFO 2018-12-17 22:31:51,672 Controller.py:333 - Heartbeat response received
> (id = 83)
> INFO 2018-12-17 22:28:44,155 Controller.py:311 - Building heartbeat message
> INFO 2018-12-17 22:29:14,883 logger.py:75 - Testing the JVM's JCE policy to
> see it if supports an unlimited key length.
> INFO 2018-12-17 22:29:17,051 Hardware.py:188 - Some mount points were
> ignored: /run, /dev/shm, /run/lock, /sys/fs/cgroup, /run/user/2008,
> /run/user/202, /run/user/2002, /run/user/2001, /run/user/203, /run/user/2007,
> /run/user/2019
> {noformat}
> We have generated multiple thread dumps to see what is happening while thread
> is waiting at that point. in multiple dumps thread is kept waiting at below
> log line.
> {noformat}
> # ThreadID: 139846973957888
> File: "/usr/lib/python2.7/threading.py", line 774, in __bootstrap
> self.__bootstrap_inner()
> File: "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
> self.run()
> File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 501, in run
> self.registerAndHeartbeat()
> File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 529, in
> registerAndHeartbeat
> self.heartbeatWithServer()
> File: "/usr/lib/ambari-agent/lib/ambari_agent/Controller.py", line 313, in
> heartbeatWithServer
> data = json.dumps(self.heartbeat.build(self.responseId, send_state,
> self.hasMappedComponents))
> File: "/usr/lib/ambari-agent/lib/ambari_agent/Heartbeat.py", line 83, in build
> logger.debug("Heartbeat: %s", pformat(heartbeat))
> File: "/usr/lib/python2.7/pprint.py", line 63, in pformat
> return PrettyPrinter(indent=indent, width=width,
> depth=depth).pformat(object)
> File: "/usr/lib/python2.7/pprint.py", line 122, in pformat
> self._format(object, sio, 0, 0, {}, 0)
> File: "/usr/lib/python2.7/pprint.py", line 164, in _format
> allowance + 1, context, level)
> {noformat}
> So for some reason pformat is taking lot of time ( 30-35 seconds ) to format
> the message ( Have not enabled the DEBUG logging)
> {noformat}
> if int(id) == 0:
> componentsMapped = False
> logger.debug("Building Heartbeat: {responseId = %s, timestamp = %s, "
> "commandsInProgress = %s, componentsMapped = %s,"
>
[jira] [Created] (AMBARI-25086) Trying to upgrade to 3.1 using the Default Version Definition fails
Jonathan Hurley created AMBARI-25086: Summary: Trying to upgrade to 3.1 using the Default Version Definition fails Key: AMBARI-25086 URL: https://issues.apache.org/jira/browse/AMBARI-25086 Project: Ambari Issue Type: Task Affects Versions: 2.7.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.8.0 When performing a stack upgrade, if the user chooses the "Default Version Definition" option and just modifies the default URLs, the backing VDF which is created and stored in the database contains which do not support upgrading. Before the upgrade, if any of these services are in maintenance mode (such as Ambari Infra), they will prevent the upgrade from starting. During the actual upgrade, this will cause problems on finalization as those services/components have not participated, yet the VDF indicates that they should have. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25085) Cover hdfs widgets view
[ https://issues.apache.org/jira/browse/AMBARI-25085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25085: Labels: pull-request-available (was: ) > Cover hdfs widgets view > --- > > Key: AMBARI-25085 > URL: https://issues.apache.org/jira/browse/AMBARI-25085 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-25085) Cover hdfs widgets view
[ https://issues.apache.org/jira/browse/AMBARI-25085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25085: Assignee: Antonenko Alexander > Cover hdfs widgets view > --- > > Key: AMBARI-25085 > URL: https://issues.apache.org/jira/browse/AMBARI-25085 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25085) Cover hdfs widgets view
Antonenko Alexander created AMBARI-25085: Summary: Cover hdfs widgets view Key: AMBARI-25085 URL: https://issues.apache.org/jira/browse/AMBARI-25085 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25084) Delete identities fails when removing service in reverse order
[
https://issues.apache.org/jira/browse/AMBARI-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25084:
Labels: pull-request-available (was: )
> Delete identities fails when removing service in reverse order
> --
>
> Key: AMBARI-25084
> URL: https://issues.apache.org/jira/browse/AMBARI-25084
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> (reverse order = host components first, then components, then service)
> STR:
> Install ZooKeeper + Kafka + Kerberos
> Stop Kafka
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c7401.ambari.apache.org/host_components/KAFKA_BROKER
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA/components/KAFKA_BROKER
> => identities are removed
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA
> => identity removal fails with PersistenceException
> {code}
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.6.2.v20151217-774c696):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
> at
> org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:53)
> at
> org.apache.ambari.server.orm.dao.ClusterDAO.getLatestConfigurationsWithTypes(ClusterDAO.java:226)
> at
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:44)
> at
> o
[jira] [Updated] (AMBARI-25084) Delete identities fails when removing service in reverse order
[
https://issues.apache.org/jira/browse/AMBARI-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-25084:
---
Fix Version/s: 2.8.0
> Delete identities fails when removing service in reverse order
> --
>
> Key: AMBARI-25084
> URL: https://issues.apache.org/jira/browse/AMBARI-25084
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Fix For: 2.8.0
>
>
> (reverse order = host components first, then components, then service)
> STR:
> Install ZooKeeper + Kafka + Kerberos
> Stop Kafka
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c7401.ambari.apache.org/host_components/KAFKA_BROKER
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA/components/KAFKA_BROKER
> => identities are removed
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA
> => identity removal fails with PersistenceException
> {code}
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.6.2.v20151217-774c696):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
> at
> org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:53)
> at
> org.apache.ambari.server.orm.dao.ClusterDAO.getLatestConfigurationsWithTypes(ClusterDAO.java:226)
> at
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:44)
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getLatestConfigsW
[jira] [Updated] (AMBARI-25084) Delete identities fails when removing service in reverse order
[
https://issues.apache.org/jira/browse/AMBARI-25084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-25084:
---
Affects Version/s: 2.7.0
> Delete identities fails when removing service in reverse order
> --
>
> Key: AMBARI-25084
> URL: https://issues.apache.org/jira/browse/AMBARI-25084
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
>
> (reverse order = host components first, then components, then service)
> STR:
> Install ZooKeeper + Kafka + Kerberos
> Stop Kafka
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c7401.ambari.apache.org/host_components/KAFKA_BROKER
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA/components/KAFKA_BROKER
> => identities are removed
> curl -X DELETE
> http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA
> => identity removal fails with PersistenceException
> {code}
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.6.2.v20151217-774c696):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
> or near ")"
> Position: 210
> Error Code: 0
> Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
> t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
> t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
> (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
> (SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE
> (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
> t0.type_name)
> bind => [4 parameters bound]
> Query:
> ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
> referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
> t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
> t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0
> WHERE t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?))
> AND (t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM
> clusterconfig t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND
> (t1.type_name = t0.type_name)")
> FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId,
> type, version, unmapped, configId, configGroupConfigMappingEntities, tag,
> selected, timestamp, clusterEntity}
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
> at
> org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:53)
> at
> org.apache.ambari.server.orm.dao.ClusterDAO.getLatestConfigurationsWithTypes(ClusterDAO.java:226)
> at
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:44)
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getLatestConfigsWithTypes(ClusterImpl.java:1
[jira] [Created] (AMBARI-25084) Delete identities fails when removing service in reverse order
Attila Magyar created AMBARI-25084:
--
Summary: Delete identities fails when removing service in reverse
order
Key: AMBARI-25084
URL: https://issues.apache.org/jira/browse/AMBARI-25084
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Attila Magyar
Assignee: Attila Magyar
(reverse order = host components first, then components, then service)
STR:
Install ZooKeeper + Kafka + Kerberos
Stop Kafka
curl -X DELETE
http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c7401.ambari.apache.org/host_components/KAFKA_BROKER
curl -X DELETE
http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA/components/KAFKA_BROKER
=> identities are removed
curl -X DELETE
http://c7401.ambari.apache.org:8080/api/v1/clusters/TEST/services/KAFKA
=> identity removal fails with PersistenceException
{code}
Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
or near ")"
Position: 210
Error Code: 0
Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
(t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
(SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE (((t1.cluster_id
= ?) AND (t1.stack_id = ?)) AND (t1.type_name = t0.type_name)
bind => [4 parameters bound]
Query:
ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0 WHERE
t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND
(t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM clusterconfig
t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
t0.type_name)")
FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId, type,
version, unmapped, configId, configGroupConfigMappingEntities, tag, selected,
timestamp, clusterEntity}
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.postgresql.util.PSQLException: ERROR: syntax error at
or near ")"
Position: 210
Error Code: 0
Call: SELECT t0.config_id, t0.cluster_id, t0.selected, t0.selected_timestamp,
t0.version_tag, t0.create_timestamp, t0.type_name, t0.unmapped, t0.version,
t0.stack_id FROM clusterconfig t0 WHERE t0.type_name IN ()) AND
(t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND (t0.selected_timestamp =
(SELECT MAX(t1.selected_timestamp) FROM clusterconfig t1 WHERE (((t1.cluster_id
= ?) AND (t1.stack_id = ?)) AND (t1.type_name = t0.type_name)
bind => [4 parameters bound]
Query:
ReadAllQuery(name="ClusterConfigEntity.findLatestConfigsByStackWithTypes"
referenceClass=ClusterConfigEntity sql="SELECT t0.config_id, t0.cluster_id,
t0.selected, t0.selected_timestamp, t0.version_tag, t0.create_timestamp,
t0.type_name, t0.unmapped, t0.version, t0.stack_id FROM clusterconfig t0 WHERE
t0.type_name IN ?) AND (t0.cluster_id = ?)) AND (t0.stack_id = ?)) AND
(t0.selected_timestamp = (SELECT MAX(t1.selected_timestamp) FROM clusterconfig
t1 WHERE (((t1.cluster_id = ?) AND (t1.stack_id = ?)) AND (t1.type_name =
t0.type_name)")
FetchGroup(){serviceConfigEntities, stack, selectedTimestamp, clusterId, type,
version, unmapped, configId, configGroupConfigMappingEntities, tag, selected,
timestamp, clusterEntity}
at
org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
at
org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
at
org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
at
org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:53)
at
org.apache.ambari.server.orm.dao.ClusterDAO.getLatestConfigurationsWithTypes(ClusterDAO.java:226)
at
org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:44)
at
org.apache.ambari.server.state.cluster.ClusterImpl.getLatestConfigsWithTypes(ClusterImpl.java:1185)
at
org.apache.ambari.server.controller.DeleteIdentityHandler$PrepareDeleteIdentityServerAction.extendWithDeletedConfigOfService(DeleteIdentityHandler.java:304)
at
org.apache.ambari.server.controller.DeleteIdentityHandler$PrepareDeleteIdentityServerAction.calculateConfig(DeleteIdentityHandler.java:296)
at
org.apache.ambari.server.controller.DeleteIdentityHandler$PrepareDeleteIdentityServer
[jira] [Commented] (AMBARI-25083) Log Search: fallback to use dynamic field 'ws_*' if new field name contains whitespace
[ https://issues.apache.org/jira/browse/AMBARI-25083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733045#comment-16733045 ] Hudson commented on AMBARI-25083: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #84 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/84/]) AMBARI-25083. Fallback to use dynamic field 'ws_*' if new field name (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=fc0edf50198f5ee8e24aeeffef84cfbdcaa024f7]) * (edit) ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/filter/Filter.java > Log Search: fallback to use dynamic field 'ws_*' if new field name contains > whitespace > -- > > Key: AMBARI-25083 > URL: https://issues.apache.org/jira/browse/AMBARI-25083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25083) Log Search: fallback to use dynamic field 'ws_*' if new field name contains whitespace
[ https://issues.apache.org/jira/browse/AMBARI-25083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25083: Labels: pull-request-available (was: ) > Log Search: fallback to use dynamic field 'ws_*' if new field name contains > whitespace > -- > > Key: AMBARI-25083 > URL: https://issues.apache.org/jira/browse/AMBARI-25083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25082) Cover HA wizard controller with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733014#comment-16733014 ] Hudson commented on AMBARI-25082: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10410 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10410/]) AMBARI-25082 Cover HA wizard controller with unit tests (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1b58df7829ad92fdb81042f29d97a07257d90705]) * (edit) ambari-web/app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js * (add) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller_test.js * (edit) ambari-web/app/assets/test/tests.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller_test.js > Cover HA wizard controller with unit tests > -- > > Key: AMBARI-25082 > URL: https://issues.apache.org/jira/browse/AMBARI-25082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * > app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js > * > app/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25083) Log Search: fallback to dynamic field 'ws_*' if new field name contains whitespace
Olivér Szabó created AMBARI-25083: - Summary: Log Search: fallback to dynamic field 'ws_*' if new field name contains whitespace Key: AMBARI-25083 URL: https://issues.apache.org/jira/browse/AMBARI-25083 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.8.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25083) Log Search: fallback to use dynamic field 'ws_*' if new field name contains whitespace
[ https://issues.apache.org/jira/browse/AMBARI-25083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-25083: -- Summary: Log Search: fallback to use dynamic field 'ws_*' if new field name contains whitespace (was: Log Search: fallback to dynamic field 'ws_*' if new field name contains whitespace) > Log Search: fallback to use dynamic field 'ws_*' if new field name contains > whitespace > -- > > Key: AMBARI-25083 > URL: https://issues.apache.org/jira/browse/AMBARI-25083 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25082) Cover HA wizard controller with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-25082. --- Resolution: Fixed > Cover HA wizard controller with unit tests > -- > > Key: AMBARI-25082 > URL: https://issues.apache.org/jira/browse/AMBARI-25082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * > app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js > * > app/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-25082) Cover HA wizard controller with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732993#comment-16732993 ] Andrii Tkach commented on AMBARI-25082: --- committed to trunk > Cover HA wizard controller with unit tests > -- > > Key: AMBARI-25082 > URL: https://issues.apache.org/jira/browse/AMBARI-25082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * > app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js > * > app/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25082) Cover HA wizard controller with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25082: Labels: pull-request-available (was: ) > Cover HA wizard controller with unit tests > -- > > Key: AMBARI-25082 > URL: https://issues.apache.org/jira/browse/AMBARI-25082 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Following files to cover: > * > app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js > * > app/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25082) Cover HA wizard controller with unit tests
Andrii Tkach created AMBARI-25082: - Summary: Cover HA wizard controller with unit tests Key: AMBARI-25082 URL: https://issues.apache.org/jira/browse/AMBARI-25082 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.8.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.8.0 Following files to cover: * app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js * app/controllers/main/admin/highAvailability/hawq/addStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25081) [Log Search UI] Add pagination settings to the user settings
Istvan Tobias created AMBARI-25081: -- Summary: [Log Search UI] Add pagination settings to the user settings Key: AMBARI-25081 URL: https://issues.apache.org/jira/browse/AMBARI-25081 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias Add the pagination settings (page size) to the user settings, so that user can see the same number of list item every login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25081) [Log Search UI] Add pagination settings to the user settings
[ https://issues.apache.org/jira/browse/AMBARI-25081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25081: --- Issue Type: Task (was: Bug) > [Log Search UI] Add pagination settings to the user settings > > > Key: AMBARI-25081 > URL: https://issues.apache.org/jira/browse/AMBARI-25081 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Add the pagination settings (page size) to the user settings, so that user > can see the same number of list item every login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25029) [Log Search UI] change the colors of the service links
[ https://issues.apache.org/jira/browse/AMBARI-25029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-25029: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] change the colors of the service links > -- > > Key: AMBARI-25029 > URL: https://issues.apache.org/jira/browse/AMBARI-25029 > Project: Ambari > Issue Type: Sub-task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
