[jira] [Commented] (AMBARI-20354) Files View: In non-HA environment, Files view executes with error when "List of NameNodes" property is cleared
[
https://issues.apache.org/jira/browse/AMBARI-20354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906027#comment-15906027
]
Hadoop QA commented on AMBARI-20354:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857423/AMBARI-20354.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/utils.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10979//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10979//console
This message is automatically generated.
> Files View: In non-HA environment, Files view executes with error when "List
> of NameNodes" property is cleared
> --
>
> Key: AMBARI-20354
> URL: https://issues.apache.org/jira/browse/AMBARI-20354
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-20354.patch
>
>
> 1. In a multi-node cluster where namenode HA is not enabled, create a Files
> View. Select Custom Configuration and enter the WebHDFS FileSystem URI*. In
> the "List of NameNodes", enter the namenode information. Save and execute
> view. There are no errors.
> 2. Edit the view and delete the values entered in the "List of NameNodes"
> field. Save and execute the view.
> The following error is thrown although Namenode HA is not enabled.
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20403) Yarn Container metrics are not being collected by AMS
[
https://issues.apache.org/jira/browse/AMBARI-20403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906013#comment-15906013
]
Hadoop QA commented on AMBARI-20403:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857433/AMBARI-20403.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-common ambari-metrics/ambari-metrics-hadoop-sink
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10978//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10978//console
This message is automatically generated.
> Yarn Container metrics are not being collected by AMS
> --
>
> Key: AMBARI-20403
> URL: https://issues.apache.org/jira/browse/AMBARI-20403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20403.patch
>
>
> Exception in NM logs :
> {code:java}
> 2017-03-07 19:14:06,143 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(197)) - Unable to connect
> to collector, null
> This exceptions will be ignored for next 100 times
>
> 2017-03-07 19:14:06,144 WARN timeline.HadoopTimelineMetricsSink
> (HadoopTimelineMetricsSink.java:putMetrics(344)) - Unable to send metrics to
> collector by address:null
> {code}
> 0jdbc:phoenix:localhost:2181:/ams-hbase-uns> select * from CONTAINER_METRICS
> order by START_TIME desc limit 10;
> ++--++-++++---+-+--+---+
> | APP_ID | CONTAINER_ID | START_TIME | FINISH_TIME | DURATION |
> HOSTNAME | EXIT_CODE | LOCALIZATION_DURATION | LAUNCH_DURATION |
> MEM_REQUESTED_GB | MEM_REQUESTED_GB_ |
> ++--++-++++---+-+--+---+
> ++--++-++++---+-+--+---+
> No rows selected (0.505 seconds)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20401: - Resolution: Fixed Status: Resolved (was: Patch Available) > HOU wizard wrongly shows hosts with only client components at the start of > 'Upgrade Hosts' group > > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20401.patch > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5 (cluster topology is: 2 hosts with > only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that > host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only > client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All > Hosts' group, there is already an entry for 'Stop on > bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal > does not have any master/slave components it is already considered that > components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even > though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20399) [Upgrade] Unable to enable Credential store support on upgraded clusters
[ https://issues.apache.org/jira/browse/AMBARI-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20399: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > [Upgrade] Unable to enable Credential store support on upgraded clusters > > > Key: AMBARI-20399 > URL: https://issues.apache.org/jira/browse/AMBARI-20399 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20399.patch > > > During a stack upgrade, the ServiceInfo does not get refreshed. Due to this, > the credential_store_supported flag is set to false when the expected value > is true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20401: - Description: # Deploy HDP-2.5.3 cluster with Ambari-2.5 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. Thanks to [~shavi71] for finding this... was: # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. Thanks to [~shavi71] for finding this... > HOU wizard wrongly shows hosts with only client components at the start of > 'Upgrade Hosts' group > > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20401.patch > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5 (cluster topology is: 2 hosts with > only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that > host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only > client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All > Hosts' group, there is already an entry for 'Stop on > bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal > does not have any master/slave components it is already considered that > components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even > though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20405: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20405.patch > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905948#comment-15905948 ] Jaimin Jetly commented on AMBARI-20405: --- +1 for the patch > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20405.patch > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20404) Enhance error message for invalid chars in properties/values
[
https://issues.apache.org/jira/browse/AMBARI-20404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yesha Vora updated AMBARI-20404:
Description:
Scenario:
* Added below configs to spark2 default
{code}
spark.io.encryption.enabled = true
spark.io.encryption.keySizeBits = 128
spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
* Restart affected services.
Spark2-client is failing to restart with below error.
{code:title=stderr}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 60, in
SparkClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 721, in restart
self.install(env)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 36, in install
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 42, in configure
setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
line 56, in setup_spark
mode=0644
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py",
line 54, in action_create
mode = self.resource.mode
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 123, in action_create
content = self._get_content()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 160, in _get_content
return content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 52, in __call__
return self.get_content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 143, in get_content
rendered = self.template.render(self.context)
File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
891, in render
return self.environment.handle_exception(exc_info, True)
File "", line 3, in top-level template code
UnicodeEncodeError: 'ascii' codec can't encode character u'\u200b' in position
8: ordinal not in range(128)
{code}
Here, While copy-pasting properties, <200b> was appended with HmacSHA1. I
believe the error message should be more clear and specific on which
property/value has unwanted chars.
Can this validation move while saving configs ?
was:
Scenario:
* Added below configs to spark2 default
{code}
spark.io.encryption.enabled = true
spark.io.encryption.keySizeBits = 128
spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
* Restart affected services.
Spark2-client is failing to restart with below error.
{code:title=stderr}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 60, in
SparkClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 721, in restart
self.install(env)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 36, in install
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 42, in configure
setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
[jira] [Updated] (AMBARI-20404) Enhance error message for invalid chars in properties/values
[
https://issues.apache.org/jira/browse/AMBARI-20404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yesha Vora updated AMBARI-20404:
Summary: Enhance error message for invalid chars in properties/values
(was: Restart of Spark2-client fails at setup_spark())
> Enhance error message for invalid chars in properties/values
>
>
> Key: AMBARI-20404
> URL: https://issues.apache.org/jira/browse/AMBARI-20404
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>
> Scenario:
> * Added below configs to spark2 default
> {code}
> spark.io.encryption.enabled = true
> spark.io.encryption.keySizeBits = 128
> spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
> * Restart affected services.
> Spark2-client is failing to restart with below error.
> {code:title=stderr}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 60, in
> SparkClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 313, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 721, in restart
> self.install(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 36, in install
> self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 116, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 42, in configure
> setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
> line 56, in setup_spark
> mode=0644
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py",
> line 54, in action_create
> mode = self.resource.mode
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 123, in action_create
> content = self._get_content()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 160, in _get_content
> return content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 52, in __call__
> return self.get_content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 143, in get_content
> rendered = self.template.render(self.context)
> File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
> 891, in render
> return self.environment.handle_exception(exc_info, True)
> File "", line 3, in top-level template code
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u200b' in
> position 8: ordinal not in range(128)
> {code}
> Here, While copy-pasting properties, <200b> was appended with HmacSHA1. I
> believe the error message should be more cleaner and specific on which
> property/value has unwanted chars.
> Can this validation move while saving configs ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20404) Restart of Spark2-client fails at setup_spark()
[
https://issues.apache.org/jira/browse/AMBARI-20404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yesha Vora updated AMBARI-20404:
Description:
Scenario:
* Added below configs to spark2 default
{code}
spark.io.encryption.enabled = true
spark.io.encryption.keySizeBits = 128
spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
* Restart affected services.
Spark2-client is failing to restart with below error.
{code:title=stderr}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 60, in
SparkClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 721, in restart
self.install(env)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 36, in install
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 42, in configure
setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
line 56, in setup_spark
mode=0644
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py",
line 54, in action_create
mode = self.resource.mode
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 123, in action_create
content = self._get_content()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 160, in _get_content
return content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 52, in __call__
return self.get_content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 143, in get_content
rendered = self.template.render(self.context)
File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
891, in render
return self.environment.handle_exception(exc_info, True)
File "", line 3, in top-level template code
UnicodeEncodeError: 'ascii' codec can't encode character u'\u200b' in position
8: ordinal not in range(128)
{code}
Here, While copy-pasting properties, <200b> was appended with HmacSHA1. I
believe the error message should be more cleaner and specific on which
property/value has unwanted chars.
Can this validation move while saving configs ?
was:
Scenario:
* Added below configs to spark2 default
{code}
spark.io.encryption.enabled = true
spark.io.encryption.keySizeBits = 128
spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
* Restart affected services.
Spark2-client is failing to restart with below error.
{code:title=stderr}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 60, in
SparkClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 721, in restart
self.install(env)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 36, in install
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 42, in configure
setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
[jira] [Commented] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[
https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905940#comment-15905940
]
Hadoop QA commented on AMBARI-20401:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857416/AMBARI-20401.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10977//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10977//console
This message is automatically generated.
> HOU wizard wrongly shows hosts with only client components at the start of
> 'Upgrade Hosts' group
>
>
> Key: AMBARI-20401
> URL: https://issues.apache.org/jira/browse/AMBARI-20401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20401.patch
>
>
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts
> with only masters, 2 hosts with only slaves, 1 host with only clients)
> # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that
> host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only
> client components)
> In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All
> Hosts' group, there is already an entry for 'Stop on
> bugbash-cluster-2-2.openstacklocal'
> Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal
> does not have any master/slave components it is already considered that
> components are stopped on this host and the entry shows up in wizard.
> Likewise From API, I checked that the Upgrade item appears as COMPLETED, even
> though earlier Upgrades items are still Pending.
> Thanks to [~shavi71] for finding this...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905929#comment-15905929 ] Xi Wang commented on AMBARI-20405: -- 20559 passing (27s) 153 pending > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20405.patch > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20405: - Status: Patch Available (was: Open) > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20405.patch > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20405: - Attachment: AMBARI-20405.patch > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20405.patch > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20405) Side Nav: several issues tested on IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20405: - Fix Version/s: 3.0.0 > Side Nav: several issues tested on IE 11 > - > > Key: AMBARI-20405 > URL: https://issues.apache.org/jira/browse/AMBARI-20405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > CSS: > 1. Active item should have a green triangle at left. Now there was no active > effect for menu items except for Admin's submenu. > 2. Hovering on Services, service actions icon is invisible. Cannot trigger > any service actions. > 3. The scrollbar was too prominent, should hide scrollbar on every browser. > JS: > 4. Click on Services/Admin menu, no collapse effect. And will go to > Service/Admin page. > 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi > menu. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20405) Side Nav: several issues tested on IE 11
Xi Wang created AMBARI-20405: Summary: Side Nav: several issues tested on IE 11 Key: AMBARI-20405 URL: https://issues.apache.org/jira/browse/AMBARI-20405 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang CSS: 1. Active item should have a green triangle at left. Now there was no active effect for menu items except for Admin's submenu. 2. Hovering on Services, service actions icon is invisible. Cannot trigger any service actions. 3. The scrollbar was too prominent, should hide scrollbar on every browser. JS: 4. Click on Services/Admin menu, no collapse effect. And will go to Service/Admin page. 5. Click on "<<" at the footer, no collapse effect. Cannot collapse side navi menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20403) Yarn Container metrics are not being collected by AMS
[
https://issues.apache.org/jira/browse/AMBARI-20403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-20403:
---
Status: Patch Available (was: Open)
> Yarn Container metrics are not being collected by AMS
> --
>
> Key: AMBARI-20403
> URL: https://issues.apache.org/jira/browse/AMBARI-20403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20403.patch
>
>
> Exception in NM logs :
> {code:java}
> 2017-03-07 19:14:06,143 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(197)) - Unable to connect
> to collector, null
> This exceptions will be ignored for next 100 times
>
> 2017-03-07 19:14:06,144 WARN timeline.HadoopTimelineMetricsSink
> (HadoopTimelineMetricsSink.java:putMetrics(344)) - Unable to send metrics to
> collector by address:null
> {code}
> 0jdbc:phoenix:localhost:2181:/ams-hbase-uns> select * from CONTAINER_METRICS
> order by START_TIME desc limit 10;
> ++--++-++++---+-+--+---+
> | APP_ID | CONTAINER_ID | START_TIME | FINISH_TIME | DURATION |
> HOSTNAME | EXIT_CODE | LOCALIZATION_DURATION | LAUNCH_DURATION |
> MEM_REQUESTED_GB | MEM_REQUESTED_GB_ |
> ++--++-++++---+-+--+---+
> ++--++-++++---+-+--+---+
> No rows selected (0.505 seconds)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[
https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905895#comment-15905895
]
Hadoop QA commented on AMBARI-20386:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857417/AMBARI-20386.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10976//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10976//console
This message is automatically generated.
> Kerberos principal creation fails during blueprint install when kdc_hosts is
> not specified in blueprint
> ---
>
> Key: AMBARI-20386
> URL: https://issues.apache.org/jira/browse/AMBARI-20386
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20386.patch
>
>
> Blueprint validation does not prompt if kdc_hosts is not specified in the
> blueprint. After service installation, deployment fails during Create
> Principal stage. As /etc/krb5.conf is overwritten with blank values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20404) Restart of Spark2-client fails at setup_spark()
Yesha Vora created AMBARI-20404:
---
Summary: Restart of Spark2-client fails at setup_spark()
Key: AMBARI-20404
URL: https://issues.apache.org/jira/browse/AMBARI-20404
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Yesha Vora
Scenario:
* Added below configs to spark2 default
{code}
spark.io.encryption.enabled = true
spark.io.encryption.keySizeBits = 128
spark.io.encryption.keygen.algorithm = HmacSHA1 {code}
* Restart affected services.
Spark2-client is failing to restart with below error.
{code:title=stderr}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 60, in
SparkClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 721, in restart
self.install(env)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 36, in install
self.configure(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 116, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
line 42, in configure
setup_spark(env, 'client', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py",
line 56, in setup_spark
mode=0644
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py",
line 54, in action_create
mode = self.resource.mode
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 123, in action_create
content = self._get_content()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 160, in _get_content
return content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 52, in __call__
return self.get_content()
File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
line 143, in get_content
rendered = self.template.render(self.context)
File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
891, in render
return self.environment.handle_exception(exc_info, True)
File "", line 3, in top-level template code
UnicodeEncodeError: 'ascii' codec can't encode character u'\u200b' in position
8: ordinal not in range(128)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20403) Yarn Container metrics are not being collected by AMS
[
https://issues.apache.org/jira/browse/AMBARI-20403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905887#comment-15905887
]
Aravindan Vijayan commented on AMBARI-20403:
PROBLEM
The collector URI used for yarn container metrics is initially seeded and not
refreshed based on collector availability (HA changes). A couple of other
places where the Container metrics URL was wrongly invoked.
FIX
Changed container metrics path to use collector host HA changes.
> Yarn Container metrics are not being collected by AMS
> --
>
> Key: AMBARI-20403
> URL: https://issues.apache.org/jira/browse/AMBARI-20403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20403.patch
>
>
> Exception in NM logs :
> {code:java}
> 2017-03-07 19:14:06,143 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(197)) - Unable to connect
> to collector, null
> This exceptions will be ignored for next 100 times
>
> 2017-03-07 19:14:06,144 WARN timeline.HadoopTimelineMetricsSink
> (HadoopTimelineMetricsSink.java:putMetrics(344)) - Unable to send metrics to
> collector by address:null
> {code}
> 0jdbc:phoenix:localhost:2181:/ams-hbase-uns> select * from CONTAINER_METRICS
> order by START_TIME desc limit 10;
> ++--++-++++---+-+--+---+
> | APP_ID | CONTAINER_ID | START_TIME | FINISH_TIME | DURATION |
> HOSTNAME | EXIT_CODE | LOCALIZATION_DURATION | LAUNCH_DURATION |
> MEM_REQUESTED_GB | MEM_REQUESTED_GB_ |
> ++--++-++++---+-+--+---+
> ++--++-++++---+-+--+---+
> No rows selected (0.505 seconds)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20403) Yarn Container metrics are not being collected by AMS
[
https://issues.apache.org/jira/browse/AMBARI-20403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-20403:
---
Attachment: AMBARI-20403.patch
> Yarn Container metrics are not being collected by AMS
> --
>
> Key: AMBARI-20403
> URL: https://issues.apache.org/jira/browse/AMBARI-20403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20403.patch
>
>
> Exception in NM logs :
> {code:java}
> 2017-03-07 19:14:06,143 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(197)) - Unable to connect
> to collector, null
> This exceptions will be ignored for next 100 times
>
> 2017-03-07 19:14:06,144 WARN timeline.HadoopTimelineMetricsSink
> (HadoopTimelineMetricsSink.java:putMetrics(344)) - Unable to send metrics to
> collector by address:null
> {code}
> 0jdbc:phoenix:localhost:2181:/ams-hbase-uns> select * from CONTAINER_METRICS
> order by START_TIME desc limit 10;
> ++--++-++++---+-+--+---+
> | APP_ID | CONTAINER_ID | START_TIME | FINISH_TIME | DURATION |
> HOSTNAME | EXIT_CODE | LOCALIZATION_DURATION | LAUNCH_DURATION |
> MEM_REQUESTED_GB | MEM_REQUESTED_GB_ |
> ++--++-++++---+-+--+---+
> ++--++-++++---+-+--+---+
> No rows selected (0.505 seconds)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20403) Yarn Container metrics are not being collected by AMS
Aravindan Vijayan created AMBARI-20403:
--
Summary: Yarn Container metrics are not being collected by AMS
Key: AMBARI-20403
URL: https://issues.apache.org/jira/browse/AMBARI-20403
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
Fix For: 2.5.0
Exception in NM logs :
{code:java}
2017-03-07 19:14:06,143 INFO timeline.HadoopTimelineMetricsSink
(AbstractTimelineMetricsSink.java:emitMetricsJson(197)) - Unable to connect to
collector, null
This exceptions will be ignored for next 100 times
2017-03-07 19:14:06,144 WARN timeline.HadoopTimelineMetricsSink
(HadoopTimelineMetricsSink.java:putMetrics(344)) - Unable to send metrics to
collector by address:null
{code}
0jdbc:phoenix:localhost:2181:/ams-hbase-uns> select * from CONTAINER_METRICS
order by START_TIME desc limit 10;
++--++-++++---+-+--+---+
| APP_ID | CONTAINER_ID | START_TIME | FINISH_TIME | DURATION | HOSTNAME
| EXIT_CODE | LOCALIZATION_DURATION | LAUNCH_DURATION | MEM_REQUESTED_GB |
MEM_REQUESTED_GB_ |
++--++-++++---+-+--+---+
++--++-++++---+-+--+---+
No rows selected (0.505 seconds)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[
https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905861#comment-15905861
]
Hadoop QA commented on AMBARI-20402:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857419/AMBARI-20402.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10975//console
This message is automatically generated.
> Assign Slaves and Clients page displays incorrect configuration unless a
> change is made in Assign Masters page
> --
>
> Key: AMBARI-20402
> URL: https://issues.apache.org/jira/browse/AMBARI-20402
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-20402.patch,
> AssignSlavesAndClients_AfterChanges.jpg,
> AssignSlavesAndClients_BeforeChanges.jpg
>
>
> 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install
> wizard.
> 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients).
> 3. The recommended configuration does not seem to be place the components
> well. For e.g., DataNodes are recommended on all 5 nodes. (see
> AssignSlavesAndClients_BeforeChanges.jpg).
> 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the
> Atlas Metadata Server to a different host. Next, change it back to the
> original host so that in effect nothing has changed.
> 5. Now move to Step 6 again and see that the configuration has changed and
> seems more in line with best practices although effectively nothing has
> changed in the Assign Masters page. (see
> AssignSlavesAndClients_AfterChanges.jpg)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20399) [Upgrade] Unable to enable Credential store support on upgraded clusters
[
https://issues.apache.org/jira/browse/AMBARI-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905860#comment-15905860
]
Hadoop QA commented on AMBARI-20399:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857369/AMBARI-20399.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10974//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10974//console
This message is automatically generated.
> [Upgrade] Unable to enable Credential store support on upgraded clusters
>
>
> Key: AMBARI-20399
> URL: https://issues.apache.org/jira/browse/AMBARI-20399
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-20399.patch
>
>
> During a stack upgrade, the ServiceInfo does not get refreshed. Due to this,
> the credential_store_supported flag is set to false when the expected value
> is true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20354) Files View: In non-HA environment, Files view executes with error when "List of NameNodes" property is cleared
[ https://issues.apache.org/jira/browse/AMBARI-20354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20354: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > Files View: In non-HA environment, Files view executes with error when "List > of NameNodes" property is cleared > -- > > Key: AMBARI-20354 > URL: https://issues.apache.org/jira/browse/AMBARI-20354 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-20354.patch > > > 1. In a multi-node cluster where namenode HA is not enabled, create a Files > View. Select Custom Configuration and enter the WebHDFS FileSystem URI*. In > the "List of NameNodes", enter the namenode information. Save and execute > view. There are no errors. > 2. Edit the view and delete the values entered in the "List of NameNodes" > field. Save and execute the view. > The following error is thrown although Namenode HA is not enabled. > Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes > count is not exactly 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20354) Files View: In non-HA environment, Files view executes with error when "List of NameNodes" property is cleared
[ https://issues.apache.org/jira/browse/AMBARI-20354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20354: Attachment: AMBARI-20354.patch > Files View: In non-HA environment, Files view executes with error when "List > of NameNodes" property is cleared > -- > > Key: AMBARI-20354 > URL: https://issues.apache.org/jira/browse/AMBARI-20354 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-20354.patch > > > 1. In a multi-node cluster where namenode HA is not enabled, create a Files > View. Select Custom Configuration and enter the WebHDFS FileSystem URI*. In > the "List of NameNodes", enter the namenode information. Save and execute > view. There are no errors. > 2. Edit the view and delete the values entered in the "List of NameNodes" > field. Save and execute the view. > The following error is thrown although Namenode HA is not enabled. > Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes > count is not exactly 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905803#comment-15905803
]
Hadoop QA commented on AMBARI-20378:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857379/AMBARI-20378.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-logfeeder ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10973//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10973//console
This message is automatically generated.
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at logfeeder.properties (global setting). For example (the
> values below are the defaults):
> {code:java}
> logfeeder.cache.enabled=false
> logfeeder.cache.size=100
> logfeeder.cache.key.field=log_message
> logfeeder.cache.dedup.interval=1000
> logfeeder.cache.last.dedup.enabled=false
> {code}
> can be overriden in input config block (per monitored file)
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Attachment: AMBARI-20402.patch > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20386: --- Status: Patch Available (was: In Progress) > Kerberos principal creation fails during blueprint install when kdc_hosts is > not specified in blueprint > --- > > Key: AMBARI-20386 > URL: https://issues.apache.org/jira/browse/AMBARI-20386 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20386.patch > > > Blueprint validation does not prompt if kdc_hosts is not specified in the > blueprint. After service installation, deployment fails during Create > Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20386: --- Attachment: AMBARI-20386.patch > Kerberos principal creation fails during blueprint install when kdc_hosts is > not specified in blueprint > --- > > Key: AMBARI-20386 > URL: https://issues.apache.org/jira/browse/AMBARI-20386 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20386.patch > > > Blueprint validation does not prompt if kdc_hosts is not specified in the > blueprint. After service installation, deployment fails during Create > Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20386: --- Attachment: (was: AMBARI-20386.patch) > Kerberos principal creation fails during blueprint install when kdc_hosts is > not specified in blueprint > --- > > Key: AMBARI-20386 > URL: https://issues.apache.org/jira/browse/AMBARI-20386 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Blueprint validation does not prompt if kdc_hosts is not specified in the > blueprint. After service installation, deployment fails during Create > Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20401: - Attachment: AMBARI-20401.patch > HOU wizard wrongly shows hosts with only client components at the start of > 'Upgrade Hosts' group > > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20401.patch > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts > with only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that > host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only > client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All > Hosts' group, there is already an entry for 'Stop on > bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal > does not have any master/slave components it is already considered that > components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even > though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20401: - Status: Patch Available (was: Open) > HOU wizard wrongly shows hosts with only client components at the start of > 'Upgrade Hosts' group > > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts > with only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that > host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only > client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All > Hosts' group, there is already an entry for 'Stop on > bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal > does not have any master/slave components it is already considered that > components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even > though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905786#comment-15905786 ] Eugene Chekanskiy commented on AMBARI-20323: addendum patch in 0bd7b86..290218f branch-2.5 -> branch-2.5 0471b0c..b69ac43 trunk -> trunk > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.addendum.patch, > AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Attachment: AMBARI-20323.addendum.patch > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.addendum.patch, > AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Attachment: AssignSlavesAndClients_BeforeChanges.jpg AssignSlavesAndClients_AfterChanges.jpg > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
Sangeeta Ravindran created AMBARI-20402: --- Summary: Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page Key: AMBARI-20402 URL: https://issues.apache.org/jira/browse/AMBARI-20402 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Attachments: AssignSlavesAndClients_AfterChanges.jpg, AssignSlavesAndClients_BeforeChanges.jpg 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install wizard. 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). 3. The recommended configuration does not seem to be place the components well. For e.g., DataNodes are recommended on all 5 nodes. (see AssignSlavesAndClients_BeforeChanges.jpg). 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the Atlas Metadata Server to a different host. Next, change it back to the original host so that in effect nothing has changed. 5. Now move to Step 6 again and see that the configuration has changed and seems more in line with best practices although effectively nothing has changed in the Assign Masters page. (see AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[
https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905776#comment-15905776
]
Jonathan Hurley commented on AMBARI-20401:
--
- There is a bug deep in the ambari orchestration logic which causes a request
to hang in a {{PENDING}} state if the stage numbers are not directly sequential
(ie 1, 2, 3 vs 1, 3)
- HOU is exposing this bug by trying to schedule a stage with no tasks (which
is wrong anyway)
It's way to dangerous to fix the first problem. The 2nd problem is now fixed
and I'm putting it up for review. Therefore, I think this bug should remain
scoped for 2.5.0.1 and I can open a new bug for 2.5.1 for the deeper issue.
> HOU wizard wrongly shows hosts with only client components at the start of
> 'Upgrade Hosts' group
>
>
> Key: AMBARI-20401
> URL: https://issues.apache.org/jira/browse/AMBARI-20401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts
> with only masters, 2 hosts with only slaves, 1 host with only clients)
> # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that
> host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only
> client components)
> In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All
> Hosts' group, there is already an entry for 'Stop on
> bugbash-cluster-2-2.openstacklocal'
> Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal
> does not have any master/slave components it is already considered that
> components are stopped on this host and the entry shows up in wizard.
> Likewise From API, I checked that the Upgrade item appears as COMPLETED, even
> though earlier Upgrades items are still Pending.
> Thanks to [~shavi71] for finding this...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[
https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905776#comment-15905776
]
Jonathan Hurley edited comment on AMBARI-20401 at 3/10/17 10:08 PM:
- There is a bug deep in the ambari orchestration logic which causes a request
to hang in a {{PENDING}} state if the stage numbers are not directly sequential
(ie 1, 2, 3 vs 1, 3)
- HOU is exposing this bug by trying to schedule a stage with no tasks (which
is wrong anyway)
It's way to dangerous to fix the first problem. The 2nd problem is now fixed
and I'm putting it up for review. Therefore, I think this bug should remain
scoped for 2.5.0 and I can open a new bug for 2.5.1 for the deeper issue.
was (Author: jonathan.hurley):
- There is a bug deep in the ambari orchestration logic which causes a request
to hang in a {{PENDING}} state if the stage numbers are not directly sequential
(ie 1, 2, 3 vs 1, 3)
- HOU is exposing this bug by trying to schedule a stage with no tasks (which
is wrong anyway)
It's way to dangerous to fix the first problem. The 2nd problem is now fixed
and I'm putting it up for review. Therefore, I think this bug should remain
scoped for 2.5.0.1 and I can open a new bug for 2.5.1 for the deeper issue.
> HOU wizard wrongly shows hosts with only client components at the start of
> 'Upgrade Hosts' group
>
>
> Key: AMBARI-20401
> URL: https://issues.apache.org/jira/browse/AMBARI-20401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts
> with only masters, 2 hosts with only slaves, 1 host with only clients)
> # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that
> host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only
> client components)
> In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All
> Hosts' group, there is already an entry for 'Stop on
> bugbash-cluster-2-2.openstacklocal'
> Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal
> does not have any master/slave components it is already considered that
> components are stopped on this host and the entry shows up in wizard.
> Likewise From API, I checked that the Upgrade item appears as COMPLETED, even
> though earlier Upgrades items are still Pending.
> Thanks to [~shavi71] for finding this...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
[ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20401: - Description: # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. Thanks to [~shavi71] for finding this... was: *STR* # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. > HOU wizard wrongly shows hosts with only client components at the start of > 'Upgrade Hosts' group > > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts > with only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that > host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only > client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All > Hosts' group, there is already an entry for 'Stop on > bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal > does not have any master/slave components it is already considered that > components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even > though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
Jonathan Hurley created AMBARI-20401: Summary: HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group Key: AMBARI-20401 URL: https://issues.apache.org/jira/browse/AMBARI-20401 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Critical Fix For: 2.5.0 *STR* # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[
https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905767#comment-15905767
]
Hadoop QA commented on AMBARI-20400:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857385/AMBARI-20400.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10972//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10972//console
This message is automatically generated.
> Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not
> installed on the cluster
>
>
> Key: AMBARI-20400
> URL: https://issues.apache.org/jira/browse/AMBARI-20400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20400.patch
>
>
> It's possible to install a cluster without Tez and Slider via blueprint. In
> this case, Yarn historyserver start logic prints two warnings about unable to
> copy tez and slider tar ball to HDFS.
> Yarn history server should skip the copy hdfs tar ball logic for tez and
> slider if they are not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20243: - Resolution: Fixed Status: Resolved (was: Patch Available) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch, > AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905662#comment-15905662
]
Olivér Szabó commented on AMBARI-20382:
---
committed to trunk:
{code:java}
commit e6fc6f47b9cf0eed4b7ac25b011a8aa7876cad7a
Author: oleewere
Date: Fri Mar 10 21:09:46 2017 +0100
AMBARI-20382. Appendum - Log Search: Web UI Alert tries to use http
protocol even if ssl is enabled (oleewere)
{code}
committed to branch-2.5:
{code:java}
commit 0bd7b864317606952a7a03a163a3b4102e5f2964
Author: oleewere
Date: Fri Mar 10 21:09:46 2017 +0100
AMBARI-20382. Appendum - Log Search: Web UI Alert tries to use http
protocol even if ssl is enabled (oleewere)
{code}
> Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
> --
>
> Key: AMBARI-20382
> URL: https://issues.apache.org/jira/browse/AMBARI-20382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-20382-appendum.patch,
> AMBARI-20382-branch-2.5-appendum.patch, AMBARI-20382.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
[ https://issues.apache.org/jira/browse/AMBARI-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20382: -- Attachment: AMBARI-20382-branch-2.5-appendum.patch > Log Search: Web UI Alert tries to use http protocol even if ssl is enabled > -- > > Key: AMBARI-20382 > URL: https://issues.apache.org/jira/browse/AMBARI-20382 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20382-appendum.patch, > AMBARI-20382-branch-2.5-appendum.patch, AMBARI-20382.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Fix Version/s: trunk > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Status: Patch Available (was: Open) > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Affects Version/s: trunk > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Component/s: ambari-server > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Attachment: AMBARI-20400.patch > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li reassigned AMBARI-20400: -- Assignee: Di Li > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug >Reporter: Di Li >Assignee: Di Li > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
Di Li created AMBARI-20400: -- Summary: Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster Key: AMBARI-20400 URL: https://issues.apache.org/jira/browse/AMBARI-20400 Project: Ambari Issue Type: Bug Reporter: Di Li It's possible to install a cluster without Tez and Slider via blueprint. In this case, Yarn historyserver start logic prints two warnings about unable to copy tez and slider tar ball to HDFS. Yarn history server should skip the copy hdfs tar ball logic for tez and slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Description:
Add de-duplication support to logfeeder.
For handling duplications, it will be an LRU cache for every input.
It can be set up at logfeeder.properties (global setting). For example (the
values below are the defaults):
{code:java}
logfeeder.cache.enabled=false
logfeeder.cache.size=100
logfeeder.cache.key.field=log_message
logfeeder.cache.dedup.interval=1000
logfeeder.cache.last.dedup.enabled=false
{code}
can be overriden in input config block (per monitored file)
{code:java}
{
"input": [
{
...
"cache_enabled" : "true",
"cache_size" : "100",
"cache_dedup_interval" : "1000",
"cache_last_dedup_enabled" : "false",
"cache_key_field" : "log_message"
}
] ...
{code}
{{cache_dedup_interval}} : if the interval (timestamp - date difference) is not
reached between 2 log messages (same content), then the new log will be
dropped.
{{cache_last_dedup_enabled}}: if its enabled and the new log message is the
same as the last one, the new log will be dropped. (dedup interval wont have
impact on that feature)
{{cache_key_field}} : field of the log message which will be compared and
stored in the cache (as keys)
was:
Add de-duplication support to logfeeder.
For handling duplications, it will be an LRU cache for every input.
It can be set up at logfeeder.properties. For example (the values below are the
defaults):
{code:java}
logfeeder.cache.enabled=false
logfeeder.cache.size=100
logfeeder.cache.key.field=log_message
logfeeder.cache.dedup.interval=1000
logfeeder.cache.last.dedup.enabled=false
{code}
can be overriden in input config block (per monitored file)
{code:java}
{
"input": [
{
...
"cache_enabled" : "true",
"cache_size" : "100",
"cache_dedup_interval" : "1000",
"cache_last_dedup_enabled" : "false",
"cache_key_field" : "log_message"
}
] ...
{code}
{{cache_dedup_interval}} : if the interval (timestamp - date difference) is not
reached between 2 log messages (same content), then the new log will be
dropped.
{{cache_last_dedup_enabled}}: if its enabled and the new log message is the
same as the last one, the new log will be dropped. (dedup interval wont have
impact on that feature)
{{cache_key_field}} : field of the log message which will be compared and
stored in the cache (as keys)
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at logfeeder.properties (global setting). For example (the
> values below are the defaults):
> {code:java}
> logfeeder.cache.enabled=false
> logfeeder.cache.size=100
> logfeeder.cache.key.field=log_message
> logfeeder.cache.dedup.interval=1000
> logfeeder.cache.last.dedup.enabled=false
> {code}
> can be overriden in input config block (per monitored file)
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Attachment: (was: AMBARI-20378.patch)
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at logfeeder.properties (global setting). For example (the
> values below are the defaults):
> {code:java}
> logfeeder.cache.enabled=false
> logfeeder.cache.size=100
> logfeeder.cache.key.field=log_message
> logfeeder.cache.dedup.interval=1000
> logfeeder.cache.last.dedup.enabled=false
> {code}
> can be overriden in input config block (per monitored file)
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Attachment: AMBARI-20378.patch
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at logfeeder.properties (global setting). For example (the
> values below are the defaults):
> {code:java}
> logfeeder.cache.enabled=false
> logfeeder.cache.size=100
> logfeeder.cache.key.field=log_message
> logfeeder.cache.dedup.interval=1000
> logfeeder.cache.last.dedup.enabled=false
> {code}
> can be overriden in input config block (per monitored file)
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Description:
Add de-duplication support to logfeeder.
For handling duplications, it will be an LRU cache for every input.
It can be set up at logfeeder.properties. For example (the values below are the
defaults):
{code:java}
logfeeder.cache.enabled=false
logfeeder.cache.size=100
logfeeder.cache.key.field=log_message
logfeeder.cache.dedup.interval=1000
logfeeder.cache.last.dedup.enabled=false
{code}
can be overriden in input config block (per monitored file)
{code:java}
{
"input": [
{
...
"cache_enabled" : "true",
"cache_size" : "100",
"cache_dedup_interval" : "1000",
"cache_last_dedup_enabled" : "false",
"cache_key_field" : "log_message"
}
] ...
{code}
{{cache_dedup_interval}} : if the interval (timestamp - date difference) is not
reached between 2 log messages (same content), then the new log will be
dropped.
{{cache_last_dedup_enabled}}: if its enabled and the new log message is the
same as the last one, the new log will be dropped. (dedup interval wont have
impact on that feature)
{{cache_key_field}} : field of the log message which will be compared and
stored in the cache (as keys)
was:
Add de-duplication support to logfeeder.
For handling duplications, it will be an LRU cache for every input.
It can be set up at input config block. For example (the values below are the
defaults):
{code:java}
{
"input": [
{
...
"cache_enabled" : "true",
"cache_size" : "100",
"cache_dedup_interval" : "1000",
"cache_last_dedup_enabled" : "false",
"cache_key_field" : "log_message"
}
] ...
{code}
{{cache_dedup_interval}} : if the interval (timestamp - date difference) is not
reached between 2 log messages (same content), then the new log will be
dropped.
{{cache_last_dedup_enabled}}: if its enabled and the new log message is the
same as the last one, the new log will be dropped. (dedup interval wont have
impact on that feature)
{{cache_key_field}} : field of the log message which will be compared and
stored in the cache (as keys)
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at logfeeder.properties. For example (the values below are
> the defaults):
> {code:java}
> logfeeder.cache.enabled=false
> logfeeder.cache.size=100
> logfeeder.cache.key.field=log_message
> logfeeder.cache.dedup.interval=1000
> logfeeder.cache.last.dedup.enabled=false
> {code}
> can be overriden in input config block (per monitored file)
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20399) [Upgrade] Unable to enable Credential store support on upgraded clusters
[ https://issues.apache.org/jira/browse/AMBARI-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20399: --- Attachment: AMBARI-20399.patch > [Upgrade] Unable to enable Credential store support on upgraded clusters > > > Key: AMBARI-20399 > URL: https://issues.apache.org/jira/browse/AMBARI-20399 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20399.patch > > > During a stack upgrade, the ServiceInfo does not get refreshed. Due to this, > the credential_store_supported flag is set to false when the expected value > is true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20399) [Upgrade] Unable to enable Credential store support on upgraded clusters
[ https://issues.apache.org/jira/browse/AMBARI-20399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20399: --- Status: Patch Available (was: Open) > [Upgrade] Unable to enable Credential store support on upgraded clusters > > > Key: AMBARI-20399 > URL: https://issues.apache.org/jira/browse/AMBARI-20399 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20399.patch > > > During a stack upgrade, the ServiceInfo does not get refreshed. Due to this, > the credential_store_supported flag is set to false when the expected value > is true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20399) [Upgrade] Unable to enable Credential store support on upgraded clusters
Madhuvanthi Radhakrishnan created AMBARI-20399: -- Summary: [Upgrade] Unable to enable Credential store support on upgraded clusters Key: AMBARI-20399 URL: https://issues.apache.org/jira/browse/AMBARI-20399 Project: Ambari Issue Type: Bug Components: ambari-sever Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.0 During a stack upgrade, the ServiceInfo does not get refreshed. Due to this, the credential_store_supported flag is set to false when the expected value is true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20396) Few Ambari Metrics configs don't have `property_value_attributes.type`
[
https://issues.apache.org/jira/browse/AMBARI-20396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905485#comment-15905485
]
Hadoop QA commented on AMBARI-20396:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857350/AMBARI-20396.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10970//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10970//console
This message is automatically generated.
> Few Ambari Metrics configs don't have `property_value_attributes.type`
> --
>
> Key: AMBARI-20396
> URL: https://issues.apache.org/jira/browse/AMBARI-20396
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20396.patch
>
>
> ssl.client.truststore.password
> ssl.server.keystore.keypassword
> ssl.server.keystore.password
> ssl.server.truststore.password
> This configs don't have property_value_attributes.type. So, this configs are
> shown as plaint text-fields and may be updated and overridden on the UI side.
> However metrics_grafana_password has property_value_attributes.type set to
> password and UI shows it as password-field.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20397) Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20397: Status: Patch Available (was: Open) > Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade > > > Key: AMBARI-20397 > URL: https://issues.apache.org/jira/browse/AMBARI-20397 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > > During stack upgrade spark2 and livy2 interpreters are not present in > zeppelin by default. Typically for a fresh install- when spark2 service is > detected , those 2 interpreters are by default created for user out-of-the box -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20397) Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath reassigned AMBARI-20397: --- Assignee: Renjith Kamath > Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade > > > Key: AMBARI-20397 > URL: https://issues.apache.org/jira/browse/AMBARI-20397 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.0 > > > During stack upgrade spark2 and livy2 interpreters are not present in > zeppelin by default. Typically for a fresh install- when spark2 service is > detected , those 2 interpreters are by default created for user out-of-the box -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20398) Data Not getting cleared
Kushagra Mittal created AMBARI-20398: Summary: Data Not getting cleared Key: AMBARI-20398 URL: https://issues.apache.org/jira/browse/AMBARI-20398 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Kushagra Mittal Priority: Minor I selected the repo and proceeded to select the services required and reached till review step.(There were multiple versions files inside /etc/yum.repos.d on different nodes) On Review Page on clicking continue i got some error message and it didn't allowed me to proceed. So i again go back to first same, it showed me warning that all changes will be lost and i clicked yes. I again did all the configs removing multiple version repo files and it ambari was still giving same exception on Review Page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20398) Data Not getting cleared
[ https://issues.apache.org/jira/browse/AMBARI-20398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kushagra Mittal updated AMBARI-20398: - Priority: Major (was: Minor) > Data Not getting cleared > > > Key: AMBARI-20398 > URL: https://issues.apache.org/jira/browse/AMBARI-20398 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Kushagra Mittal > > I selected the repo and proceeded to select the services required and reached > till review step.(There were multiple versions files inside /etc/yum.repos.d > on different nodes) On Review Page on clicking continue i got some error > message and it didn't allowed me to proceed. So i again go back to first > same, it showed me warning that all changes will be lost and i clicked yes. I > again did all the configs removing multiple version repo files and it ambari > was still giving same exception on Review Page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[
https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905392#comment-15905392
]
Hadoop QA commented on AMBARI-20243:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857341/AMBARI-20243-Mar10.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10969//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10969//console
This message is automatically generated.
> Include option to filter out properties from APi that returns
> ambari.properties file
>
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch,
> AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned
> by the API call.
> Some of those information may not be utilized and hence an option can be
> provided to filter the properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19835: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > --- > > Key: AMBARI-19835 > URL: https://issues.apache.org/jira/browse/AMBARI-19835 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-19835_2.patch, AMBARI-19835_3.patch > > > HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, > quicklinks, and themes > Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0 > In HDP 3.0, we have created a new stack definition that does not inherit from > other stacks, in order to reduce the complexity of having to analyze older > stacks. > This means that we need to create a service definition (metainfo.xml, > configs, kerberos, widgets, metrics, quicklinks, and themes) that is > equivalent to what is inherit and deleted from all of the previous stacks. > A merge needs to account for additions, overrides, and deletions. > metainfo.xml and configs perform a merge of older versions > kerberos.json always seems to override the previous file > Because the bits for this service may not yet be available in the HDP 3.0 > repo, > the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER > (which uses inheritance) is equivalent to the flattening of > /api/v1/stacks/HDP/versions/3.0/services/SLIDER . > Please take a look at how this was done for ZK, HDFS, and YARN/MR. > This means that you will not be able to actually install the service for now, > but can still perform validation during the Install Wizard that the correct > components and configs show up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20397) Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade
Kshitij Badani created AMBARI-20397: --- Summary: Zeppelin: Spark2 and Livy2 interpreter config disappear during stack upgrade Key: AMBARI-20397 URL: https://issues.apache.org/jira/browse/AMBARI-20397 Project: Ambari Issue Type: Bug Components: ambari-upgrade Affects Versions: 2.5.0 Reporter: Kshitij Badani Fix For: 2.5.0 During stack upgrade spark2 and livy2 interpreters are not present in zeppelin by default. Typically for a fresh install- when spark2 service is detected , those 2 interpreters are by default created for user out-of-the box -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20396) Few Ambari Metrics configs don't have `property_value_attributes.type`
[ https://issues.apache.org/jira/browse/AMBARI-20396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20396: Attachment: AMBARI-20396.patch > Few Ambari Metrics configs don't have `property_value_attributes.type` > -- > > Key: AMBARI-20396 > URL: https://issues.apache.org/jira/browse/AMBARI-20396 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20396.patch > > > ssl.client.truststore.password > ssl.server.keystore.keypassword > ssl.server.keystore.password > ssl.server.truststore.password > This configs don't have property_value_attributes.type. So, this configs are > shown as plaint text-fields and may be updated and overridden on the UI side. > However metrics_grafana_password has property_value_attributes.type set to > password and UI shows it as password-field. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20396) Few Ambari Metrics configs don't have `property_value_attributes.type`
[ https://issues.apache.org/jira/browse/AMBARI-20396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20396: Status: Patch Available (was: Open) > Few Ambari Metrics configs don't have `property_value_attributes.type` > -- > > Key: AMBARI-20396 > URL: https://issues.apache.org/jira/browse/AMBARI-20396 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20396.patch > > > ssl.client.truststore.password > ssl.server.keystore.keypassword > ssl.server.keystore.password > ssl.server.truststore.password > This configs don't have property_value_attributes.type. So, this configs are > shown as plaint text-fields and may be updated and overridden on the UI side. > However metrics_grafana_password has property_value_attributes.type set to > password and UI shows it as password-field. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20396) Few Ambari Metrics configs don't have `property_value_attributes.type`
Dmytro Sen created AMBARI-20396: --- Summary: Few Ambari Metrics configs don't have `property_value_attributes.type` Key: AMBARI-20396 URL: https://issues.apache.org/jira/browse/AMBARI-20396 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.5.0 ssl.client.truststore.password ssl.server.keystore.keypassword ssl.server.keystore.password ssl.server.truststore.password This configs don't have property_value_attributes.type. So, this configs are shown as plaint text-fields and may be updated and overridden on the UI side. However metrics_grafana_password has property_value_attributes.type set to password and UI shows it as password-field. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905344#comment-15905344 ] Doroszlai, Attila commented on AMBARI-20385: Thanks! > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385-2.patch, AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: AMBARI-20243-Mar10.patch > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch, > AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: (was: AMBARI-20243-Mar10.patch) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch, > AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20389:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20389.patch
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: AMBARI-20243-Mar10.patch > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch, > AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: (was: AMBARI-20243-Mar6.patch) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243-Mar10.patch, AMBARI-20243-Mar1.patch, > AMBARI-20243-Mar3.patch, AMBARI-20243-Mar8.patch, AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385-2.patch, AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Status: Patch Available (was: Reopened) Patch for unit test fix > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385-2.patch, AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Attachment: AMBARI-20385-2.patch > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385-2.patch, AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20383) Not able to view the error log details on UI
[
https://issues.apache.org/jira/browse/AMBARI-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905204#comment-15905204
]
Hadoop QA commented on AMBARI-20383:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857317/AMBARI-20383_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10968//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10968//console
This message is automatically generated.
> Not able to view the error log details on UI
> -
>
> Key: AMBARI-20383
> URL: https://issues.apache.org/jira/browse/AMBARI-20383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20383_trunk.patch
>
>
> Not able to view the error logs on UI. When user clicks on 'Details' link, UI
> is failing with below error:
> {code}
> Uncaught TypeError: Cannot read property 'nodes' of null
> at n.isWorkflowValid
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:8:25204)
> at n.validate
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:58:12130)
> at
> http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:30047
> at Array.map (native)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:29848)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:24894)
> at d.p.get
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:9:31289)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3104)
> at c
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3694)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3093)
> {code}
> Steps to reproduce :
> 1) Try to import a workflow which user doesn't have read permission.
> 2) 'Permission Denied' message is shown on the UI. But when user clicks on
> 'Details' link, UI is failing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20392) Get aggregate metric records from HBase encounters performance issues
[
https://issues.apache.org/jira/browse/AMBARI-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905130#comment-15905130
]
Hadoop QA commented on AMBARI-20392:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857320/AggregateMetric.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10967//console
This message is automatically generated.
> Get aggregate metric records from HBase encounters performance issues
> -
>
> Key: AMBARI-20392
> URL: https://issues.apache.org/jira/browse/AMBARI-20392
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.4.2
>Reporter: Chuan Jin
> Attachments: AggregateMetric.patch
>
>
> I have a mini cluster ( ~6 nodes) managed by Ambari, and use a distributed
> HBase (~3 nodes) to hold metrics collected from these nodes. After I deploy
> YARN serivce, then I notice that some widgets (Cluster Memory,Cluster
> Disk,...) cannot display properly in the YARN service dashboard page. And
> Ambari Server has continuous timeout exceptions, which complains that it
> doesn't get timeline metrics for connection refused.
> The request timeout parameter is 5s, which means the query of getting metrics
> from HBase takes more time than that. Then I use Phoenix shell to login and
> perform the same query in the HBase , and it takes nearly 30s to finish. But
> If I split the big query into small pieces , i mean, use less values in the
> "metric_name" field in the where ... in clause , then the result return in 1s
> after several small queries.
> The query performance in HBase is highly based on the design of rowkey and
> the proper usage for it. In the method of getting aggregate metrics, AMS
> collector query the METRIC_AGGREGATE table in a way that may cause the
> co-processor to scan several regions across different RS. If we add more
> metrics in the service dashboard, this situation will be worse.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[
https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905127#comment-15905127
]
Hadoop QA commented on AMBARI-20395:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857324/AMBARI-20395.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10966//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10966//console
This message is automatically generated.
> Clicking on ambari logo on ambari-admin ui takes to broken layout on
> ambari-web
> ---
>
> Key: AMBARI-20395
> URL: https://issues.apache.org/jira/browse/AMBARI-20395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13
> PM.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[
https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reopened AMBARI-20385:
[~avijayan], could you please check this unit test failure? Thanks.
{noformat}
ERROR: test_start (test_metrics_grafana.TestMetricsGrafana)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py",
line 47, in test_start
target = RMFTestCase.TARGET_COMMON_SERVICES
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 155, in executeScript
method(RMFTestCase.env, *command_args)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 58, in start
create_grafana_admin_pwd()
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 230, in create_grafana_admin_pwd
host = params.ams_grafana_host.strip(),
AttributeError: 'NoneType' object has no attribute 'strip'
{noformat}
> Grafana is storing credentials in plain text in its configuration
> -
>
> Key: AMBARI-20385
> URL: https://issues.apache.org/jira/browse/AMBARI-20385
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20385.patch
>
>
> Grafana stores the cluster admin credentails in plain text form at
> /etc/ambari-metrics-grafana/conf/ams-grafana.ini
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20394) Penetration test: Missing Content-Type header of woff/ttf files
[ https://issues.apache.org/jira/browse/AMBARI-20394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-20394: --- Attachment: AMBARI-20394_trunk.patch AMBARI-20394_branch-2.5.patch > Penetration test: Missing Content-Type header of woff/ttf files > --- > > Key: AMBARI-20394 > URL: https://issues.apache.org/jira/browse/AMBARI-20394 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > Attachments: AMBARI-20394_branch-2.5.patch, AMBARI-20394_trunk.patch > > > No Content-Type HTTP header is set when downloading woff or ttf files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20387) Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
[
https://issues.apache.org/jira/browse/AMBARI-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20387:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
> -
>
> Key: AMBARI-20387
> URL: https://issues.apache.org/jira/browse/AMBARI-20387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20387.patch
>
>
> There are some MySQL installations of Ambari which are correctly setup to use
> {{InnoDB}}, but still are missing foreign key relationships on certain
> tables. When the upgrade catalogs try to drop foreign keys by name, they are
> not found. However, when re-creating them, the existing {{INDEX}} constraints
> are named the same and prevent the new FKs from being created.
> {code}
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:350)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
> at com.mysql.jdbc.Util.getInstance(Util.java:387)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:942)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3902)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2503)
> at
> com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:839)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:739)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:827)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:472)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:456)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.updateServiceComponentDesiredStateTableDDL(UpgradeCatalog240.java:1621)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:898)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> {code}
> {code}
> mysql> show create table hostcomponentdesiredstate;
> --+
> | hostcomponentdesiredstate | CREATE TABLE `hostcomponentdesiredstate` (
> `cluster_id` bigint(20) NOT NULL,
> `component_name` varchar(255) NOT NULL,
> `desired_state` varchar(255) NOT NULL,
> `service_name` varchar(255) NOT NULL,
> `admin_state` varchar(32) DEFAULT NULL,
> `maintenance_state` varchar(32) NOT NULL DEFAULT 'ACTIVE',
> `security_state` varchar(32) NOT NULL DEFAULT 'UNSECURED',
> `restart_required` tinyint(1) NOT NULL DEFAULT '0',
> `host_id` bigint(20) NOT NULL,
> `desired_stack_id` bigint(20) NOT NULL,
> PRIMARY KEY (`cluster_id`,`component_name`,`host_id`,`service_name`),
> KEY `hstcmpnntdesiredstatecmpnntnme`
> (`component_name`,`cluster_id`,`service_name`),
> KEY `FK_hostcomponentdesiredstate_desired_stack_id` (`desired_stack_id`),
> KEY `FK_hostcomponentdesiredstate_host_id` (`host_id`),
> CONSTRAINT `FK_hcdesiredstate_host_id` FOREIGN KEY (`host_id`) REFERENCES
> `hosts` (`host_id`),
> CONSTRAINT `fk_hcds_desired_stack_id` FOREIGN KEY (`desired_stack_id`)
> REFERENCES `stack` (`stack_id`),
>
[jira] [Commented] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905090#comment-15905090 ] Andrii Tkach commented on AMBARI-20395: --- committed to trunk > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20393) Fix typo in alert-definitions doc file
[
https://issues.apache.org/jira/browse/AMBARI-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905071#comment-15905071
]
Hadoop QA commented on AMBARI-20393:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857325/AMBARI-20393.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10965//console
This message is automatically generated.
> Fix typo in alert-definitions doc file
> --
>
> Key: AMBARI-20393
> URL: https://issues.apache.org/jira/browse/AMBARI-20393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20393.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905070#comment-15905070 ] Aleksandr Kovalenko commented on AMBARI-20395: -- +1 for the patch > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[
https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905069#comment-15905069
]
Hadoop QA commented on AMBARI-20395:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857323/AMBARI-20395.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10964//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10964//console
This message is automatically generated.
> Clicking on ambari logo on ambari-admin ui takes to broken layout on
> ambari-web
> ---
>
> Key: AMBARI-20395
> URL: https://issues.apache.org/jira/browse/AMBARI-20395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13
> PM.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20393) Fix typo in alert-definitions doc file
[ https://issues.apache.org/jira/browse/AMBARI-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20393: -- Attachment: AMBARI-20393.patch > Fix typo in alert-definitions doc file > -- > > Key: AMBARI-20393 > URL: https://issues.apache.org/jira/browse/AMBARI-20393 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: trunk > > Attachments: AMBARI-20393.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20393) Fix typo in alert-definitions doc file
[ https://issues.apache.org/jira/browse/AMBARI-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20393: -- Status: Patch Available (was: Open) > Fix typo in alert-definitions doc file > -- > > Key: AMBARI-20393 > URL: https://issues.apache.org/jira/browse/AMBARI-20393 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: trunk > > Attachments: AMBARI-20393.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20393) Fix typo in alert-definitions doc file
[
https://issues.apache.org/jira/browse/AMBARI-20393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905046#comment-15905046
]
Olivér Szabó commented on AMBARI-20393:
---
committed to trunk:
{code:java}
commit 0da5fc02193809487d3de7373bdfd466d561464b
Author: oleewere
Date: Fri Mar 10 12:25:53 2017 +0100
AMBARI-20393. Fix typo in alert-definitions doc file (oleewere)
{code}
> Fix typo in alert-definitions doc file
> --
>
> Key: AMBARI-20393
> URL: https://issues.apache.org/jira/browse/AMBARI-20393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Attachment: (was: AMBARI-20395.patch) > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Attachment: AMBARI-20395.patch > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Status: Patch Available (was: Open) > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Status: Open (was: Patch Available) > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905039#comment-15905039 ] Andrii Tkach commented on AMBARI-20395: --- 20559 passing (35s) 153 pending > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20395) Clicking on ambari logo on ambari-admin ui takes to broken layout on ambari-web
[ https://issues.apache.org/jira/browse/AMBARI-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20395: -- Attachment: AMBARI-20395.patch > Clicking on ambari logo on ambari-admin ui takes to broken layout on > ambari-web > --- > > Key: AMBARI-20395 > URL: https://issues.apache.org/jira/browse/AMBARI-20395 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20395.patch, Screen Shot 2017-03-01 at 3.53.13 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
