[jira] [Assigned] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.
[
https://issues.apache.org/jira/browse/AMBARI-23604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore reassigned AMBARI-23604:
--
Assignee: Nitiraj Singh Rathore
> ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in
> table buckets specification when uploading table using Hive view 2.0.
> -
>
> Key: AMBARI-23604
> URL: https://issues.apache.org/jira/browse/AMBARI-23604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: HDP 2.6.3
> Ambari 2.6.1
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: test_csv.csv
>
>
> *Problem:*
> When uploading table using CSV file as transactional table, below is the
> error see:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:116 mismatched input
> 'ROW' expecting INTO near ')' in table buckets specification
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
> at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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)
> {code}
> *Steps to replicate:*
> 1. Upload the attached file.
> 2. Select any of the columns as 'clustered'.
> 3. Under Advanced options, enable transactional and buckets=4.
> 4. Click on create table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22270) Ambari should warn user when G1GC is used on Java 7
[ https://issues.apache.org/jira/browse/AMBARI-22270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-22270: Description: Java 7 runtime doesn't handle G1GC in robust manner. Ambari should warn user when G1GC is chosen on JDK 7. was: Java 7 runtime doesn't handle G1GC in robust manner. Ambari should warn user when G1GC is chosen on JDK 7. > Ambari should warn user when G1GC is used on Java 7 > --- > > Key: AMBARI-22270 > URL: https://issues.apache.org/jira/browse/AMBARI-22270 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > Java 7 runtime doesn't handle G1GC in robust manner. > Ambari should warn user when G1GC is chosen on JDK 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22621) Ensure value for hbase.coprocessor.abortonerror is true
[ https://issues.apache.org/jira/browse/AMBARI-22621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-22621: Description: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. was: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. > Ensure value for hbase.coprocessor.abortonerror is true > --- > > Key: AMBARI-22621 > URL: https://issues.apache.org/jira/browse/AMBARI-22621 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > In the coprocessor refactor for hbase-2, Server#abort has been taken out of > reach. > We should ensure that value for hbase.coprocessor.abortonerror is true so > that coprocessor can abort the server by throwing exception. > See HBASE-19341 for related details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23288) stateWatcherClient should be closed upon return from OutputSolr#createSolrStateWatcher
[
https://issues.apache.org/jira/browse/AMBARI-23288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-23288:
Description:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
was:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
> stateWatcherClient should be closed upon return from
> OutputSolr#createSolrStateWatcher
> --
>
> Key: AMBARI-23288
> URL: https://issues.apache.org/jira/browse/AMBARI-23288
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> CloudSolrClient stateWatcherClient = createSolrClient();
> {code}
> stateWatcherClient should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23594) LZO Libraries Are Not Installed Correctly During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-23594.
--
Resolution: Fixed
> LZO Libraries Are Not Installed Correctly During Upgrade
>
>
> Key: AMBARI-23594
> URL: https://issues.apache.org/jira/browse/AMBARI-23594
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.6.1.5-3 and HDP version: 2.6.1.0-129
> # Upgrade Ambari to Target Version: 2.7.0.0-312, then upgrade AMS
> # Delete unsupported services like Flume, Falcon
> # Try Express Upgrade to HDP-3.0.0.0-1192
>
> *Result*
> Oozie server start failed
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 154, in
> OozieServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie.py",
> line 196, in oozie
> Execute(format('{sudo} cp {hadoop_lib_home}/hadoop-lzo*.jar
> {oozie_lib_dir}'),
> 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
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh cp /usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar
> /usr/hdp/current/oozie-server' returned 1. cp: cannot stat
> '/usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23601) NN Federation Wizard: Format NameNode fails due to stopped NameNodes
[ https://issues.apache.org/jira/browse/AMBARI-23601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23601. -- Resolution: Fixed committed to trunk > NN Federation Wizard: Format NameNode fails due to stopped NameNodes > > > Key: AMBARI-23601 > URL: https://issues.apache.org/jira/browse/AMBARI-23601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > NameNodes are stopped in first step of the flow. This prevents _Format > NameNode_ step from getting clusterId of existing NameNodes. > NameNodes should be started, too, after JournalNodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23607) Server must generated "tag" when configs are created/updated
Madhuvanthi Radhakrishnan created AMBARI-23607: -- Summary: Server must generated "tag" when configs are created/updated Key: AMBARI-23607 URL: https://issues.apache.org/jira/browse/AMBARI-23607 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 The "tag" value submitted with service configs is supposed to be a unique ID. It should be generated on the server when a service config is created or a new config version is created. The UI will not pass this value going forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23582) UI reads service versions from base stack repo
[ https://issues.apache.org/jira/browse/AMBARI-23582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23582. -- Resolution: Fixed Fix Version/s: trunk > UI reads service versions from base stack repo > -- > > Key: AMBARI-23582 > URL: https://issues.apache.org/jira/browse/AMBARI-23582 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After HDP upgrade to HDP-2.6.5.0 Kafka and Spark is supposed to have versions > 1.0 and 2.3 as per the latest changes. But Ambari UI shows it incorrectly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23606) Lifecycle-Bulk: Components can be added even when ambari agent is down
[ https://issues.apache.org/jira/browse/AMBARI-23606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23606: Labels: pull-request-available (was: ) > Lifecycle-Bulk: Components can be added even when ambari agent is down > -- > > Key: AMBARI-23606 > URL: https://issues.apache.org/jira/browse/AMBARI-23606 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > Skip hosts that do not have heartbeat while adding components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23602) NN Federation Lower priority changes
[ https://issues.apache.org/jira/browse/AMBARI-23602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-23602. --- Resolution: Fixed Merged to trunk > NN Federation Lower priority changes > > > Key: AMBARI-23602 > URL: https://issues.apache.org/jira/browse/AMBARI-23602 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > - The add metric in the HDFS Metrics needs more padding around it > - Create metric - because of menu depth the name of the metric is hard to > see, we should wrap them and do anything to make sure the metric names are > easily readable > - In the move master wizard we need to add the namespace before the word > "NameNode", like "ns1 NameNode" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23606) Lifecycle-Bulk: Components can be added even when ambari agent is down
Ishan Bhatt created AMBARI-23606: Summary: Lifecycle-Bulk: Components can be added even when ambari agent is down Key: AMBARI-23606 URL: https://issues.apache.org/jira/browse/AMBARI-23606 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk Skip hosts that do not have heartbeat while adding components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23552) Switch to using Surrogate PK in Ambari DB tables, wherever applicable.
[
https://issues.apache.org/jira/browse/AMBARI-23552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar resolved AMBARI-23552.
--
Resolution: Fixed
> Switch to using Surrogate PK in Ambari DB tables, wherever applicable.
> --
>
> Key: AMBARI-23552
> URL: https://issues.apache.org/jira/browse/AMBARI-23552
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> The {{clusterservices}} table was given a new surrogate, auto-incrementing
> primary key:
> {code}
> @Entity
> @TableGenerator(name = "service_id_generator",
> table = "ambari_sequences", pkColumnName = "sequence_name", valueColumnName
> = "sequence_value"
> , pkColumnValue = "service_id_seq"
> , initialValue = 1
> )
> {code}
> However, the table doesn't use this for its PK. Instead, it combines it with
> 2 other columns. This would allow a single Service Group to be a part of 2
> clusters and still be considered unique (which is incorrect). Compound PKs
> also present a problem in slower cloud-based databases as they can cause
> table locks on read which lead to deadlocks in the database:
> {code}
> CREATE TABLE clusterservices (
> id BIGINT NOT NULL,
> service_name VARCHAR(255) NOT NULL,
> service_type VARCHAR(255) NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_group_id BIGINT NOT NULL,
> service_enabled INTEGER NOT NULL,
> CONSTRAINT PK_clusterservices PRIMARY KEY (id, service_group_id,
> cluster_id),
> CONSTRAINT UQ_service_id UNIQUE (id),
> CONSTRAINT FK_clusterservices_cluster_id FOREIGN KEY (service_group_id,
> cluster_id) REFERENCES servicegroups (id, cluster_id));
> {code}
> By not using the surrogate PK, we also cause other tables, like
> {{serviceconfig}} to have to create compound FKs as well:
> {code}
> CONSTRAINT FK_serviceconfig_clstr_svc FOREIGN KEY (service_id,
> service_group_id, cluster_id) REFERENCES clusterservices (id,
> service_group_id, cluster_id),
> {code}
> This should just be a single FK to the surrogate ID.
> Same for some other other tables, too, like {{servicegroups}}:
> {code}
> CREATE TABLE servicegroups (
> id BIGINT NOT NULL,
> service_group_name VARCHAR(255) NOT NULL,
> cluster_id BIGINT NOT NULL,
> CONSTRAINT PK_servicegroups PRIMARY KEY (id, cluster_id),
> CONSTRAINT FK_servicegroups_cluster_id FOREIGN KEY (cluster_id) REFERENCES
> clusters (cluster_id));
> {code}
> It uses a surrogate auto-incrementing ID, but it's PK is a compound.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23605) Add Host wizard not working
Jason Golieb created AMBARI-23605: - Summary: Add Host wizard not working Key: AMBARI-23605 URL: https://issues.apache.org/jira/browse/AMBARI-23605 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Add Host wizard is broken due to changes in shared code with the Install wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.
Sindhu Subhas created AMBARI-23604:
--
Summary: ParseException line 1:116 mismatched input 'ROW'
expecting INTO near ')' in table buckets specification when uploading table
using Hive view 2.0.
Key: AMBARI-23604
URL: https://issues.apache.org/jira/browse/AMBARI-23604
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.6.1
Environment: HDP 2.6.3
Ambari 2.6.1
Reporter: Sindhu Subhas
Attachments: test_csv.csv
*Problem:*
When uploading table using CSV file as transactional table, below is the error
see:
{code:java}
java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error while
compiling statement: FAILED: ParseException line 1:116 mismatched input 'ROW'
expecting INTO near ')' in table buckets specification
java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error while
compiling statement: FAILED: ParseException line 1:116 mismatched input 'ROW'
expecting INTO near ')' in table buckets specification
at
org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
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)
{code}
*Steps to replicate:*
1. Upload the attached file.
2. Select any of the columns as 'clustered'.
3. Under Advanced options, enable transactional and buckets=4.
4. Click on create table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23287) Lack of synchronization accessing topologyHolder in HostResourceProvider#processDeleteHostRequests
[ https://issues.apache.org/jira/browse/AMBARI-23287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-23287: Description: HostResourceProvider#processDeleteHostRequests accesses topologyHolder without any synchronization . was: HostResourceProvider#processDeleteHostRequests accesses topologyHolder without any synchronization. > Lack of synchronization accessing topologyHolder in > HostResourceProvider#processDeleteHostRequests > -- > > Key: AMBARI-23287 > URL: https://issues.apache.org/jira/browse/AMBARI-23287 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Minor > > HostResourceProvider#processDeleteHostRequests accesses topologyHolder > without any synchronization . > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22965) Boolean#getBoolean is used to parse value
[
https://issues.apache.org/jira/browse/AMBARI-22965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-22965:
Description:
In StormTimelineMetricsReporter.java :
{code}
if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
setInstanceId =
Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
{code}
According to
https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
{code}
Returns true if and only if the system property named by the argument exists
and is equal to the string "true"
{code}
This was not the intention of the quoted code.
FlumeTimelineMetricsSink.java may have the same issue.
was:
In StormTimelineMetricsReporter.java :
{code}
if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
setInstanceId =
Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
{code}
According to
https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
{code}
Returns true if and only if the system property named by the argument exists
and is equal to the string "true"
{code}
This was not the intention of the quoted code.
FlumeTimelineMetricsSink.java may have the same issue.
> Boolean#getBoolean is used to parse value
> -
>
> Key: AMBARI-22965
> URL: https://issues.apache.org/jira/browse/AMBARI-22965
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> In StormTimelineMetricsReporter.java :
> {code}
> if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
> setInstanceId =
> Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
> {code}
> According to
> https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
> {code}
> Returns true if and only if the system property named by the argument exists
> and is equal to the string "true"
> {code}
> This was not the intention of the quoted code.
> FlumeTimelineMetricsSink.java may have the same issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-23470) None of the Ambari View works because of 'X-Frame-Options' to 'deny' error
[
https://issues.apache.org/jira/browse/AMBARI-23470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi reassigned AMBARI-23470:
--
Assignee: Myroslav Papirkovskyi
> None of the Ambari View works because of 'X-Frame-Options' to 'deny' error
> ---
>
> Key: AMBARI-23470
> URL: https://issues.apache.org/jira/browse/AMBARI-23470
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views, ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: Myroslav Papirkovskyi
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In Ambari 2.7.0, While accessing any View like HiveView 2.0 we see a blank
> page.
> On te Browser Debugger Console we see the XFrame related error as following:
> {code}
> Refused to display
> 'http://latest1.example.com:8080/#/login?targetURI=/views/HIVE/2.0.0/Hive20/'
> in a frame because it set 'X-Frame-Options' to 'deny'.
> Uncaught DOMException: Blocked a frame with origin
> "http://latest1.example.com:8080"; from accessing a cross-origin frame.
> at Class.resizeFunction
> (http://latest1.example.com:8080/javascripts/app.js:237835:78)
> at http://latest1.example.com:8080/javascripts/app.js:237810:12
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23555) HBase fails to restart during upgrade to HDP 3.0 with Improperly specified VM option 'CMSInitiatingOccupancyFraction=' error
[ https://issues.apache.org/jira/browse/AMBARI-23555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-23555. Resolution: Fixed > HBase fails to restart during upgrade to HDP 3.0 with Improperly specified VM > option 'CMSInitiatingOccupancyFraction=' error > > > Key: AMBARI-23555 > URL: https://issues.apache.org/jira/browse/AMBARI-23555 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > > Improperly specified VM option 'CMSInitiatingOccupancyFraction=' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23447) Ambari Kafka unable to parse listeners value when added after kerberos is enabled.
[
https://issues.apache.org/jira/browse/AMBARI-23447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-23447.
Resolution: Fixed
> Ambari Kafka unable to parse listeners value when added after kerberos is
> enabled.
> --
>
> Key: AMBARI-23447
> URL: https://issues.apache.org/jira/browse/AMBARI-23447
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Fix For: 2.7.0
>
>
> Adding Kafka from Ambari after {{kerberos}} is enabled results an
> AmbariException with message "Circular reference found while replacing
> variables in...".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23459) ServiceAdvisor KeyError during kerberization of OneFS
[
https://issues.apache.org/jira/browse/AMBARI-23459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23459:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ServiceAdvisor KeyError during kerberization of OneFS
> -
>
> Key: AMBARI-23459
> URL: https://issues.apache.org/jira/browse/AMBARI-23459
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> Error message: Stack Advisor reported an error. Exit Code: 2. Error:
> KeyError: 'onefs'
> StdOut file: /var/run/ambari-server/stack-recommendations/5/stackadvisor.out
>
> StdErr file: /var/run/ambari-server/stack-recommendations/5/stackadvisor.err
>
> Stackadvisor.err shows the following traceback:
>
> 2018-04-03 16:09:09,711 ERROR HDP26StackAdvisor
> getCapacitySchedulerProperties: - Couldn't retrieve 'capacity-scheduler' from
> services.
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 167,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1565, in recommendConfigurations
> serviceAdvisor.getServiceConfigurationRecommendations(configurations,
> clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/2.6/services/ONEFS/service_advisor.py",
> line 112, in getServiceConfigurationRecommendations
> onefs_host = Uri.onefs(services)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/2.6/services/ONEFS/service_advisor.py",
> line 41, in onefs
> return self.from_config(configs, 'onefs', 'onefs_host')
> File
> "/var/lib/ambari-server/resources/stacks/HDP/2.6/services/ONEFS/service_advisor.py",
> line 45, in from_config
> return
> Uri(configs['configurations'][config_type]['properties'][property_name])
> KeyError: 'onefs'{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23603) Yarn queue manager when configured to use remote cluster shows the wrong user
Mastan Shaik created AMBARI-23603: - Summary: Yarn queue manager when configured to use remote cluster shows the wrong user Key: AMBARI-23603 URL: https://issues.apache.org/jira/browse/AMBARI-23603 Project: Ambari Issue Type: Bug Reporter: Mastan Shaik Steps to reproduce: 1) Configure capacity scheduler view to remote cluster. 2) Make changes to the capacity scheduler as a non admin user id. 3) save and refresh queues 4) Go to configuration changes in yarn. You will the changes have been made as user Admin instead of user logged in. This is fixed if we use local cluster instead of remote for the capacity scheduler view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23601) NN Federation Wizard: Format NameNode fails due to stopped NameNodes
[ https://issues.apache.org/jira/browse/AMBARI-23601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23601: Labels: pull-request-available (was: ) > NN Federation Wizard: Format NameNode fails due to stopped NameNodes > > > Key: AMBARI-23601 > URL: https://issues.apache.org/jira/browse/AMBARI-23601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > NameNodes are stopped in first step of the flow. This prevents _Format > NameNode_ step from getting clusterId of existing NameNodes. > NameNodes should be started, too, after JournalNodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23602) NN Federation Lower priority changes
[ https://issues.apache.org/jira/browse/AMBARI-23602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23602: Labels: pull-request-available (was: ) > NN Federation Lower priority changes > > > Key: AMBARI-23602 > URL: https://issues.apache.org/jira/browse/AMBARI-23602 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > - The add metric in the HDFS Metrics needs more padding around it > - Create metric - because of menu depth the name of the metric is hard to > see, we should wrap them and do anything to make sure the metric names are > easily readable > - In the move master wizard we need to add the namespace before the word > "NameNode", like "ns1 NameNode" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23602) NN Federation Lower priority changes
Andrii Babiichuk created AMBARI-23602: - Summary: NN Federation Lower priority changes Key: AMBARI-23602 URL: https://issues.apache.org/jira/browse/AMBARI-23602 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 - The add metric in the HDFS Metrics needs more padding around it - Create metric - because of menu depth the name of the metric is hard to see, we should wrap them and do anything to make sure the metric names are easily readable - In the move master wizard we need to add the namespace before the word "NameNode", like "ns1 NameNode" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23588) NN Federation Wizard Changes
[ https://issues.apache.org/jira/browse/AMBARI-23588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23588. -- Resolution: Resolved committed to trunk > NN Federation Wizard Changes > > > Key: AMBARI-23588 > URL: https://issues.apache.org/jira/browse/AMBARI-23588 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > There are a few required changes to the "Add New HDFS Namespace" wizard: > * Remove the "If you have HBase running" warning and replace it with a red > warning similar to what we have for move name node that says: "You should > plan a cluster maintenance window and prepare for cluster downtime when > adding a new HDFS Namespace as this Wizard will restart all services. > * During the wizard if you hit the Esc key you bounce completely out of the > wizard, is there anyway we can prompt the user to say are you sure you want > to exit this wizard if the user hits the Esc key? > * In the Configure Components step, we need to change the info text to: > "Please wait while your new HDFS Namespace is being deployed" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23601) NN Federation Wizard: Format NameNode fails due to stopped NameNodes
Aleksandr Kovalenko created AMBARI-23601: Summary: NN Federation Wizard: Format NameNode fails due to stopped NameNodes Key: AMBARI-23601 URL: https://issues.apache.org/jira/browse/AMBARI-23601 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 NameNodes are stopped in first step of the flow. This prevents _Format NameNode_ step from getting clusterId of existing NameNodes. NameNodes should be started, too, after JournalNodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23594) LZO Libraries Are Not Installed Correctly During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23594:
Labels: pull-request-available (was: )
> LZO Libraries Are Not Installed Correctly During Upgrade
>
>
> Key: AMBARI-23594
> URL: https://issues.apache.org/jira/browse/AMBARI-23594
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.6.1.5-3 and HDP version: 2.6.1.0-129
> # Upgrade Ambari to Target Version: 2.7.0.0-312, then upgrade AMS
> # Delete unsupported services like Flume, Falcon
> # Try Express Upgrade to HDP-3.0.0.0-1192
>
> *Result*
> Oozie server start failed
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 154, in
> OozieServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie.py",
> line 196, in oozie
> Execute(format('{sudo} cp {hadoop_lib_home}/hadoop-lzo*.jar
> {oozie_lib_dir}'),
> 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
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh cp /usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar
> /usr/hdp/current/oozie-server' returned 1. cp: cannot stat
> '/usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23600) cluster name validation issue in ADMIN view
[ https://issues.apache.org/jira/browse/AMBARI-23600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23600: Labels: pull-request-available (was: ) > cluster name validation issue in ADMIN view > --- > > Key: AMBARI-23600 > URL: https://issues.apache.org/jira/browse/AMBARI-23600 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Cluster name is limited to 100 characters. Need to remove all another UI > validation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23600) cluster name validation issue in ADMIN view
Antonenko Alexander created AMBARI-23600: Summary: cluster name validation issue in ADMIN view Key: AMBARI-23600 URL: https://issues.apache.org/jira/browse/AMBARI-23600 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 Cluster name is limited to 100 characters. Need to remove all another UI validation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23600) cluster name validation issue in ADMIN view
[ https://issues.apache.org/jira/browse/AMBARI-23600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23600: Assignee: Antonenko Alexander > cluster name validation issue in ADMIN view > --- > > Key: AMBARI-23600 > URL: https://issues.apache.org/jira/browse/AMBARI-23600 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.0 > > > Cluster name is limited to 100 characters. Need to remove all another UI > validation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations
[ https://issues.apache.org/jira/browse/AMBARI-23599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23599: - Status: Patch Available (was: Open) > It is hectic whether or not a setting a property attribute in the service > advisor gets into the recommendations > --- > > Key: AMBARI-23599 > URL: https://issues.apache.org/jira/browse/AMBARI-23599 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Expected behavior of the field "HA HSI namespace": > When the switch is off, it should not be visible. > When the switch is on, and 1 host is selected, it should not be visible. > When the switch is on, and 2 hosts are selected then it should be visible. > Experienced behavior: > At first it is not visible. If I select two hosts, it is still not visible, > though the service advisor sets the visibility attribute to true. When I > discard it, it is visible, as for some reason the service advisor sees that > there are two HSI hosts, though there are none, I've just discarded it. > I've added a message in the service advisor log starting "Setting the > visibily of hive.server2.active.passive.ha.registry.namespace to" to make it > easier to see what decision it made. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23598) Customize Services : update Druid and Superset themes
[ https://issues.apache.org/jira/browse/AMBARI-23598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23598. -- Resolution: Invalid > Customize Services : update Druid and Superset themes > - > > Key: AMBARI-23598 > URL: https://issues.apache.org/jira/browse/AMBARI-23598 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.7.0 > > > Update Superset and Druid themes to expose appropriate configs on Credentials > and Databases tabs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations
[ https://issues.apache.org/jira/browse/AMBARI-23599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23599: Labels: pull-request-available (was: ) > It is hectic whether or not a setting a property attribute in the service > advisor gets into the recommendations > --- > > Key: AMBARI-23599 > URL: https://issues.apache.org/jira/browse/AMBARI-23599 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Expected behavior of the field "HA HSI namespace": > When the switch is off, it should not be visible. > When the switch is on, and 1 host is selected, it should not be visible. > When the switch is on, and 2 hosts are selected then it should be visible. > Experienced behavior: > At first it is not visible. If I select two hosts, it is still not visible, > though the service advisor sets the visibility attribute to true. When I > discard it, it is visible, as for some reason the service advisor sees that > there are two HSI hosts, though there are none, I've just discarded it. > I've added a message in the service advisor log starting "Setting the > visibily of hive.server2.active.passive.ha.registry.namespace to" to make it > easier to see what decision it made. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations
[ https://issues.apache.org/jira/browse/AMBARI-23599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23599: Assignee: Antonenko Alexander > It is hectic whether or not a setting a property attribute in the service > advisor gets into the recommendations > --- > > Key: AMBARI-23599 > URL: https://issues.apache.org/jira/browse/AMBARI-23599 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.0 > > > Expected behavior of the field "HA HSI namespace": > When the switch is off, it should not be visible. > When the switch is on, and 1 host is selected, it should not be visible. > When the switch is on, and 2 hosts are selected then it should be visible. > Experienced behavior: > At first it is not visible. If I select two hosts, it is still not visible, > though the service advisor sets the visibility attribute to true. When I > discard it, it is visible, as for some reason the service advisor sees that > there are two HSI hosts, though there are none, I've just discarded it. > I've added a message in the service advisor log starting "Setting the > visibily of hive.server2.active.passive.ha.registry.namespace to" to make it > easier to see what decision it made. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations
Antonenko Alexander created AMBARI-23599: Summary: It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations Key: AMBARI-23599 URL: https://issues.apache.org/jira/browse/AMBARI-23599 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 Expected behavior of the field "HA HSI namespace": When the switch is off, it should not be visible. When the switch is on, and 1 host is selected, it should not be visible. When the switch is on, and 2 hosts are selected then it should be visible. Experienced behavior: At first it is not visible. If I select two hosts, it is still not visible, though the service advisor sets the visibility attribute to true. When I discard it, it is visible, as for some reason the service advisor sees that there are two HSI hosts, though there are none, I've just discarded it. I've added a message in the service advisor log starting "Setting the visibily of hive.server2.active.passive.ha.registry.namespace to" to make it easier to see what decision it made. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23598) Customize Services : update Druid and Superset themes
Aleksandr Kovalenko created AMBARI-23598: Summary: Customize Services : update Druid and Superset themes Key: AMBARI-23598 URL: https://issues.apache.org/jira/browse/AMBARI-23598 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Update Superset and Druid themes to expose appropriate configs on Credentials and Databases tabs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23597) Config's tags should be cached
Andrii Tkach created AMBARI-23597: - Summary: Config's tags should be cached Key: AMBARI-23597 URL: https://issues.apache.org/jira/browse/AMBARI-23597 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 UI often make calls to fetch current tags, which can be cached and updated on WebSocket event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23596) Ambari web should escape slash in config names
[ https://issues.apache.org/jira/browse/AMBARI-23596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23596: Labels: pull-request-available (was: ) > Ambari web should escape slash in config names > -- > > Key: AMBARI-23596 > URL: https://issues.apache.org/jira/browse/AMBARI-23596 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Should escape property's name "a/b" => "a\u002Fb". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23545) Remove livy2.pyspark3 interpreter
[ https://issues.apache.org/jira/browse/AMBARI-23545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi resolved AMBARI-23545. Resolution: Fixed > Remove livy2.pyspark3 interpreter > - > > Key: AMBARI-23545 > URL: https://issues.apache.org/jira/browse/AMBARI-23545 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.7.0 > > > Need to remove livy2.pyspark3 interpreter from Zeppelin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23596) Ambari web should escape slash in config names
Andrii Tkach created AMBARI-23596: - Summary: Ambari web should escape slash in config names Key: AMBARI-23596 URL: https://issues.apache.org/jira/browse/AMBARI-23596 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Should escape property's name "a/b" => "a\u002Fb". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23595) Ambari to replace HOSTGROUP variable in blueprints.
Balázs Bence Sári created AMBARI-23595: -- Summary: Ambari to replace HOSTGROUP variable in blueprints. Key: AMBARI-23595 URL: https://issues.apache.org/jira/browse/AMBARI-23595 Project: Ambari Issue Type: Bug Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári These variables are replaced with fqdn's in some cases and not in other cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23594) LZO Libraries Are Not Installed Correctly During Upgrade
Jonathan Hurley created AMBARI-23594:
Summary: LZO Libraries Are Not Installed Correctly During Upgrade
Key: AMBARI-23594
URL: https://issues.apache.org/jira/browse/AMBARI-23594
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.7.0
*STR*
# Deployed cluster with Ambari version: 2.6.1.5-3 and HDP version: 2.6.1.0-129
# Upgrade Ambari to Target Version: 2.7.0.0-312, then upgrade AMS
# Delete unsupported services like Flume, Falcon
# Try Express Upgrade to HDP-3.0.0.0-1192
*Result*
Oozie server start failed
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
line 154, in
OozieServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
line 70, in configure
oozie(is_server=True)
File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie.py",
line 196, in oozie
Execute(format('{sudo} cp {hadoop_lib_home}/hadoop-lzo*.jar
{oozie_lib_dir}'),
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 308,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'ambari-sudo.sh cp /usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar
/usr/hdp/current/oozie-server' returned 1. cp: cannot stat
'/usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar': No such file or directory
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23594) LZO Libraries Are Not Installed Correctly During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440792#comment-16440792
]
Jonathan Hurley commented on AMBARI-23594:
--
The RCA for this one is that we are trying to install the wrong LZO packages
during NameNode 3.0 startup:
{code}
2018-04-13 18:21:47,999 - Package['lzo'] {'retry_on_repo_unavailability': True,
'retry_count': 5}
2018-04-13 18:21:48,121 - Skipping installation of existing package lzo
2018-04-13 18:21:48,121 - Package['hadooplzo_2_6_1_0_129']
{'retry_on_repo_unavailability': True, 'retry_count': 5}
2018-04-13 18:21:48,136 - Skipping installation of existing package
hadooplzo_2_6_1_0_129
2018-04-13 18:21:48,137 - Package['hadooplzo_2_6_1_0_129-native']
{'retry_on_repo_unavailability': True, 'retry_count': 5}
2018-04-13 18:21:48,151 - Skipping installation of existing package
hadooplzo_2_6_1_0_129-native
{code}
Because we're sending down the wrong version here, we never install
{{hadooplzo_3_0_0_0_1192.x86_64}}.
{code}
hadooplzo.noarch : hadooplzo Distro virtual package
hadooplzo-native.noarch : hadooplzo-native Distro virtual package
hadooplzo_2_6_1_0_129.x86_64 : Hadoop-LZO is a project to bring splittable LZO
compression to Hadoop
hadooplzo_2_6_1_0_129-native.x86_64 : GPL Compression Libraries for Hadoop
(native)
hadooplzo_3_0_0_0_1192.x86_64 : Hadoop-LZO is a project to bring splittable LZO
compression to Hadoop
hadooplzo_3_0_0_0_1192-native.x86_64 : GPL Compression Libraries for Hadoop
(native)
{code}
This is an Ambari issue with how we generate commands for the upgrade. When
creating commands, we are populating a {{RepositoryFile}} which captures the
current state of the component's repository (2.6.1.0-129). When this runs
during the upgrade, the wrong {{RepositoryFile}} is being sent down. This is
why the version for installing LZO is incorrect.
In general, we shouldn't need to pre-populate {{ExecutionCommand}}s with
{{RepositoryFile}} since it can usually be taken at command-runtime. However,
there is one case where this is not so:
- During a stack's distribution
The core logic in Ambari states that when a command is about to run, we should
populate the {{repositoryFile}} IFF it's not already set on the command. Most
times, this is benign, but in the case of upgrades, it's a real problem.
As I see it, we have a couple of options here:
- Remove it from all execution/action command helpers
-- Rely on the {{ExecutionCommandWrapper}} to set it before the command is sent
-- Require that stack distribution code to ensure that they place it on there
instead of having the helpers do it
- Have the {{UpgradeResourceProvider}} strip it from all commands that it
generates
> LZO Libraries Are Not Installed Correctly During Upgrade
>
>
> Key: AMBARI-23594
> URL: https://issues.apache.org/jira/browse/AMBARI-23594
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.6.1.5-3 and HDP version: 2.6.1.0-129
> # Upgrade Ambari to Target Version: 2.7.0.0-312, then upgrade AMS
> # Delete unsupported services like Flume, Falcon
> # Try Express Upgrade to HDP-3.0.0.0-1192
>
> *Result*
> Oozie server start failed
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 154, in
> OozieServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie.py",
> line 196, in oozie
> Execute(format('{sudo} cp {hadoop_lib_home}/hadoop-lzo*.jar
> {oozie_lib_dir}'),
> 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
>
[jira] [Updated] (AMBARI-23594) LZO Libraries Are Not Installed Correctly During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-23594:
-
Reporter: Vivek Sharma (was: Jonathan Hurley)
> LZO Libraries Are Not Installed Correctly During Upgrade
>
>
> Key: AMBARI-23594
> URL: https://issues.apache.org/jira/browse/AMBARI-23594
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.6.1.5-3 and HDP version: 2.6.1.0-129
> # Upgrade Ambari to Target Version: 2.7.0.0-312, then upgrade AMS
> # Delete unsupported services like Flume, Falcon
> # Try Express Upgrade to HDP-3.0.0.0-1192
>
> *Result*
> Oozie server start failed
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 154, in
> OozieServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie.py",
> line 196, in oozie
> Execute(format('{sudo} cp {hadoop_lib_home}/hadoop-lzo*.jar
> {oozie_lib_dir}'),
> 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
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh cp /usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar
> /usr/hdp/current/oozie-server' returned 1. cp: cannot stat
> '/usr/hdp/3.0.0.0-1192/hadoop/lib/hadoop-lzo*.jar': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23593) Logsearch UI: Fix Log Feeder Config issues
[ https://issues.apache.org/jira/browse/AMBARI-23593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23593: Labels: pull-request-available (was: ) > Logsearch UI: Fix Log Feeder Config issues > -- > > Key: AMBARI-23593 > URL: https://issues.apache.org/jira/browse/AMBARI-23593 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > * Change the name of the parameters. > * Handle the server response correctly (it will return status 200 even if > the validation is failed, but it contains errorMessage property in this case) > * Fix the notifications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23593) Logsearch UI: Fix Log Feeder Config issues
[ https://issues.apache.org/jira/browse/AMBARI-23593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23593: --- Summary: Logsearch UI: Fix Log Feeder Config issues (was: Logsearch UI: Fix Log Feeder issues) > Logsearch UI: Fix Log Feeder Config issues > -- > > Key: AMBARI-23593 > URL: https://issues.apache.org/jira/browse/AMBARI-23593 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Fix For: 2.7.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > * Change the name of the parameters. > * Handle the server response correctly (it will return status 200 even if > the validation is failed, but it contains errorMessage property in this case) > * Fix the notifications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23593) Logsearch UI: Fix Log Feeder issues
Istvan Tobias created AMBARI-23593: -- Summary: Logsearch UI: Fix Log Feeder issues Key: AMBARI-23593 URL: https://issues.apache.org/jira/browse/AMBARI-23593 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Fix For: 2.7.0 * Change the name of the parameters. * Handle the server response correctly (it will return status 200 even if the validation is failed, but it contains errorMessage property in this case) * Fix the notifications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
