[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.1.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18297) View for Apache HAWQ
[
https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457143#comment-15457143
]
Hadoop QA commented on AMBARI-18297:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826749/AMBARI-18297-orig-binary.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 16 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:red}-1 core tests{color}. The test build failed in
contrib/views/hawq
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8557//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8557//console
This message is automatically generated.
> View for Apache HAWQ
>
>
> Key: AMBARI-18297
> URL: https://issues.apache.org/jira/browse/AMBARI-18297
> Project: Ambari
> Issue Type: New Feature
> Components: contrib
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Stuart Pollock
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18297-orig-binary.patch, AMBARI-18297-orig.patch
>
>
> Add initial code for HAWQ View under contrib/views
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18297: -- Attachment: AMBARI-18297-orig.patch > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18297-orig-binary.patch, AMBARI-18297-orig.patch > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18297: -- Attachment: AMBARI-18297-orig-binary.patch > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18297-orig-binary.patch, AMBARI-18297-orig.patch > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18297: -- Attachment: (was: AMBARI-18297-orig.patch) > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18297-orig-binary.patch, AMBARI-18297-orig.patch > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18297) View for Apache HAWQ
[
https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457056#comment-15457056
]
Hadoop QA commented on AMBARI-18297:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826721/AMBARI-18297-orig.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/8556//console
This message is automatically generated.
> View for Apache HAWQ
>
>
> Key: AMBARI-18297
> URL: https://issues.apache.org/jira/browse/AMBARI-18297
> Project: Ambari
> Issue Type: New Feature
> Components: contrib
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Stuart Pollock
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18297-orig.patch
>
>
> Add initial code for HAWQ View under contrib/views
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18299) Support open files ulimit for ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18299: --- Attachment: rb51588.patch > Support open files ulimit for ambari-agent > -- > > Key: AMBARI-18299 > URL: https://issues.apache.org/jira/browse/AMBARI-18299 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 3.0.0 > > Attachments: rb51588.patch > > > The properties file ambari.properties has ulimit flag to override ulimit on > ambari-server. > For ambari-agent there is no such config override. There have been few cases > where user needed to override ulimit on agent nodes. > It will be good to have a first class support for this through > ambari-agent.ini file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18299) Support open files ulimit for ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18299: --- Status: Patch Available (was: Open) > Support open files ulimit for ambari-agent > -- > > Key: AMBARI-18299 > URL: https://issues.apache.org/jira/browse/AMBARI-18299 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 3.0.0 > > Attachments: rb51588.patch > > > The properties file ambari.properties has ulimit flag to override ulimit on > ambari-server. > For ambari-agent there is no such config override. There have been few cases > where user needed to override ulimit on agent nodes. > It will be good to have a first class support for this through > ambari-agent.ini file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18299) Support open files ulimit for ambari-agent
Nahappan Somasundaram created AMBARI-18299: -- Summary: Support open files ulimit for ambari-agent Key: AMBARI-18299 URL: https://issues.apache.org/jira/browse/AMBARI-18299 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.5.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Fix For: 3.0.0 The properties file ambari.properties has ulimit flag to override ulimit on ambari-server. For ambari-agent there is no such config override. There have been few cases where user needed to override ulimit on agent nodes. It will be good to have a first class support for this through ambari-agent.ini file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18297: -- Status: Patch Available (was: Open) > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18297-orig.patch > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Pollock updated AMBARI-18297: Attachment: AMBARI-18297-orig.patch Initial patch > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18297-orig.patch > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18297) View for Apache HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Pollock reassigned AMBARI-18297: --- Assignee: Stuart Pollock > View for Apache HAWQ > > > Key: AMBARI-18297 > URL: https://issues.apache.org/jira/browse/AMBARI-18297 > Project: Ambari > Issue Type: New Feature > Components: contrib >Affects Versions: trunk >Reporter: Matt >Assignee: Stuart Pollock >Priority: Minor > Fix For: trunk > > > Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18298) Add ability to add custom grok filters and custom grok patterns with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18298: Status: Patch Available (was: In Progress) > Add ability to add custom grok filters and custom grok patterns with Ambari > --- > > Key: AMBARI-18298 > URL: https://issues.apache.org/jira/browse/AMBARI-18298 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18298.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18298) Add ability to add custom grok filters and custom grok patterns with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18298: Attachment: AMBARI-18298.patch > Add ability to add custom grok filters and custom grok patterns with Ambari > --- > > Key: AMBARI-18298 > URL: https://issues.apache.org/jira/browse/AMBARI-18298 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18298.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18298) Add ability to add custom grok filters and custom grok patterns with Ambari
Miklos Gergely created AMBARI-18298: --- Summary: Add ability to add custom grok filters and custom grok patterns with Ambari Key: AMBARI-18298 URL: https://issues.apache.org/jira/browse/AMBARI-18298 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch, AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[ https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456417#comment-15456417 ] Hudson commented on AMBARI-18273: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5615 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5615/]) AMBARI-18273. Add logging to differentiate between ambari-server (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8f7506c5aee1bba768f8f0c4fb929542308cfa63]) * (edit) ambari-server/conf/unix/ambari.properties * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/python/ambari_server/hostUpdate.py * (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py * (edit) ambari-server/sbin/ambari-server * (edit) ambari-server/src/main/python/ambari_server/setupSso.py * (edit) ambari-server/src/main/python/ambari_server/setupActions.py * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/python/ambari_server/checkDatabase.py * (edit) ambari-server/src/main/python/ambari_server/serverSetup.py * (edit) ambari-server/src/main/python/ambari_server/setupMpacks.py * (edit) ambari-server/src/main/python/ambari-server.py * (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py * (edit) ambari-server/src/main/python/ambari_server/dbCleanup.py > Add logging to differentiate between ambari-server start/restart commands vs. > other commands > > > Key: AMBARI-18273 > URL: https://issues.apache.org/jira/browse/AMBARI-18273 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18273.patch > > > Add ambari server python side logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18296) Database Consistency Check Fails With NPE With Missing Service From Stack
[
https://issues.apache.org/jira/browse/AMBARI-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18296:
---
Status: Patch Available (was: Open)
> Database Consistency Check Fails With NPE With Missing Service From Stack
> -
>
> Key: AMBARI-18296
> URL: https://issues.apache.org/jira/browse/AMBARI-18296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18296.patch
>
>
> The database consistency checker can fail if a service configuration exists
> for a service which is no longer on the current stack:
> {code}
> 2016-08-31 21:52:28,082 INFO - *** Check database
> started *** 2016-08-31 21:52:31,647 INFO -
> Checking for configs not mapped to any cluster 2016-08-31 21:52:31,653 INFO -
> Checking for configs selected more than once 2016-08-31 21:52:31,655 INFO -
> Checking for hosts without state 2016-08-31 21:52:31,657 INFO - Checking host
> component states count equals host component desired states count 2016-08-31
> 21:52:31,660 INFO - Checking services and their configs 2016-08-31
> 21:52:33,669 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It seems like what happens is this query returns a service which is not
> defined in the current stack:
> {code}
> SELECT
> c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> FROM clusterservices cs
> JOIN serviceconfig sc
> ON cs.service_name = sc.service_name
> AND cs.cluster_id = sc.cluster_id
> JOIN serviceconfigmapping scm
> ON sc.service_config_id = scm.service_config_id
> JOIN clusterconfig cc
> ON scm.config_id = cc.config_id
> AND sc.cluster_id = cc.cluster_id
> JOIN clusters c
> ON cc.cluster_id = c.cluster_id
> AND sc.stack_id = c.desired_stack_id
> WHERE sc.group_id IS NULL
> AND sc.service_config_id = (SELECT
> MAX(service_config_id)
> FROM serviceconfig sc2
> WHERE sc2.service_name = sc.service_name
> AND sc2.cluster_id = sc.cluster_id)
> GROUP BY c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> {code}
> Problem area of code:
> {code:title=serviceInfo is null}
> for (String serviceName : serviceNames) {
> ServiceInfo serviceInfo = serviceInfoMap.get(serviceName);
> Set configTypes =
> serviceInfo.getConfigTypeAttributes().keySet();
> for (String configType : configTypes) {
> stackServiceConfigs.put(serviceName, configType);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-18296) Database Consistency Check Fails With NPE With Missing Service From Stack
[
https://issues.apache.org/jira/browse/AMBARI-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi reassigned AMBARI-18296:
--
Assignee: Vitaly Brodetskyi
> Database Consistency Check Fails With NPE With Missing Service From Stack
> -
>
> Key: AMBARI-18296
> URL: https://issues.apache.org/jira/browse/AMBARI-18296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18296.patch
>
>
> The database consistency checker can fail if a service configuration exists
> for a service which is no longer on the current stack:
> {code}
> 2016-08-31 21:52:28,082 INFO - *** Check database
> started *** 2016-08-31 21:52:31,647 INFO -
> Checking for configs not mapped to any cluster 2016-08-31 21:52:31,653 INFO -
> Checking for configs selected more than once 2016-08-31 21:52:31,655 INFO -
> Checking for hosts without state 2016-08-31 21:52:31,657 INFO - Checking host
> component states count equals host component desired states count 2016-08-31
> 21:52:31,660 INFO - Checking services and their configs 2016-08-31
> 21:52:33,669 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It seems like what happens is this query returns a service which is not
> defined in the current stack:
> {code}
> SELECT
> c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> FROM clusterservices cs
> JOIN serviceconfig sc
> ON cs.service_name = sc.service_name
> AND cs.cluster_id = sc.cluster_id
> JOIN serviceconfigmapping scm
> ON sc.service_config_id = scm.service_config_id
> JOIN clusterconfig cc
> ON scm.config_id = cc.config_id
> AND sc.cluster_id = cc.cluster_id
> JOIN clusters c
> ON cc.cluster_id = c.cluster_id
> AND sc.stack_id = c.desired_stack_id
> WHERE sc.group_id IS NULL
> AND sc.service_config_id = (SELECT
> MAX(service_config_id)
> FROM serviceconfig sc2
> WHERE sc2.service_name = sc.service_name
> AND sc2.cluster_id = sc.cluster_id)
> GROUP BY c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> {code}
> Problem area of code:
> {code:title=serviceInfo is null}
> for (String serviceName : serviceNames) {
> ServiceInfo serviceInfo = serviceInfoMap.get(serviceName);
> Set configTypes =
> serviceInfo.getConfigTypeAttributes().keySet();
> for (String configType : configTypes) {
> stackServiceConfigs.put(serviceName, configType);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18296) Database Consistency Check Fails With NPE With Missing Service From Stack
[
https://issues.apache.org/jira/browse/AMBARI-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18296:
---
Attachment: AMBARI-18296.patch
> Database Consistency Check Fails With NPE With Missing Service From Stack
> -
>
> Key: AMBARI-18296
> URL: https://issues.apache.org/jira/browse/AMBARI-18296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18296.patch
>
>
> The database consistency checker can fail if a service configuration exists
> for a service which is no longer on the current stack:
> {code}
> 2016-08-31 21:52:28,082 INFO - *** Check database
> started *** 2016-08-31 21:52:31,647 INFO -
> Checking for configs not mapped to any cluster 2016-08-31 21:52:31,653 INFO -
> Checking for configs selected more than once 2016-08-31 21:52:31,655 INFO -
> Checking for hosts without state 2016-08-31 21:52:31,657 INFO - Checking host
> component states count equals host component desired states count 2016-08-31
> 21:52:31,660 INFO - Checking services and their configs 2016-08-31
> 21:52:33,669 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It seems like what happens is this query returns a service which is not
> defined in the current stack:
> {code}
> SELECT
> c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> FROM clusterservices cs
> JOIN serviceconfig sc
> ON cs.service_name = sc.service_name
> AND cs.cluster_id = sc.cluster_id
> JOIN serviceconfigmapping scm
> ON sc.service_config_id = scm.service_config_id
> JOIN clusterconfig cc
> ON scm.config_id = cc.config_id
> AND sc.cluster_id = cc.cluster_id
> JOIN clusters c
> ON cc.cluster_id = c.cluster_id
> AND sc.stack_id = c.desired_stack_id
> WHERE sc.group_id IS NULL
> AND sc.service_config_id = (SELECT
> MAX(service_config_id)
> FROM serviceconfig sc2
> WHERE sc2.service_name = sc.service_name
> AND sc2.cluster_id = sc.cluster_id)
> GROUP BY c.cluster_name,
> cs.service_name,
> cc.type_name,
> sc.version
> {code}
> Problem area of code:
> {code:title=serviceInfo is null}
> for (String serviceName : serviceNames) {
> ServiceInfo serviceInfo = serviceInfoMap.get(serviceName);
> Set configTypes =
> serviceInfo.getConfigTypeAttributes().keySet();
> for (String configType : configTypes) {
> stackServiceConfigs.put(serviceName, configType);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15621) Cluster Second aggregator taking more than 2 mins to execute on large clusters, thereby causing lag.
[ https://issues.apache.org/jira/browse/AMBARI-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15621: --- Affects Version/s: 2.2.2 > Cluster Second aggregator taking more than 2 mins to execute on large > clusters, thereby causing lag. > > > Key: AMBARI-15621 > URL: https://issues.apache.org/jira/browse/AMBARI-15621 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15621.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15680) METRICS_GRAFANA START failed with 401 Unauthorized Error
[ https://issues.apache.org/jira/browse/AMBARI-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15680: --- Component/s: ambari-metrics > METRICS_GRAFANA START failed with 401 Unauthorized Error > > > Key: AMBARI-15680 > URL: https://issues.apache.org/jira/browse/AMBARI-15680 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15680.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15680) METRICS_GRAFANA START failed with 401 Unauthorized Error
[ https://issues.apache.org/jira/browse/AMBARI-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15680: --- Affects Version/s: 2.2.2 > METRICS_GRAFANA START failed with 401 Unauthorized Error > > > Key: AMBARI-15680 > URL: https://issues.apache.org/jira/browse/AMBARI-15680 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15680.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18297) View for Apache HAWQ
Matt created AMBARI-18297: - Summary: View for Apache HAWQ Key: AMBARI-18297 URL: https://issues.apache.org/jira/browse/AMBARI-18297 Project: Ambari Issue Type: New Feature Components: contrib Affects Versions: trunk Reporter: Matt Priority: Minor Fix For: trunk Add initial code for HAWQ View under contrib/views -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15680) METRICS_GRAFANA START failed with 401 Unauthorized Error
[ https://issues.apache.org/jira/browse/AMBARI-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15680: --- Fix Version/s: 2.2.2 > METRICS_GRAFANA START failed with 401 Unauthorized Error > > > Key: AMBARI-15680 > URL: https://issues.apache.org/jira/browse/AMBARI-15680 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15680.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15621) Cluster Second aggregator taking more than 2 mins to execute on large clusters, thereby causing lag.
[ https://issues.apache.org/jira/browse/AMBARI-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15621: --- Component/s: ambari-metrics > Cluster Second aggregator taking more than 2 mins to execute on large > clusters, thereby causing lag. > > > Key: AMBARI-15621 > URL: https://issues.apache.org/jira/browse/AMBARI-15621 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15621.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15452) Change timeouts for Hbase and Phoenix
[ https://issues.apache.org/jira/browse/AMBARI-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15452: --- Fix Version/s: 2.2.2 > Change timeouts for Hbase and Phoenix > - > > Key: AMBARI-15452 > URL: https://issues.apache.org/jira/browse/AMBARI-15452 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Labels: ambari-metrics > Fix For: 2.2.2 > > Attachments: AMBARI-15452-trunk.patch, AMBARI-15452.patch > > > Change a few timeouts in AMS Hbase and Phoenix to 5 minutes in Hbase-site.xml > hbase.client.scanner.timeout.period = 30 > hbase.rpc.timeout = 30 > phoenix.query.timeoutMs = 30 > phoenix.query.keepAliveMs = 30 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15452) Change timeouts for Hbase and Phoenix
[ https://issues.apache.org/jira/browse/AMBARI-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15452: --- Labels: ambari-metrics (was: ) > Change timeouts for Hbase and Phoenix > - > > Key: AMBARI-15452 > URL: https://issues.apache.org/jira/browse/AMBARI-15452 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Labels: ambari-metrics > Fix For: 2.2.2 > > Attachments: AMBARI-15452-trunk.patch, AMBARI-15452.patch > > > Change a few timeouts in AMS Hbase and Phoenix to 5 minutes in Hbase-site.xml > hbase.client.scanner.timeout.period = 30 > hbase.rpc.timeout = 30 > phoenix.query.timeoutMs = 30 > phoenix.query.keepAliveMs = 30 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15452) Change timeouts for Hbase and Phoenix
[ https://issues.apache.org/jira/browse/AMBARI-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15452: --- Affects Version/s: 2.2.2 > Change timeouts for Hbase and Phoenix > - > > Key: AMBARI-15452 > URL: https://issues.apache.org/jira/browse/AMBARI-15452 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Labels: ambari-metrics > Fix For: 2.2.2 > > Attachments: AMBARI-15452-trunk.patch, AMBARI-15452.patch > > > Change a few timeouts in AMS Hbase and Phoenix to 5 minutes in Hbase-site.xml > hbase.client.scanner.timeout.period = 30 > hbase.rpc.timeout = 30 > phoenix.query.timeoutMs = 30 > phoenix.query.keepAliveMs = 30 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15452) Change timeouts for Hbase and Phoenix
[ https://issues.apache.org/jira/browse/AMBARI-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15452: --- Component/s: ambari-metrics > Change timeouts for Hbase and Phoenix > - > > Key: AMBARI-15452 > URL: https://issues.apache.org/jira/browse/AMBARI-15452 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Labels: ambari-metrics > Fix For: 2.2.2 > > Attachments: AMBARI-15452-trunk.patch, AMBARI-15452.patch > > > Change a few timeouts in AMS Hbase and Phoenix to 5 minutes in Hbase-site.xml > hbase.client.scanner.timeout.period = 30 > hbase.rpc.timeout = 30 > phoenix.query.timeoutMs = 30 > phoenix.query.keepAliveMs = 30 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Fix Version/s: 2.2.2 > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15698) Metrics is not showing data
[ https://issues.apache.org/jira/browse/AMBARI-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15698: --- Affects Version/s: 2.2.2 > Metrics is not showing data > --- > > Key: AMBARI-15698 > URL: https://issues.apache.org/jira/browse/AMBARI-15698 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 > Environment: TestStormServiceMetrics > Impacted test method : testStormMetrics > Test makes the api call > /api/v1/clusters/cl1/services/STORM/components/NIMBUS?fields=metrics/storm/nimbus/totalslots[1459768484,1459772084,15],metrics/storm/nimbus/freeslots[1459768484,1459772084,15],metrics/storm/nimbus/usedslots[1459768484,1459772084,15] > and compares the result for field 'metrics'. > Due to this issue, api response doesn't contain metrics field causing the > test to fail >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15698.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Affects Version/s: 2.2.2 > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15698) Metrics is not showing data
[ https://issues.apache.org/jira/browse/AMBARI-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15698: --- Fix Version/s: 2.2.2 > Metrics is not showing data > --- > > Key: AMBARI-15698 > URL: https://issues.apache.org/jira/browse/AMBARI-15698 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 > Environment: TestStormServiceMetrics > Impacted test method : testStormMetrics > Test makes the api call > /api/v1/clusters/cl1/services/STORM/components/NIMBUS?fields=metrics/storm/nimbus/totalslots[1459768484,1459772084,15],metrics/storm/nimbus/freeslots[1459768484,1459772084,15],metrics/storm/nimbus/usedslots[1459768484,1459772084,15] > and compares the result for field 'metrics'. > Due to this issue, api response doesn't contain metrics field causing the > test to fail >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15698.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18154) Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric
[ https://issues.apache.org/jira/browse/AMBARI-18154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18154: --- Fix Version/s: 2.5.0 > Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric > > > Key: AMBARI-18154 > URL: https://issues.apache.org/jira/browse/AMBARI-18154 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.0, 2.2.1, 2.2.2 >Reporter: Sandeep Nemuri >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18154.patch, Cluster_Load.png > > > *PROBLEM* : > Under Ambari Dashboard -> Cluster metrics. > It has been noticed that the metrics Nodes._avg and CPUs._avg are showing the > same data. > Below is the screenshot which shows Cluster metrics of a cluster which has > nodes 200+ and the Nodes._avg shows 18.5 as maximum value. > !Cluster_Load.png|align=center,|height=750%,width=700&! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16969: --- Affects Version/s: (was: 2.2.2) 2.4.0 > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.4.0 > > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file > Additional change - Ability to specifiy different durability settings for > precision/aggregate tables. > ams-site : timeline.metrics.precision.table.durability > ams-site : timeline.metrics.aggregate.tables.durability > Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16969: --- Affects Version/s: 2.2.2 > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.4.0 > > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file > Additional change - Ability to specifiy different durability settings for > precision/aggregate tables. > ams-site : timeline.metrics.precision.table.durability > ams-site : timeline.metrics.aggregate.tables.durability > Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16969: --- Fix Version/s: 2.4.0 > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.4.0 > > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file > Additional change - Ability to specifiy different durability settings for > precision/aggregate tables. > ams-site : timeline.metrics.precision.table.durability > ams-site : timeline.metrics.aggregate.tables.durability > Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16969: --- Description: The file should contain a list of metrics that will be the only metrics stored and aggregated in AMS. Config to use for specifying metric file. ams-site : timeline.metrics.whitelist.file Additional change - Ability to specifiy different durability settings for precision/aggregate tables. ams-site : timeline.metrics.precision.table.durability ams-site : timeline.metrics.aggregate.tables.durability Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL was: The file should contain a list of metrics that will be the only metrics stored and aggregated in AMS. Config to use for specifying metric file. ams-site : timeline.metrics.whitelist.file > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file > Additional change - Ability to specifiy different durability settings for > precision/aggregate tables. > ams-site : timeline.metrics.precision.table.durability > ams-site : timeline.metrics.aggregate.tables.durability > Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15872) Provide ability to tune WAL file writes for AMS HBase tables
[ https://issues.apache.org/jira/browse/AMBARI-15872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15872: --- Affects Version/s: 2.2.1 > Provide ability to tune WAL file writes for AMS HBase tables > - > > Key: AMBARI-15872 > URL: https://issues.apache.org/jira/browse/AMBARI-15872 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-15872.patch > > > This is a tuning parameter that can be used in HBase to improve performance > as a trade-off to data loss. For large clusters, this is a very useful > optimization that can be employed. > FIX > Added an optional config (Not available through default from the stack) > ams-site : timeline.metrics.tables.durability > Valid values it can take : SKIP_WAL / SYNC_WAL / ASYNC_WAL / FSYNC_WAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18291) Ambari tempory path configuration
[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy reassigned AMBARI-18291: -- Assignee: amarnathreddy > Ambari tempory path configuration > - > > Key: AMBARI-18291 > URL: https://issues.apache.org/jira/browse/AMBARI-18291 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Trivial > > By default Ambari uses "/tmp" as temporary path, > 1. while using Ambari-server it creates so many temporary files under /tmp > path. > 2. While doing the file upload in the File View, Ambari uses /tmp path during > the file upload and if there is no enough space left then file upload would > fail. > Proposing solution: > path should be configurable in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18290) Ambari does not support HBase on HTTPS mode
[ https://issues.apache.org/jira/browse/AMBARI-18290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy reassigned AMBARI-18290: -- Assignee: amarnathreddy > Ambari does not support HBase on HTTPS mode > --- > > Key: AMBARI-18290 > URL: https://issues.apache.org/jira/browse/AMBARI-18290 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Critical > > Ambari try to talk to Hbase URL on HTTP mode even after SSL is enabled for > HBase master. it is enable the retrieve JMX parameters and show the HBase > master as standby even though there is one Hbase master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18287) status commands get all the *-env files irrespective of a service exists or not
[ https://issues.apache.org/jira/browse/AMBARI-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456153#comment-15456153 ] Hudson commented on AMBARI-18287: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5614/]) AMBARI-18287. status commands get all the *-env files irrespective of a (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2c40528d9ae1e36b7bab9b5f3dd51338dd8e7366]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatMonitor.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatMonitor.java > status commands get all the *-env files irrespective of a service exists or > not > --- > > Key: AMBARI-18287 > URL: https://issues.apache.org/jira/browse/AMBARI-18287 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18287.patch > > > Ambari should not send env files corresponding to the deleted services for > the status commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-11639: --- Status: Patch Available (was: In Progress) > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 > Environment: RHEL 6.6 >Reporter: Jesus Alvarez >Assignee: Di Li > Fix For: trunk > > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch, > AMBARI-11639.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-11639: --- Environment: (was: RHEL 6.6) > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 >Reporter: Jesus Alvarez >Assignee: Di Li > Fix For: trunk > > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch, > AMBARI-11639.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-11639: --- Fix Version/s: trunk Status: In Progress (was: Patch Available) > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 > Environment: RHEL 6.6 >Reporter: Jesus Alvarez >Assignee: Di Li > Fix For: trunk > > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-11639: --- Attachment: AMBARI-11639.patch > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 > Environment: RHEL 6.6 >Reporter: Jesus Alvarez >Assignee: Di Li > Fix For: trunk > > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch, > AMBARI-11639.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17999: - Fix Version/s: trunk > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Assignee: Ying Zhang >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17999.patch, AMBARI-17999.rebased.patch > > > In Ambari code, property name "yarn.nodemanager.log.retain-second" is wrong. > It should be "yarn.nodemanager.log.retain-seconds" instead, which is the > property name being looked up in Hadoop code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17999: - Assignee: Ying Zhang > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Assignee: Ying Zhang >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17999.patch, AMBARI-17999.rebased.patch > > > In Ambari code, property name "yarn.nodemanager.log.retain-second" is wrong. > It should be "yarn.nodemanager.log.retain-seconds" instead, which is the > property name being looked up in Hadoop code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456057#comment-15456057 ] Di Li commented on AMBARI-11639: After a discussion with Jesus, I am taking the jira from here to move it further. > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 > Environment: RHEL 6.6 >Reporter: Jesus Alvarez >Assignee: Di Li > Fix For: trunk > > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch, > AMBARI-11639.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18273) Add logging to differentiate between ambari-server start/restart commands vs. other commands
[ https://issues.apache.org/jira/browse/AMBARI-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18273: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Add logging to differentiate between ambari-server start/restart commands vs. > other commands > > > Key: AMBARI-18273 > URL: https://issues.apache.org/jira/browse/AMBARI-18273 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18273.patch > > > Add ambari server python side logging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18287) status commands get all the *-env files irrespective of a service exists or not
[ https://issues.apache.org/jira/browse/AMBARI-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18287: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > status commands get all the *-env files irrespective of a service exists or > not > --- > > Key: AMBARI-18287 > URL: https://issues.apache.org/jira/browse/AMBARI-18287 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18287.patch > > > Ambari should not send env files corresponding to the deleted services for > the status commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455716#comment-15455716 ] Hudson commented on AMBARI-18295: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5613/]) AMBARI-18295. Dependent Configurations popup isn't changed after the (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=169d8dbbfd7c0f0e21e3f99f3c6e52f622f87aac]) * (edit) ambari-web/app/mixins/common/configs/config_recommendations.js * (edit) ambari-web/test/mixins/common/configs/config_recommendations_test.js * (edit) ambari-web/app/templates/common/modal_popups/dependent_configs_list.hbs * (add) ambari-web/app/views/common/configs/config_diff_view.js * (edit) ambari-web/app/views.js > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[
https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455706#comment-15455706
]
Hadoop QA commented on AMBARI-18295:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826613/AMBARI-18295.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/8555//console
This message is automatically generated.
> Dependent Configurations popup isn't changed after the subsequent property
> changes
> --
>
> Key: AMBARI-18295
> URL: https://issues.apache.org/jira/browse/AMBARI-18295
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18295.patch
>
>
> *STR:*
> 1) Deploy a cluster
> 2) Go to YARN -> Configs
> 3) Change 'Minimum Container Size (Memory)'
> 4) Click 'Show Details' to open the 'Dependent Configurations' popup.
> 5) Close the popup and change 'Minimum Container Size (Memory)' again
> 6) Open 'Dependent Configurations' popup again.
> *Result:*
> The 'Recommended values' displayed in the popup are not changed and are stale
> (it's recommended values for the first property change, not for the second)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18261) CapSched View: Showing warning icons to refresh or restart capsched once after configs are saved
[
https://issues.apache.org/jira/browse/AMBARI-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455698#comment-15455698
]
Hadoop QA commented on AMBARI-18261:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826624/AMBARI-18261.2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8553//console
This message is automatically generated.
> CapSched View: Showing warning icons to refresh or restart capsched once
> after configs are saved
>
>
> Key: AMBARI-18261
> URL: https://issues.apache.org/jira/browse/AMBARI-18261
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Akhil PB
>Assignee: Akhil PB
> Fix For: 2.5.0
>
> Attachments: AMBARI-18261.1.patch, AMBARI-18261.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17891) Provide stack-advisor support for Microsoft-R service
[
https://issues.apache.org/jira/browse/AMBARI-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455703#comment-15455703
]
Hadoop QA commented on AMBARI-17891:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826616/AMBARI-17891.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8554//console
This message is automatically generated.
> Provide stack-advisor support for Microsoft-R service
> -
>
> Key: AMBARI-17891
> URL: https://issues.apache.org/jira/browse/AMBARI-17891
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.4.0
>Reporter: Srimanth Gunturi
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
> Attachments: AMBARI-17891.patch, AMBARI-17891.patch
>
>
> Microsoft-R service should have stack-advisor ability to recommend component
> layout for the client component which should be installed on hosts which have:
> * NodeManagers
> * Client nodes
> The script should also validate that the client component is on these hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18287) status commands get all the *-env files irrespective of a service exists or not
[
https://issues.apache.org/jira/browse/AMBARI-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455697#comment-15455697
]
Hadoop QA commented on AMBARI-18287:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826643/AMBARI-18287.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8552//console
This message is automatically generated.
> status commands get all the *-env files irrespective of a service exists or
> not
> ---
>
> Key: AMBARI-18287
> URL: https://issues.apache.org/jira/browse/AMBARI-18287
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18287.patch
>
>
> Ambari should not send env files corresponding to the deleted services for
> the status commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18287) status commands get all the *-env files irrespective of a service exists or not
[ https://issues.apache.org/jira/browse/AMBARI-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18287: --- Attachment: (was: AMBARI-18287.patch) > status commands get all the *-env files irrespective of a service exists or > not > --- > > Key: AMBARI-18287 > URL: https://issues.apache.org/jira/browse/AMBARI-18287 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18287.patch > > > Ambari should not send env files corresponding to the deleted services for > the status commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18296) Database Consistency Check Fails With NPE With Missing Service From Stack
Jonathan Hurley created AMBARI-18296:
Summary: Database Consistency Check Fails With NPE With Missing
Service From Stack
Key: AMBARI-18296
URL: https://issues.apache.org/jira/browse/AMBARI-18296
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jonathan Hurley
Priority: Critical
Fix For: trunk
The database consistency checker can fail if a service configuration exists for
a service which is no longer on the current stack:
{code}
2016-08-31 21:52:28,082 INFO - *** Check database
started *** 2016-08-31 21:52:31,647 INFO - Checking
for configs not mapped to any cluster 2016-08-31 21:52:31,653 INFO - Checking
for configs selected more than once 2016-08-31 21:52:31,655 INFO - Checking for
hosts without state 2016-08-31 21:52:31,657 INFO - Checking host component
states count equals host component desired states count 2016-08-31 21:52:31,660
INFO - Checking services and their configs 2016-08-31 21:52:33,669 ERROR -
Unexpected error, database check failed java.lang.NullPointerException at
org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
at
org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
{code}
It seems like what happens is this query returns a service which is not defined
in the current stack:
{code}
SELECT
c.cluster_name,
cs.service_name,
cc.type_name,
sc.version
FROM clusterservices cs
JOIN serviceconfig sc
ON cs.service_name = sc.service_name
AND cs.cluster_id = sc.cluster_id
JOIN serviceconfigmapping scm
ON sc.service_config_id = scm.service_config_id
JOIN clusterconfig cc
ON scm.config_id = cc.config_id
AND sc.cluster_id = cc.cluster_id
JOIN clusters c
ON cc.cluster_id = c.cluster_id
AND sc.stack_id = c.desired_stack_id
WHERE sc.group_id IS NULL
AND sc.service_config_id = (SELECT
MAX(service_config_id)
FROM serviceconfig sc2
WHERE sc2.service_name = sc.service_name
AND sc2.cluster_id = sc.cluster_id)
GROUP BY c.cluster_name,
cs.service_name,
cc.type_name,
sc.version
{code}
Problem area of code:
{code:title=serviceInfo is null}
for (String serviceName : serviceNames) {
ServiceInfo serviceInfo = serviceInfoMap.get(serviceName);
Set configTypes =
serviceInfo.getConfigTypeAttributes().keySet();
for (String configType : configTypes) {
stackServiceConfigs.put(serviceName, configType);
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18287) status commands get all the *-env files irrespective of a service exists or not
[ https://issues.apache.org/jira/browse/AMBARI-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18287: --- Attachment: AMBARI-18287.patch > status commands get all the *-env files irrespective of a service exists or > not > --- > > Key: AMBARI-18287 > URL: https://issues.apache.org/jira/browse/AMBARI-18287 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18287.patch, AMBARI-18287.patch > > > Ambari should not send env files corresponding to the deleted services for > the status commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-11639) Ambari Admin View URL does not get properly parsed for custom versions
[ https://issues.apache.org/jira/browse/AMBARI-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li reassigned AMBARI-11639: -- Assignee: Di Li (was: Jesus Alvarez) > Ambari Admin View URL does not get properly parsed for custom versions > -- > > Key: AMBARI-11639 > URL: https://issues.apache.org/jira/browse/AMBARI-11639 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.1.0 > Environment: RHEL 6.6 >Reporter: Jesus Alvarez >Assignee: Di Li > Attachments: > 0001-AMBARI-11639-Ambari-Admin-View-URL-does-not-get-prop.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > When building a custom version of ADMIN VIEW jar with new version such as > "2.1.0_custom", the UI returns a 404 message upon redirect. > Upon loading ambari-server (http://node1.bigdata:8080) for the first time, > the URL is redirected to: > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0_custom/INSTANCE/# , which > returns a 404 missing page. > If the URL is manually changed to > http://node1.bigdata:8080/views/ADMIN_VIEW/2.1.0/INSTANCE/# , the UI loads -- > though links in ambari UI remain broken. > This appears to be caused by > latestVersion = sortedMappedVersions[sortedMappedVersions.length-1]; > and ambari.service.load_server_version ; each parsing version string > differently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18261) CapSched View: Showing warning icons to refresh or restart capsched once after configs are saved
[ https://issues.apache.org/jira/browse/AMBARI-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-18261: -- Attachment: AMBARI-18261.2.patch > CapSched View: Showing warning icons to refresh or restart capsched once > after configs are saved > > > Key: AMBARI-18261 > URL: https://issues.apache.org/jira/browse/AMBARI-18261 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18261.1.patch, AMBARI-18261.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18286) Processes children are not killed on timeout
[ https://issues.apache.org/jira/browse/AMBARI-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455339#comment-15455339 ] Hudson commented on AMBARI-18286: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5612 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5612/]) AMBARI-18286. Processes children are not killed on timeout (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dd7424f34e37987f4dedaa7de753c7ead10de53e]) * (edit) ambari-common/src/main/python/resource_management/core/shell.py * (edit) ambari-agent/src/test/python/resource_management/TestUserResource.py * (edit) ambari-common/src/main/python/resource_management/core/resources/system.py * (edit) ambari-common/src/main/python/resource_management/core/providers/system.py * (edit) ambari-agent/src/test/python/resource_management/TestGroupResource.py * (edit) ambari-common/src/main/python/resource_management/core/utils.py > Processes children are not killed on timeout > > > Key: AMBARI-18286 > URL: https://issues.apache.org/jira/browse/AMBARI-18286 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18286.patch > > > This leads to spawning a lot of processes on machines where Hive alerts run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18261) CapSched View: Showing warning icons to refresh or restart capsched once after configs are saved
[ https://issues.apache.org/jira/browse/AMBARI-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-18261: -- Attachment: (was: AMBARI-18261.2.patch) > CapSched View: Showing warning icons to refresh or restart capsched once > after configs are saved > > > Key: AMBARI-18261 > URL: https://issues.apache.org/jira/browse/AMBARI-18261 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18261.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17891) Provide stack-advisor support for Microsoft-R service
[ https://issues.apache.org/jira/browse/AMBARI-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-17891: --- Status: Patch Available (was: Open) > Provide stack-advisor support for Microsoft-R service > - > > Key: AMBARI-17891 > URL: https://issues.apache.org/jira/browse/AMBARI-17891 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Doroszlai, Attila > Fix For: 2.5.0 > > Attachments: AMBARI-17891.patch, AMBARI-17891.patch > > > Microsoft-R service should have stack-advisor ability to recommend component > layout for the client component which should be installed on hosts which have: > * NodeManagers > * Client nodes > The script should also validate that the client component is on these hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17891) Provide stack-advisor support for Microsoft-R service
[ https://issues.apache.org/jira/browse/AMBARI-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-17891: --- Attachment: AMBARI-17891.patch > Provide stack-advisor support for Microsoft-R service > - > > Key: AMBARI-17891 > URL: https://issues.apache.org/jira/browse/AMBARI-17891 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Doroszlai, Attila > Fix For: 2.5.0 > > Attachments: AMBARI-17891.patch, AMBARI-17891.patch > > > Microsoft-R service should have stack-advisor ability to recommend component > layout for the client component which should be installed on hosts which have: > * NodeManagers > * Client nodes > The script should also validate that the client component is on these hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17891) Provide stack-advisor support for Microsoft-R service
[ https://issues.apache.org/jira/browse/AMBARI-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-17891: --- Status: Open (was: Patch Available) > Provide stack-advisor support for Microsoft-R service > - > > Key: AMBARI-17891 > URL: https://issues.apache.org/jira/browse/AMBARI-17891 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Doroszlai, Attila > Fix For: 2.5.0 > > Attachments: AMBARI-17891.patch > > > Microsoft-R service should have stack-advisor ability to recommend component > layout for the client component which should be installed on hosts which have: > * NodeManagers > * Client nodes > The script should also validate that the client component is on these hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17891) Provide stack-advisor support for Microsoft-R service
[ https://issues.apache.org/jira/browse/AMBARI-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila reassigned AMBARI-17891: -- Assignee: Doroszlai, Attila (was: Srimanth Gunturi) > Provide stack-advisor support for Microsoft-R service > - > > Key: AMBARI-17891 > URL: https://issues.apache.org/jira/browse/AMBARI-17891 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Doroszlai, Attila > Fix For: 2.5.0 > > Attachments: AMBARI-17891.patch > > > Microsoft-R service should have stack-advisor ability to recommend component > layout for the client component which should be installed on hosts which have: > * NodeManagers > * Client nodes > The script should also validate that the client component is on these hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455283#comment-15455283 ] Aleksandr Kovalenko commented on AMBARI-18295: -- committed to trunk > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455282#comment-15455282 ] Aleksandr Kovalenko commented on AMBARI-18295: -- Tested patch locally. Result of running unit tests: 30134 tests complete (34 seconds) 151 tests pending > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[
https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455262#comment-15455262
]
Hadoop QA commented on AMBARI-18295:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826613/AMBARI-18295.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8551//console
This message is automatically generated.
> Dependent Configurations popup isn't changed after the subsequent property
> changes
> --
>
> Key: AMBARI-18295
> URL: https://issues.apache.org/jira/browse/AMBARI-18295
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18295.patch
>
>
> *STR:*
> 1) Deploy a cluster
> 2) Go to YARN -> Configs
> 3) Change 'Minimum Container Size (Memory)'
> 4) Click 'Show Details' to open the 'Dependent Configurations' popup.
> 5) Close the popup and change 'Minimum Container Size (Memory)' again
> 6) Open 'Dependent Configurations' popup again.
> *Result:*
> The 'Recommended values' displayed in the popup are not changed and are stale
> (it's recommended values for the first property change, not for the second)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455261#comment-15455261 ] Andrii Babiichuk commented on AMBARI-18295: --- +1 for the patch > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18295: - Status: Patch Available (was: Open) > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
[ https://issues.apache.org/jira/browse/AMBARI-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18295: - Attachment: AMBARI-18295.patch > Dependent Configurations popup isn't changed after the subsequent property > changes > -- > > Key: AMBARI-18295 > URL: https://issues.apache.org/jira/browse/AMBARI-18295 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18295.patch > > > *STR:* > 1) Deploy a cluster > 2) Go to YARN -> Configs > 3) Change 'Minimum Container Size (Memory)' > 4) Click 'Show Details' to open the 'Dependent Configurations' popup. > 5) Close the popup and change 'Minimum Container Size (Memory)' again > 6) Open 'Dependent Configurations' popup again. > *Result:* > The 'Recommended values' displayed in the popup are not changed and are stale > (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18295) Dependent Configurations popup isn't changed after the subsequent property changes
Aleksandr Kovalenko created AMBARI-18295: Summary: Dependent Configurations popup isn't changed after the subsequent property changes Key: AMBARI-18295 URL: https://issues.apache.org/jira/browse/AMBARI-18295 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 3.0.0 *STR:* 1) Deploy a cluster 2) Go to YARN -> Configs 3) Change 'Minimum Container Size (Memory)' 4) Click 'Show Details' to open the 'Dependent Configurations' popup. 5) Close the popup and change 'Minimum Container Size (Memory)' again 6) Open 'Dependent Configurations' popup again. *Result:* The 'Recommended values' displayed in the popup are not changed and are stale (it's recommended values for the first property change, not for the second) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18261) CapSched View: Showing warning icons to refresh or restart capsched once after configs are saved
[ https://issues.apache.org/jira/browse/AMBARI-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-18261: -- Attachment: AMBARI-18261.2.patch > CapSched View: Showing warning icons to refresh or restart capsched once > after configs are saved > > > Key: AMBARI-18261 > URL: https://issues.apache.org/jira/browse/AMBARI-18261 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18261.1.patch, AMBARI-18261.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455117#comment-15455117 ] Hudson commented on AMBARI-18294: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5611 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5611/]) AMBARI-18294. Ambari Server Start/Stop fails on Centos 7.1+ (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5c2a40e3e9bcb948e91cc7db2673cb4122da0d15]) * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/main/python/ambari_server_main.py > Ambari Server Start/Stop fails on Centos 7.1+ > - > > Key: AMBARI-18294 > URL: https://issues.apache.org/jira/browse/AMBARI-18294 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18294.patch > > > Brand new install on Centos 7.2 > Ambari Server 'setup' completed successfully. > [root@c7001 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > Ambari Server running with administrator privileges. > Organizing resource files at /var/lib/ambari-server/resources... > Ambari database consistency check started... > No errors were found. > Ambari database consistency check finished > Server PID at: /var/run/ambari-server/ambari-server.pid > Server out at: /var/log/ambari-server/ambari-server.out > Server log at: /var/log/ambari-server/ambari-server.log > Waiting for server start > Ambari Server 'start' completed successfully. > [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid > 12302 > 12303 > [root@c7001 ~]# ps aux | grep AmbariServer > root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c > ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > > /var/run/ambari-server/ambari-server.exitcode & > root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 > /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar > org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter notification of some alert states This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL state notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched was: By default, Ambari allow notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched was: By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Support dispatching notification of assigned alert states for script-based alert dispatcher (was: Support dispatching assigned alert states notification for script-based alert dispatcher) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18293) Enable log search for NIFI_CA component
[
https://issues.apache.org/jira/browse/AMBARI-18293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454897#comment-15454897
]
Hadoop QA commented on AMBARI-18293:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826582/AMBARI-18293.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8550//console
This message is automatically generated.
> Enable log search for NIFI_CA component
> ---
>
> Key: AMBARI-18293
> URL: https://issues.apache.org/jira/browse/AMBARI-18293
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18293.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[
https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454896#comment-15454896
]
Hadoop QA commented on AMBARI-18292:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826584/AMBARI-18292.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8549//console
This message is automatically generated.
> Support dispatching assigned alert states notification for script-based alert
> dispatcher
>
>
> Key: AMBARI-18292
> URL: https://issues.apache.org/jira/browse/AMBARI-18292
> Project: Ambari
> Issue Type: Improvement
> Components: alerts
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: 2.5.0
>
> Attachments: AMBARI-18292.patch
>
>
> By default, Ambari allow all kinds of alert states
> (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert
> dispatcher.
> However, sometimes we hope to filter some alert states notification
> This patch will resolve this by setting
> 'notification.dispatch.alert.script.states' in ambari.properties as
> following:
> #Only dispatch WARNING and CRITICAL alert notification
> notification.dispatch.alert.script.states=WARNING,CRITICAL
> If you don't set this property that means all notification will be dispatched
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18294: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 and branch-2.5 > Ambari Server Start/Stop fails on Centos 7.1+ > - > > Key: AMBARI-18294 > URL: https://issues.apache.org/jira/browse/AMBARI-18294 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18294.patch > > > Brand new install on Centos 7.2 > Ambari Server 'setup' completed successfully. > [root@c7001 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > Ambari Server running with administrator privileges. > Organizing resource files at /var/lib/ambari-server/resources... > Ambari database consistency check started... > No errors were found. > Ambari database consistency check finished > Server PID at: /var/run/ambari-server/ambari-server.pid > Server out at: /var/log/ambari-server/ambari-server.out > Server log at: /var/log/ambari-server/ambari-server.log > Waiting for server start > Ambari Server 'start' completed successfully. > [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid > 12302 > 12303 > [root@c7001 ~]# ps aux | grep AmbariServer > root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c > ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > > /var/run/ambari-server/ambari-server.exitcode & > root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 > /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar > org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[
https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454839#comment-15454839
]
Hadoop QA commented on AMBARI-18294:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12826587/AMBARI-18294.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8548//console
This message is automatically generated.
> Ambari Server Start/Stop fails on Centos 7.1+
> -
>
> Key: AMBARI-18294
> URL: https://issues.apache.org/jira/browse/AMBARI-18294
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.1
>
> Attachments: AMBARI-18294.patch
>
>
> Brand new install on Centos 7.2
> Ambari Server 'setup' completed successfully.
> [root@c7001 ~]# ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> Ambari database consistency check finished
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start
> Ambari Server 'start' completed successfully.
> [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid
> 12302
> 12303
> [root@c7001 ~]# ps aux | grep AmbariServer
> root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c
> ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3
> -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit
> -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled
> -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m
> -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djavax.security.auth.useSubjectCredsOnly=false -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar'
> org.apache.ambari.server.controller.AmbariServer >
> /var/log/ambari-server/ambari-server.out 2>&1 || echo $? >
> /var/run/ambari-server/ambari-server.exitcode &
> root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29
> /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3
> -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit
> -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled
> -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djavax.security.auth.useSubjectCredsOnly=false -cp
> /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar
> org.apache.ambari.server.controller.AmbariServer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18294: - Status: Patch Available (was: Open) > Ambari Server Start/Stop fails on Centos 7.1+ > - > > Key: AMBARI-18294 > URL: https://issues.apache.org/jira/browse/AMBARI-18294 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18294.patch > > > Brand new install on Centos 7.2 > Ambari Server 'setup' completed successfully. > [root@c7001 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > Ambari Server running with administrator privileges. > Organizing resource files at /var/lib/ambari-server/resources... > Ambari database consistency check started... > No errors were found. > Ambari database consistency check finished > Server PID at: /var/run/ambari-server/ambari-server.pid > Server out at: /var/log/ambari-server/ambari-server.out > Server log at: /var/log/ambari-server/ambari-server.log > Waiting for server start > Ambari Server 'start' completed successfully. > [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid > 12302 > 12303 > [root@c7001 ~]# ps aux | grep AmbariServer > root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c > ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > > /var/run/ambari-server/ambari-server.exitcode & > root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 > /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar > org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
Andrew Onischuk created AMBARI-18294: Summary: Ambari Server Start/Stop fails on Centos 7.1+ Key: AMBARI-18294 URL: https://issues.apache.org/jira/browse/AMBARI-18294 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.1 Attachments: AMBARI-18294.patch Brand new install on Centos 7.2 Ambari Server 'setup' completed successfully. [root@c7001 ~]# ambari-server start Using python /usr/bin/python Starting ambari-server Ambari Server running with administrator privileges. Organizing resource files at /var/lib/ambari-server/resources... Ambari database consistency check started... No errors were found. Ambari database consistency check finished Server PID at: /var/run/ambari-server/ambari-server.pid Server out at: /var/log/ambari-server/ambari-server.out Server log at: /var/log/ambari-server/ambari-server.log Waiting for server start Ambari Server 'start' completed successfully. [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid 12302 12303 [root@c7001 ~]# ps aux | grep AmbariServer root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' org.apache.ambari.server.controller.AmbariServer > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > /var/run/ambari-server/ambari-server.exitcode & root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18294: - Attachment: AMBARI-18294.patch > Ambari Server Start/Stop fails on Centos 7.1+ > - > > Key: AMBARI-18294 > URL: https://issues.apache.org/jira/browse/AMBARI-18294 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18294.patch > > > Brand new install on Centos 7.2 > Ambari Server 'setup' completed successfully. > [root@c7001 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > Ambari Server running with administrator privileges. > Organizing resource files at /var/lib/ambari-server/resources... > Ambari database consistency check started... > No errors were found. > Ambari database consistency check finished > Server PID at: /var/run/ambari-server/ambari-server.pid > Server out at: /var/log/ambari-server/ambari-server.out > Server log at: /var/log/ambari-server/ambari-server.log > Waiting for server start > Ambari Server 'start' completed successfully. > [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid > 12302 > 12303 > [root@c7001 ~]# ps aux | grep AmbariServer > root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c > ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > > /var/run/ambari-server/ambari-server.exitcode & > root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 > /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar > org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18293) Enable log search for NIFI_CA component
[ https://issues.apache.org/jira/browse/AMBARI-18293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18293: Status: Patch Available (was: In Progress) > Enable log search for NIFI_CA component > --- > > Key: AMBARI-18293 > URL: https://issues.apache.org/jira/browse/AMBARI-18293 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18293.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18293) Enable log search for NIFI_CA component
[ https://issues.apache.org/jira/browse/AMBARI-18293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18293: Attachment: AMBARI-18293.patch > Enable log search for NIFI_CA component > --- > > Key: AMBARI-18293 > URL: https://issues.apache.org/jira/browse/AMBARI-18293 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-18293.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
