[jira] [Commented] (AMBARI-14383) Add support for Ranger TagSync process as a component under RANGER
[ https://issues.apache.org/jira/browse/AMBARI-14383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225820#comment-15225820 ] Hudson commented on AMBARI-14383: - FAILURE: Integrated in Ambari-trunk-Commit #4595 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4595/]) AMBARI-14383. Add support for Ranger TagSync process as a component (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bf04d16b103e89a2d6a0d4538b47a99d3d75a772]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/tagsync-application-properties.xml * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py * ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/themes/theme_version_3.json * ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py * ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/status_params.py * ambari-common/src/main/python/resource_management/libraries/functions/constants.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py * ambari-common/src/main/python/resource_management/libraries/functions/stack_features.py * ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/ranger-tagsync-site.xml * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json > Add support for Ranger TagSync process as a component under RANGER > -- > > Key: AMBARI-14383 > URL: https://issues.apache.org/jira/browse/AMBARI-14383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.4.0 > > Attachments: AMBARI-14383.1.patch, AMBARI-14383.2.patch, > AMBARI-14383.patch > > > Ranger TagSync is a separate service that will be responsible for > synchronizing the tags from Apache Atlas into Apache Ranger (db). > This jira will track changes required to install/configure TagSync from > Ambari. > * Add Ranger TagSync component under existing RANGER service. > * The component will be a master component > * Ability to start/stop the component independently of Ranger Admin. > * Ability to install the component on any host of the cluster > * Support should be available only from HDP 2.3 > * Any other changes required in Ambari stack to support such component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15683) Background Operations window opening with avoid opening checkbox set
[ https://issues.apache.org/jira/browse/AMBARI-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-15683: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Background Operations window opening with avoid opening checkbox set > > > Key: AMBARI-15683 > URL: https://issues.apache.org/jira/browse/AMBARI-15683 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-15683.patch, AMBARI-15683_branch-2.2.patch > > > Steps: > # Deploy cluster with SmartSense. > # Open Background Operations window and set "Do not show this dialog again > when starting a background operation" checkbox. > # Go to host with SmartSense HST Agent. > # Choose "Unregister" or "Uninstall" operation for SmartSense HST Agent. > Result: Background Operation window was opened, but shouldn't. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
Vitaly Brodetskyi created AMBARI-15707:
--
Summary: Dev Deploy: Unexpected error, database check failed
Key: AMBARI-15707
URL: https://issues.apache.org/jira/browse/AMBARI-15707
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.4.0
Database check failed with log:
{noformat}
2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
com.google.inject.CreationException: Guice creation errors:
1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
while locating org.apache.ambari.server.audit.AuditLogger
for field at
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
at
org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
while locating org.apache.ambari.server.audit.AuditLogger
for field at
org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
at
org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
2 errors
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
at
com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
at com.google.inject.Guice.createInjector(Guice.java:95)
at com.google.inject.Guice.createInjector(Guice.java:72)
at com.google.inject.Guice.createInjector(Guice.java:62)
at
org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
[
https://issues.apache.org/jira/browse/AMBARI-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-15707:
---
Attachment: AMBARI-15707.patch
> Dev Deploy: Unexpected error, database check failed
> ---
>
> Key: AMBARI-15707
> URL: https://issues.apache.org/jira/browse/AMBARI-15707
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-15707.patch
>
>
> Database check failed with log:
> {noformat}
> 2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
[
https://issues.apache.org/jira/browse/AMBARI-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-15707:
---
Status: Patch Available (was: Open)
> Dev Deploy: Unexpected error, database check failed
> ---
>
> Key: AMBARI-15707
> URL: https://issues.apache.org/jira/browse/AMBARI-15707
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-15707.patch
>
>
> Database check failed with log:
> {noformat}
> 2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
[
https://issues.apache.org/jira/browse/AMBARI-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225990#comment-15225990
]
Vitaly Brodetskyi commented on AMBARI-15707:
Tested and committed to trunk.
> Dev Deploy: Unexpected error, database check failed
> ---
>
> Key: AMBARI-15707
> URL: https://issues.apache.org/jira/browse/AMBARI-15707
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-15707.patch
>
>
> Database check failed with log:
> {noformat}
> 2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
Dmytro Sen created AMBARI-15708:
---
Summary: "Wrong metrics path " exceptions for JMX metrics
Key: AMBARI-15708
URL: https://issues.apache.org/jira/browse/AMBARI-15708
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 2.2.2
{code}
04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 - Caught
exception getting JMX metrics : Can not fetch 0th element of document path
(executorsTotal._sum) from json. Wrong metrics path:
/api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for next
5 minutes
java.io.IOException: Can not fetch 0th element of document path
(executorsTotal._sum) from json. Wrong metrics path:
/api/v1/cluster/summary##executorsTotal._sum
at
org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
at
org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
at
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
at
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}
AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Attachment: AMBARI-15708-trunk_1.patch
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_1.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Status: Patch Available (was: Open)
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_1.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226005#comment-15226005
]
Hadoop QA commented on AMBARI-15708:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797031/AMBARI-15708-trunk_1.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/6200//console
This message is automatically generated.
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_1.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Attachment: (was: AMBARI-15708-trunk_1.patch)
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Attachment: AMBARI-15708-trunk_2.patch
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Status: Patch Available (was: Open)
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-15708:
Status: Open (was: Patch Available)
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226014#comment-15226014
]
Hadoop QA commented on AMBARI-15708:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797032/AMBARI-15708-trunk_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/6201//console
This message is automatically generated.
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
[
https://issues.apache.org/jira/browse/AMBARI-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-15707:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Dev Deploy: Unexpected error, database check failed
> ---
>
> Key: AMBARI-15707
> URL: https://issues.apache.org/jira/browse/AMBARI-15707
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-15707.patch
>
>
> Database check failed with log:
> {noformat}
> 2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15709) JS error on Dashboard page while fast switching pages
Oleg Nechiporenko created AMBARI-15709:
--
Summary: JS error on Dashboard page while fast switching pages
Key: AMBARI-15709
URL: https://issues.apache.org/jira/browse/AMBARI-15709
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 2.4.0
JS error appears on the Dashboard when user fast switching pages:
{{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226052#comment-15226052
]
Oleg Nechiporenko commented on AMBARI-15709:
25609 tests complete (24 seconds)
154 tests pending
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-15709:
---
Status: Patch Available (was: Open)
Patch added
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-15709:
---
Attachment: AMBARI-15709.patch
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226055#comment-15226055
]
Andrii Babiichuk commented on AMBARI-15709:
---
+1 for the patch
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226059#comment-15226059
]
Hadoop QA commented on AMBARI-15709:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797038/AMBARI-15709.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/6202//console
This message is automatically generated.
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226061#comment-15226061
]
Hadoop QA commented on AMBARI-15709:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797038/AMBARI-15709.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/6203//console
This message is automatically generated.
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
[ https://issues.apache.org/jira/browse/AMBARI-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-15710: - Attachment: AMBARI-15710.patch > Create script to export AMS metrics and re-import into AMS to visualize using > Grafana > - > > Key: AMBARI-15710 > URL: https://issues.apache.org/jira/browse/AMBARI-15710 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-15710.patch > > > Need to integrate this into 1 script and add it to ambari scripts to be used > by any support / dev person. > The output options should allow the result to be directly consumable by > grafana or allow import in to live AMS instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
Andrew Onischuk created AMBARI-15710: Summary: Create script to export AMS metrics and re-import into AMS to visualize using Grafana Key: AMBARI-15710 URL: https://issues.apache.org/jira/browse/AMBARI-15710 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-15710.patch Need to integrate this into 1 script and add it to ambari scripts to be used by any support / dev person. The output options should allow the result to be directly consumable by grafana or allow import in to live AMS instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
[ https://issues.apache.org/jira/browse/AMBARI-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-15710: - Status: Patch Available (was: Open) > Create script to export AMS metrics and re-import into AMS to visualize using > Grafana > - > > Key: AMBARI-15710 > URL: https://issues.apache.org/jira/browse/AMBARI-15710 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-15710.patch > > > Need to integrate this into 1 script and add it to ambari scripts to be used > by any support / dev person. > The output options should allow the result to be directly consumable by > grafana or allow import in to live AMS instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
[
https://issues.apache.org/jira/browse/AMBARI-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226074#comment-15226074
]
Hadoop QA commented on AMBARI-15710:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797049/AMBARI-15710.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/6204//console
This message is automatically generated.
> Create script to export AMS metrics and re-import into AMS to visualize using
> Grafana
> -
>
> Key: AMBARI-15710
> URL: https://issues.apache.org/jira/browse/AMBARI-15710
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15710.patch
>
>
> Need to integrate this into 1 script and add it to ambari scripts to be used
> by any support / dev person.
> The output options should allow the result to be directly consumable by
> grafana or allow import in to live AMS instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15711) Exception thrown when host with unsupported OS is to be mapped to cluster is silently swallowed
Andrew Onischuk created AMBARI-15711:
Summary: Exception thrown when host with unsupported OS is to be
mapped to cluster is silently swallowed
Key: AMBARI-15711
URL: https://issues.apache.org/jira/browse/AMBARI-15711
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.4.0
Attachments: AMBARI-15711.patch
When hosts are being mapped to a clusters (see
ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
matches the OS types supported by the stack that is being deployed.
If the OS type of the host is not supported than a warning message is logged
and an exception is thrown which is silently swallowed.
if (!isOsSupportedByClusterStack(cluster, host)) {
String message = "Trying to map host to cluster where stack does not"
+ " support host's os type" + ", clusterName=" + clusterName
+ ", clusterStackId=" +
cluster.getDesiredStackVersion().getStackId()
+ ", hostname=" + hostname + ", hostOsFamily=" +
host.getOsFamily();
LOG.warn(message);
throw new AmbariException(message);
}
...
This message should be logged as ERROR to make easier troubleshooting as most
of the time people search for exceptions and ERRORs in the log when looking
into issues with cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15711) Exception thrown when host with unsupported OS is to be mapped to cluster is silently swallowed
[
https://issues.apache.org/jira/browse/AMBARI-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15711:
-
Status: Patch Available (was: Open)
> Exception thrown when host with unsupported OS is to be mapped to cluster is
> silently swallowed
> ---
>
> Key: AMBARI-15711
> URL: https://issues.apache.org/jira/browse/AMBARI-15711
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15711.patch
>
>
> When hosts are being mapped to a clusters (see
> ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
> matches the OS types supported by the stack that is being deployed.
> If the OS type of the host is not supported than a warning message is logged
> and an exception is thrown which is silently swallowed.
>
>
>
>
> if (!isOsSupportedByClusterStack(cluster, host)) {
> String message = "Trying to map host to cluster where stack does
> not"
> + " support host's os type" + ", clusterName=" + clusterName
> + ", clusterStackId=" +
> cluster.getDesiredStackVersion().getStackId()
> + ", hostname=" + hostname + ", hostOsFamily=" +
> host.getOsFamily();
> LOG.warn(message);
> throw new AmbariException(message);
> }
> ...
>
> This message should be logged as ERROR to make easier troubleshooting as most
> of the time people search for exceptions and ERRORs in the log when looking
> into issues with cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15711) Exception thrown when host with unsupported OS is to be mapped to cluster is silently swallowed
[
https://issues.apache.org/jira/browse/AMBARI-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15711:
-
Attachment: AMBARI-15711.patch
> Exception thrown when host with unsupported OS is to be mapped to cluster is
> silently swallowed
> ---
>
> Key: AMBARI-15711
> URL: https://issues.apache.org/jira/browse/AMBARI-15711
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15711.patch
>
>
> When hosts are being mapped to a clusters (see
> ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
> matches the OS types supported by the stack that is being deployed.
> If the OS type of the host is not supported than a warning message is logged
> and an exception is thrown which is silently swallowed.
>
>
>
>
> if (!isOsSupportedByClusterStack(cluster, host)) {
> String message = "Trying to map host to cluster where stack does
> not"
> + " support host's os type" + ", clusterName=" + clusterName
> + ", clusterStackId=" +
> cluster.getDesiredStackVersion().getStackId()
> + ", hostname=" + hostname + ", hostOsFamily=" +
> host.getOsFamily();
> LOG.warn(message);
> throw new AmbariException(message);
> }
> ...
>
> This message should be logged as ERROR to make easier troubleshooting as most
> of the time people search for exceptions and ERRORs in the log when looking
> into issues with cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226076#comment-15226076
]
Oleg Nechiporenko commented on AMBARI-15709:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web SUCCESS [ 49.894 s]
[INFO] Ambari Admin View . FAILURE [ 7.969 s]
{noformat}
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226078#comment-15226078
]
Oleg Nechiporenko commented on AMBARI-15709:
Committed to trunk
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15711) Exception thrown when host with unsupported OS is to be mapped to cluster is silently swallowed
[
https://issues.apache.org/jira/browse/AMBARI-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226080#comment-15226080
]
Hadoop QA commented on AMBARI-15711:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797050/AMBARI-15711.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/6205//console
This message is automatically generated.
> Exception thrown when host with unsupported OS is to be mapped to cluster is
> silently swallowed
> ---
>
> Key: AMBARI-15711
> URL: https://issues.apache.org/jira/browse/AMBARI-15711
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15711.patch
>
>
> When hosts are being mapped to a clusters (see
> ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
> matches the OS types supported by the stack that is being deployed.
> If the OS type of the host is not supported than a warning message is logged
> and an exception is thrown which is silently swallowed.
>
>
>
>
> if (!isOsSupportedByClusterStack(cluster, host)) {
> String message = "Trying to map host to cluster where stack does
> not"
> + " support host's os type" + ", clusterName=" + clusterName
> + ", clusterStackId=" +
> cluster.getDesiredStackVersion().getStackId()
> + ", hostname=" + hostname + ", hostOsFamily=" +
> host.getOsFamily();
> LOG.warn(message);
> throw new AmbariException(message);
> }
> ...
>
> This message should be logged as ERROR to make easier troubleshooting as most
> of the time people search for exceptions and ERRORs in the log when looking
> into issues with cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
Andrew Onischuk created AMBARI-15712:
Summary: Flume Handler Start fails while installing without HDFS
Key: AMBARI-15712
URL: https://issues.apache.org/jira/browse/AMBARI-15712
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.2.2
Attachments: AMBARI-15712.patch
STR:
Install Ambari
Install cluster with only Flume
Flume Handler start fails. This was not see in previous runs, so it may be
intermittent.
{
"href" :
"http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
"Tasks" : {
"attempt_cnt" : 1,
"cluster_name" : "cl1",
"command" : "START",
"command_detail" : "FLUME_HANDLER START",
"end_time" : 1459753941446,
"error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
"exit_code" : 1,
"host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
"id" : 14,
"output_log" : "/var/lib/ambari-agent/data/output-14.txt",
"request_id" : 5,
"role" : "FLUME_HANDLER",
"stage_id" : 0,
"start_time" : 1459753934012,
"status" : "FAILED",
"stderr" : "Traceback (most recent call last):\n File
\"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
line 39, in \nBeforeStartHook().execute()\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
line 219, in execute\nmethod(env)\n File
\"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
line 36, in hook\ncreate_topology_script_and_mapping()\n File
\"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
line 43, in create_topology_script_and_mapping\n
create_topology_mapping()\n File
\"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
line 32, in create_topology_mapping\nonly_if=format(\"test -d
{net_topology_script_dir}\"))\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
154, in __init__\nself.env.run()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 160, in run\nself.run_action(resource, action)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 124, in run_action\nprovider_action()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
line 108, in action_create\nself.resource.group, mode=self.resource.mode,
cd_access=self.resource.cd_access)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
line 40, in _ensure_metadata\nif user or group:\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
self.name + \"' was not found in configurations
dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
parameter 'hadoop-env' was not found in configurations dictionary!",
"stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
due to not_if\n2016-04-04 07:12:19,807 - Execute[('setenforce', '0')]
{'not_if': '(! which getenforce ) || (which getenforce && getenforce | grep -q
Disabled)', 'sudo': True, 'only_if': 'test -f /selinux/enforce'}\n2016-04-04
07:12:19,813 - Skipping Execute[('setenforce', '0')] due to not_if\n2016-04-04
07:12:19,822 - File['/etc/hadoop/conf/topology_mappings.data'] {'owner':
[EMPTY], 'content': Template('topology_mappings.data.j2'), 'only_if': 'test -d
/etc/hadoop/conf', 'group': 'hadoop'}\n2016-04-04 07:12:19,827 - Writing
File['/etc/hadoop/conf/topology_mappings.data'] because it doesn't exist",
"structured_out" : { }
}
}
Artifacts:
[jira] [Updated] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15712:
-
Status: Patch Available (was: Open)
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('setenforce', '0')]
> {'not_if': '(! which getenforce ) || (which getenforce && getenforce | grep
> -q Disabled)', 'sudo': True, 'only_if': 'test -f
> /selinux/enforce'}\n2016-04-04 07:12:19,813 - Skipping Execute[('setenforce',
> '0')] due to not_if\n2016-04-04 07:12:19,822 -
> File['/etc/hadoop/conf/topology_mappings.data'] {'owner': [EMPTY], 'content':
> Template('topology_mappings.data.j2'), 'o
[jira] [Updated] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15712:
-
Attachment: AMBARI-15712.patch
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('setenforce', '0')]
> {'not_if': '(! which getenforce ) || (which getenforce && getenforce | grep
> -q Disabled)', 'sudo': True, 'only_if': 'test -f
> /selinux/enforce'}\n2016-04-04 07:12:19,813 - Skipping Execute[('setenforce',
> '0')] due to not_if\n2016-04-04 07:12:19,822 -
> File['/etc/hadoop/conf/topology_mappings.data'] {'owner': [EMPTY], 'content':
> Template('topology_mappings.data.j2'), 'only_if
[jira] [Commented] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226086#comment-15226086
]
Hadoop QA commented on AMBARI-15712:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797052/AMBARI-15712.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/6206//console
This message is automatically generated.
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('se
[jira] [Reopened] (AMBARI-14383) Add support for Ranger TagSync process as a component under RANGER
[
https://issues.apache.org/jira/browse/AMBARI-14383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen reopened AMBARI-14383:
-
This has been reverted, it breaks unit tests
{code}
Ran 253 tests in 6.096s
OK
--
Failed tests:
FAIL: test_hook_default_conf_select (test_after_install.TestHookAfterInstall)
--
Traceback (most recent call last):
File "/tmp/inc-ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
in patched
return func(*args, **keywargs)
File
"/tmp/inc-ambari/ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py",
line 85, in test_hook_default_conf_sele
ct
sudo = True)
File
"/tmp/inc-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 253, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: Tuples differ: ('cp', '-R', '-p', '/etc/knox/... != ('cp',
'-R', '-p', '/etc/range...
First differing element 3:
/etc/knox/conf
/etc/ranger/kms/conf
- ('cp', '-R', '-p', '/etc/knox/conf', '/etc/knox/conf.backup')
? ^^^ ^^^
+ ('cp', '-R', '-p', '/etc/ranger/kms/conf', '/etc/ranger/kms/conf.backup')
? +++ ^^ +++ ^^
FAIL: test_hook_default_conf_select_with_error
(test_after_install.TestHookAfterInstall)
--
Traceback (most recent call last):
File "/tmp/inc-ambari/ambari-common/src/test/python/mock/mock.py", line 1199,
in patched
return func(*args, **keywargs)
File
"/tmp/inc-ambari/ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py",
line 332, in test_hook_default_conf_sel
ect_with_error
sudo = True)
File
"/tmp/inc-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 253, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: Tuples differ: ('cp', '-R', '-p', '/etc/knox/... != ('cp',
'-R', '-p', '/etc/range...
First differing element 3:
/etc/knox/conf
/etc/ranger/kms/conf
- ('cp', '-R', '-p', '/etc/knox/conf', '/etc/knox/conf.backup')
? ^^^ ^^^
+ ('cp', '-R', '-p', '/etc/ranger/kms/conf', '/etc/ranger/kms/conf.backup')
? +++ ^^ +++ ^^
{code}
Please follow the contribution process
https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute
Get +1 from another committer and ensure, that all unit tests passed before
commit
> Add support for Ranger TagSync process as a component under RANGER
> --
>
> Key: AMBARI-14383
> URL: https://issues.apache.org/jira/browse/AMBARI-14383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-14383.1.patch, AMBARI-14383.2.patch,
> AMBARI-14383.patch
>
>
> Ranger TagSync is a separate service that will be responsible for
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> This jira will track changes required to install/configure TagSync from
> Ambari.
> * Add Ranger TagSync component under existing RANGER service.
> * The component will be a master component
> * Ability to start/stop the component independently of Ranger Admin.
> * Ability to install the component on any host of the cluster
> * Support should be available only from HDP 2.3
> * Any other changes required in Ambari stack to support such component
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226115#comment-15226115
]
Hadoop QA commented on AMBARI-15708:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797032/AMBARI-15708-trunk_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/6207//console
This message is automatically generated.
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15697) Allow skipping creation of repo files
[ https://issues.apache.org/jira/browse/AMBARI-15697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-15697: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Allow skipping creation of repo files > - > > Key: AMBARI-15697 > URL: https://issues.apache.org/jira/browse/AMBARI-15697 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15697.patch > > > Support the case of RH Satellite and don't create .repo files where Ambari > shouldn't manage the OS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226127#comment-15226127
]
Hadoop QA commented on AMBARI-15708:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797032/AMBARI-15708-trunk_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/6208//console
This message is automatically generated.
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226129#comment-15226129
]
Hadoop QA commented on AMBARI-15712:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797052/AMBARI-15712.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/6209//console
This message is automatically generated.
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('se
[jira] [Commented] (AMBARI-15711) Exception thrown when host with unsupported OS is to be mapped to cluster is silently swallowed
[
https://issues.apache.org/jira/browse/AMBARI-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226131#comment-15226131
]
Hadoop QA commented on AMBARI-15711:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797050/AMBARI-15711.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/6210//console
This message is automatically generated.
> Exception thrown when host with unsupported OS is to be mapped to cluster is
> silently swallowed
> ---
>
> Key: AMBARI-15711
> URL: https://issues.apache.org/jira/browse/AMBARI-15711
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15711.patch
>
>
> When hosts are being mapped to a clusters (see
> ClustersImpl.java:mapHostToCluster) it verifies if the OS type of the host
> matches the OS types supported by the stack that is being deployed.
> If the OS type of the host is not supported than a warning message is logged
> and an exception is thrown which is silently swallowed.
>
>
>
>
> if (!isOsSupportedByClusterStack(cluster, host)) {
> String message = "Trying to map host to cluster where stack does
> not"
> + " support host's os type" + ", clusterName=" + clusterName
> + ", clusterStackId=" +
> cluster.getDesiredStackVersion().getStackId()
> + ", hostname=" + hostname + ", hostOsFamily=" +
> host.getOsFamily();
> LOG.warn(message);
> throw new AmbariException(message);
> }
> ...
>
> This message should be logged as ERROR to make easier troubleshooting as most
> of the time people search for exceptions and ERRORs in the log when looking
> into issues with cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15709) JS error on Dashboard page while fast switching pages
[
https://issues.apache.org/jira/browse/AMBARI-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226133#comment-15226133
]
Hadoop QA commented on AMBARI-15709:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797038/AMBARI-15709.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/6211//console
This message is automatically generated.
> JS error on Dashboard page while fast switching pages
> -
>
> Key: AMBARI-15709
> URL: https://issues.apache.org/jira/browse/AMBARI-15709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15709.patch
>
>
> JS error appears on the Dashboard when user fast switching pages:
> {{Uncaught Error: assertion failed: `namespace` should be defined}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
[
https://issues.apache.org/jira/browse/AMBARI-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226136#comment-15226136
]
Hadoop QA commented on AMBARI-15710:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797049/AMBARI-15710.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/6212//console
This message is automatically generated.
> Create script to export AMS metrics and re-import into AMS to visualize using
> Grafana
> -
>
> Key: AMBARI-15710
> URL: https://issues.apache.org/jira/browse/AMBARI-15710
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15710.patch
>
>
> Need to integrate this into 1 script and add it to ambari scripts to be used
> by any support / dev person.
> The output options should allow the result to be directly consumable by
> grafana or allow import in to live AMS instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15666) Add visibility attribute into SCRIPT params
[
https://issues.apache.org/jira/browse/AMBARI-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15666:
-
Status: Patch Available (was: Reopened)
> Add visibility attribute into SCRIPT params
> ---
>
> Key: AMBARI-15666
> URL: https://issues.apache.org/jira/browse/AMBARI-15666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15666.patch, AMBARI-15666.patch
>
>
> As discussed...Need an attribute "visibility" that can optionally be included
> in SCRIPT params.
> 1) If omitted, the param is shown in the UI
> 2) If set "visibility":"hidden", the param is hidden in the UI
> 3) If set "visibility":"readonly", the param is shown in the UI but not
> edtiable
> {code}
> "parameters": [
> {
> "name": "connection.timeout",
> "display_name": "Connection Timeout",
> "value": 5.0,
> "type": "NUMERIC",
> "description": "The maximum time before this alert is considered to be
> CRITICAL",
> "units": "seconds",
> "threshold": "CRITICAL"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15666) Add visibility attribute into SCRIPT params
[
https://issues.apache.org/jira/browse/AMBARI-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15666:
-
Attachment: AMBARI-15666.patch
> Add visibility attribute into SCRIPT params
> ---
>
> Key: AMBARI-15666
> URL: https://issues.apache.org/jira/browse/AMBARI-15666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15666.patch, AMBARI-15666.patch
>
>
> As discussed...Need an attribute "visibility" that can optionally be included
> in SCRIPT params.
> 1) If omitted, the param is shown in the UI
> 2) If set "visibility":"hidden", the param is hidden in the UI
> 3) If set "visibility":"readonly", the param is shown in the UI but not
> edtiable
> {code}
> "parameters": [
> {
> "name": "connection.timeout",
> "display_name": "Connection Timeout",
> "value": 5.0,
> "type": "NUMERIC",
> "description": "The maximum time before this alert is considered to be
> CRITICAL",
> "units": "seconds",
> "threshold": "CRITICAL"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15666) Add visibility attribute into SCRIPT params
[
https://issues.apache.org/jira/browse/AMBARI-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226138#comment-15226138
]
Hadoop QA commented on AMBARI-15666:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797054/AMBARI-15666.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/6213//console
This message is automatically generated.
> Add visibility attribute into SCRIPT params
> ---
>
> Key: AMBARI-15666
> URL: https://issues.apache.org/jira/browse/AMBARI-15666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15666.patch, AMBARI-15666.patch
>
>
> As discussed...Need an attribute "visibility" that can optionally be included
> in SCRIPT params.
> 1) If omitted, the param is shown in the UI
> 2) If set "visibility":"hidden", the param is hidden in the UI
> 3) If set "visibility":"readonly", the param is shown in the UI but not
> edtiable
> {code}
> "parameters": [
> {
> "name": "connection.timeout",
> "display_name": "Connection Timeout",
> "value": 5.0,
> "type": "NUMERIC",
> "description": "The maximum time before this alert is considered to be
> CRITICAL",
> "units": "seconds",
> "threshold": "CRITICAL"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-15649: -- Issue still happens on a hash that's newer than b019e1dcf22b1c79c8fef0f63979b7289f0c66ce AMBARI-15649. Service Actions button is missing (alexantonenko) > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14084) Ambari Views : each view should have separate log file for better troubleshooting
[ https://issues.apache.org/jira/browse/AMBARI-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226143#comment-15226143 ] Hudson commented on AMBARI-14084: - FAILURE: Integrated in Ambari-branch-2.2 #590 (See [https://builds.apache.org/job/Ambari-branch-2.2/590/]) AMBARI-14084. Ambari Views : each view should have separate log file for (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4aa6524aff56ac100a8d454b74fb14079bf85d2c]) * contrib/views/storm/src/main/resources/view.log4j.properties * contrib/views/pig/src/main/resources/view.log4j.properties * contrib/views/capacity-scheduler/src/main/resources/view.log4j.properties * contrib/views/slider/src/main/resources/view.log4j.properties * contrib/views/hive/src/main/resources/view.log4j.properties * contrib/views/tez/src/main/resources/view.log4j.properties * contrib/views/jobs/src/main/resources/view.log4j.properties * contrib/views/files/src/main/resources/view.log4j.properties * ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java > Ambari Views : each view should have separate log file for better > troubleshooting > - > > Key: AMBARI-14084 > URL: https://issues.apache.org/jira/browse/AMBARI-14084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.2.2 > > Attachments: AMBARI-14084_branch-2.1.patch, > AMBARI-14084_branch-2.2.patch, AMBARI-14084_branch-2.2_1.patch, > AMBARI-14084_branch-2.2_2.patch > > > There should be separate log files for hive view, tez view for better > debbugability -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Status: Patch Available (was: Reopened) > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Attachment: AMBARI-15649.patch > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15710) Create script to export AMS metrics and re-import into AMS to visualize using Grafana
[
https://issues.apache.org/jira/browse/AMBARI-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226145#comment-15226145
]
Andrew Onischuk commented on AMBARI-15710:
--
Non related failure. Admin view is broken:
{noformat}
[INFO] Ambari Main ... SUCCESS [ 3.005 s]
[INFO] Apache Ambari Project POM . SUCCESS [ 0.058 s]
[INFO] Ambari Web SUCCESS [ 37.674 s]
[INFO] Ambari Views .. SUCCESS [ 1.300 s]
[INFO] Ambari Admin View . FAILURE [ 6.319 s]
[INFO] ambari-metrics SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
{noformat}
Ran python UT:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 143 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Server . SUCCESS [1:41.922s]
[INFO] Ambari Agent .. SUCCESS [20.134s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:02.746s
[INFO] Finished at: Tue Apr 05 15:16:50 EEST 2016
[INFO] Final Memory: 138M/900M
[INFO]
{noformat}
> Create script to export AMS metrics and re-import into AMS to visualize using
> Grafana
> -
>
> Key: AMBARI-15710
> URL: https://issues.apache.org/jira/browse/AMBARI-15710
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15710.patch
>
>
> Need to integrate this into 1 script and add it to ambari scripts to be used
> by any support / dev person.
> The output options should allow the result to be directly consumable by
> grafana or allow import in to live AMS instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[
https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226147#comment-15226147
]
Hadoop QA commented on AMBARI-15649:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797056/AMBARI-15649.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/6214//console
This message is automatically generated.
> Service Actions button is missing
> -
>
> Key: AMBARI-15649
> URL: https://issues.apache.org/jira/browse/AMBARI-15649
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15649.patch, AMBARI-15649.patch
>
>
> After couple of seconds Service Actions button is hidden
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226146#comment-15226146
]
Andrew Onischuk commented on AMBARI-15712:
--
Non related failure. Admin view is broken:
{noformat}
[INFO] Ambari Main ... SUCCESS [ 3.005 s]
[INFO] Apache Ambari Project POM . SUCCESS [ 0.058 s]
[INFO] Ambari Web SUCCESS [ 37.674 s]
[INFO] Ambari Views .. SUCCESS [ 1.300 s]
[INFO] Ambari Admin View . FAILURE [ 6.319 s]
[INFO] ambari-metrics SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
{noformat}
Run UT:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 143 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Server . SUCCESS [1:41.922s]
[INFO] Ambari Agent .. SUCCESS [20.134s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:02.746s
[INFO] Finished at: Tue Apr 05 15:16:50 EEST 2016
[INFO] Final Memory: 138M/900M
[INFO]
{noformat}
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations di
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Attachment: (was: AMBARI-15649.patch) > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Status: Patch Available (was: Open) > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Status: Open (was: Patch Available) > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Attachment: AMBARI-15649_updated.patch > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
Andrew Onischuk created AMBARI-15713:
Summary: Starting MapR History Server Fails When NameNode is SSL
Key: AMBARI-15713
URL: https://issues.apache.org/jira/browse/AMBARI-15713
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.4.0
Attachments: AMBARI-15713.patch
The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
property. As a result, when starting components like MapR History Server, they
will fail when NameNode is protected by SSL:
2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
/bin/bash -c 'curl --negotiate -u : -s
'"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
line 38, in get_value_from_jmx
_, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
line 49, in get_user_call_output
func_result = func(shell.as_user(command_string, user), quiet=quiet,
**call_kwargs)
File
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70,
in inner
result = function(command, **kwargs)
File
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92,
in checked_call
tries=tries, try_sleep=try_sleep)
File
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140,
in _call_wrapper
result = _call(command, **kwargs_copy)
File
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 291,
in _call
raise Fail(err_msg)
Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15713:
-
Status: Patch Available (was: Open)
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226150#comment-15226150 ] Oleg Nechiporenko commented on AMBARI-15649: +1 for patch > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15713:
-
Attachment: AMBARI-15713.patch
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[
https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226153#comment-15226153
]
Hadoop QA commented on AMBARI-15649:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797057/AMBARI-15649_updated.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/6215//console
This message is automatically generated.
> Service Actions button is missing
> -
>
> Key: AMBARI-15649
> URL: https://issues.apache.org/jira/browse/AMBARI-15649
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch
>
>
> After couple of seconds Service Actions button is hidden
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226154#comment-15226154
]
Hadoop QA commented on AMBARI-15713:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797058/AMBARI-15713.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/6216//console
This message is automatically generated.
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14084) Ambari Views : each view should have separate log file for better troubleshooting
[ https://issues.apache.org/jira/browse/AMBARI-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-14084: --- Attachment: AMBARI-14084_trunk.patch attached new patch to resolve merge conflicts of trunk AMBARI-14084_trunk.patch > Ambari Views : each view should have separate log file for better > troubleshooting > - > > Key: AMBARI-14084 > URL: https://issues.apache.org/jira/browse/AMBARI-14084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.2.2 > > Attachments: AMBARI-14084_branch-2.1.patch, > AMBARI-14084_branch-2.2.patch, AMBARI-14084_branch-2.2_1.patch, > AMBARI-14084_branch-2.2_2.patch, AMBARI-14084_trunk.patch > > > There should be separate log files for hive view, tez view for better > debbugability -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226167#comment-15226167 ] Antonenko Alexander commented on AMBARI-15649: -- Hadoop QA is failing to compile ambari-admin, and because of that cannot compile ambari web trunk local UT results after applying patch: 24576 tests complete (20 seconds) 145 tests pending Rat check passed on trunk > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15714) Express Upgrade hung after FAILED step is retried
Myroslav Papirkovskyi created AMBARI-15714:
--
Summary: Express Upgrade hung after FAILED step is retried
Key: AMBARI-15714
URL: https://issues.apache.org/jira/browse/AMBARI-15714
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Critical
Fix For: 2.2.2
*Steps:*
# Start Express Upgrade from HDP 2.4.0.0 to 2.4.2.0-130
# Reach till backup the Hive Metastore message and hit Proceed
# Stop Ambari agent on one of the HBase RegionServer host
(os-r7-kwjvku-ambari-eu-4-4.novalocal on the current cluster)
# Wait for EU to report failure (status as HOLDING_TIMEDOUT)
# Start ambari-agent on the RS host and wait 60 secs. for the heartbeat to be
operational
# Retry the failed step in EU wizard
*Result*
EU hangs
ambari-server logs report below:
{code}
05 Apr 2016 08:09:26,526 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:157 -
Heartbeat lost from host os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,563 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component SECONDARY_NAMENODE on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,566 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component HISTORYSERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,568 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component HIVE_METASTORE on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,571 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component WEBHCAT_SERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,574 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component HIVE_SERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,577 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component OOZIE_SERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,580 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,583 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component DRPC_SERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,585 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component KAFKA_BROKER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,589 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component SPARK_JOBHISTORYSERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,592 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component METRICS_GRAFANA on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,595 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component DATANODE on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,597 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component NFS_GATEWAY on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,600 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component NODEMANAGER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,603 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component HBASE_REGIONSERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,606 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component SUPERVISOR on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,609 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component FLUME_HANDLER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,611 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component SPARK_THRIFTSERVER on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,615 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component METRICS_MONITOR on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:26,618 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172 -
Setting component state to UNKNOWN for component HST_AGENT on
os-r7-kwjvku-ambari-eu-4-4.novalocal
05 Apr 2016 08:09:27,571 INFO [ambari-action-scheduler] ActionScheduler:702 -
Host:os-r7-kwjvku-ambari-e
[jira] [Updated] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15712:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.2
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('setenforce', '0')]
> {'not_if': '(! which getenforce ) || (which getenforce && getenforce | grep
> -q Disabled)', 'sudo': True, 'only_if': 'test -f
> /selinux/enforce'}\n2016-04-04 07:12:19,813 - Skipping Execute[('setenforce',
> '0')] due to not_if\n2016-04-04 07:12:19,822 -
> File['/etc/hadoop/conf/topology_mappings.data'] {'owner':
[jira] [Commented] (AMBARI-15666) Add visibility attribute into SCRIPT params
[
https://issues.apache.org/jira/browse/AMBARI-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226207#comment-15226207
]
Andrew Onischuk commented on AMBARI-15666:
--
This failing for the jobs on BAO, is problem in ambari-admin and not related to
the patch.
Ran the tests manually:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views .. SUCCESS [2.687s]
[INFO] Ambari Metrics Common . SUCCESS [2.131s]
[INFO] Ambari Server . SUCCESS [53:34.339s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 53:39.950s
[INFO] Finished at: Wed Apr 5 10:27:48 UTC 2016
[INFO] Final Memory: 65M/983M
[INFO]
{noformat}
> Add visibility attribute into SCRIPT params
> ---
>
> Key: AMBARI-15666
> URL: https://issues.apache.org/jira/browse/AMBARI-15666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15666.patch, AMBARI-15666.patch
>
>
> As discussed...Need an attribute "visibility" that can optionally be included
> in SCRIPT params.
> 1) If omitted, the param is shown in the UI
> 2) If set "visibility":"hidden", the param is hidden in the UI
> 3) If set "visibility":"readonly", the param is shown in the UI but not
> edtiable
> {code}
> "parameters": [
> {
> "name": "connection.timeout",
> "display_name": "Connection Timeout",
> "value": 5.0,
> "type": "NUMERIC",
> "description": "The maximum time before this alert is considered to be
> CRITICAL",
> "units": "seconds",
> "threshold": "CRITICAL"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15666) Add visibility attribute into SCRIPT params
[
https://issues.apache.org/jira/browse/AMBARI-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15666:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Add visibility attribute into SCRIPT params
> ---
>
> Key: AMBARI-15666
> URL: https://issues.apache.org/jira/browse/AMBARI-15666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15666.patch, AMBARI-15666.patch
>
>
> As discussed...Need an attribute "visibility" that can optionally be included
> in SCRIPT params.
> 1) If omitted, the param is shown in the UI
> 2) If set "visibility":"hidden", the param is hidden in the UI
> 3) If set "visibility":"readonly", the param is shown in the UI but not
> edtiable
> {code}
> "parameters": [
> {
> "name": "connection.timeout",
> "display_name": "Connection Timeout",
> "value": 5.0,
> "type": "NUMERIC",
> "description": "The maximum time before this alert is considered to be
> CRITICAL",
> "units": "seconds",
> "threshold": "CRITICAL"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226216#comment-15226216
]
Andrew Onischuk commented on AMBARI-15713:
--
Non related failure. Admin view is broken:
{noformat}
[INFO] Ambari Main ... SUCCESS [ 3.005 s]
[INFO] Apache Ambari Project POM . SUCCESS [ 0.058 s]
[INFO] Ambari Web SUCCESS [ 37.674 s]
[INFO] Ambari Views .. SUCCESS [ 1.300 s]
[INFO] Ambari Admin View . FAILURE [ 6.319 s]
[INFO] ambari-metrics SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
{noformat}
UT:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 143 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Server . SUCCESS [1:37.423s]
[INFO] Ambari Agent .. SUCCESS [23.345s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:08.431s
[INFO] Finished at: Tue Apr 05 15:20:36 EEST 2016
[INFO] Final Memory: 138M/900M
[INFO]
{noformat}
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15714) Express Upgrade hung after FAILED step is retried
[
https://issues.apache.org/jira/browse/AMBARI-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi updated AMBARI-15714:
---
Status: Patch Available (was: Open)
> Express Upgrade hung after FAILED step is retried
> -
>
> Key: AMBARI-15714
> URL: https://issues.apache.org/jira/browse/AMBARI-15714
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15714.patch
>
>
> *Steps:*
> # Start Express Upgrade from HDP 2.4.0.0 to 2.4.2.0-130
> # Reach till backup the Hive Metastore message and hit Proceed
> # Stop Ambari agent on one of the HBase RegionServer host
> (os-r7-kwjvku-ambari-eu-4-4.novalocal on the current cluster)
> # Wait for EU to report failure (status as HOLDING_TIMEDOUT)
> # Start ambari-agent on the RS host and wait 60 secs. for the heartbeat to be
> operational
> # Retry the failed step in EU wizard
>
> *Result*
> EU hangs
> ambari-server logs report below:
> {code}
> 05 Apr 2016 08:09:26,526 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:157
> - Heartbeat lost from host os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,563 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SECONDARY_NAMENODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,566 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,568 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_METASTORE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,571 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component WEBHCAT_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,574 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,577 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component OOZIE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,580 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,583 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DRPC_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,585 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component KAFKA_BROKER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,589 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SPARK_JOBHISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,592 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component METRICS_GRAFANA on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,595 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DATANODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,597 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NFS_GATEWAY on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,600 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NODEMANAGER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,603 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HBASE_REGIONSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,606 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SUPERVISOR on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,609 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component FLUME_HANDLER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,611 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SPARK_THRIFTSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,615 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:1
[jira] [Updated] (AMBARI-15714) Express Upgrade hung after FAILED step is retried
[
https://issues.apache.org/jira/browse/AMBARI-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi updated AMBARI-15714:
---
Attachment: AMBARI-15714.patch
> Express Upgrade hung after FAILED step is retried
> -
>
> Key: AMBARI-15714
> URL: https://issues.apache.org/jira/browse/AMBARI-15714
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15714.patch
>
>
> *Steps:*
> # Start Express Upgrade from HDP 2.4.0.0 to 2.4.2.0-130
> # Reach till backup the Hive Metastore message and hit Proceed
> # Stop Ambari agent on one of the HBase RegionServer host
> (os-r7-kwjvku-ambari-eu-4-4.novalocal on the current cluster)
> # Wait for EU to report failure (status as HOLDING_TIMEDOUT)
> # Start ambari-agent on the RS host and wait 60 secs. for the heartbeat to be
> operational
> # Retry the failed step in EU wizard
>
> *Result*
> EU hangs
> ambari-server logs report below:
> {code}
> 05 Apr 2016 08:09:26,526 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:157
> - Heartbeat lost from host os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,563 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SECONDARY_NAMENODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,566 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,568 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_METASTORE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,571 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component WEBHCAT_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,574 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,577 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component OOZIE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,580 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,583 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DRPC_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,585 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component KAFKA_BROKER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,589 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SPARK_JOBHISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,592 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component METRICS_GRAFANA on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,595 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DATANODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,597 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NFS_GATEWAY on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,600 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NODEMANAGER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,603 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HBASE_REGIONSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,606 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SUPERVISOR on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,609 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component FLUME_HANDLER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,611 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SPARK_THRIFTSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,615 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
>
[jira] [Commented] (AMBARI-15712) Flume Handler Start fails while installing without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226300#comment-15226300
]
Hudson commented on AMBARI-15712:
-
FAILURE: Integrated in Ambari-branch-2.2 #591 (See
[https://builds.apache.org/job/Ambari-branch-2.2/591/])
AMBARI-15712. Flume Handler Start fails while installing without HDFS
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dfac4b98cd557b30071013d69aa12feeb27838d0])
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py
> Flume Handler Start fails while installing without HDFS
> ---
>
> Key: AMBARI-15712
> URL: https://issues.apache.org/jira/browse/AMBARI-15712
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15712.patch
>
>
> STR:
> Install Ambari
> Install cluster with only Flume
> Flume Handler start fails. This was not see in previous runs, so it may be
> intermittent.
>
>
>
> {
> "href" :
> "http://172.22.74.255:8080/api/v1/clusters/cl1/requests/5/tasks/14";,
> "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "START",
> "command_detail" : "FLUME_HANDLER START",
> "end_time" : 1459753941446,
> "error_log" : "/var/lib/ambari-agent/data/errors-14.txt",
> "exit_code" : 1,
> "host_name" : "os-d7-ngzvlu-ambari-se-serv-2-2.novalocal",
> "id" : 14,
> "output_log" : "/var/lib/ambari-agent/data/output-14.txt",
> "request_id" : 5,
> "role" : "FLUME_HANDLER",
> "stage_id" : 0,
> "start_time" : 1459753934012,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 39, in \nBeforeStartHook().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py\",
> line 36, in hook\ncreate_topology_script_and_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 43, in create_topology_script_and_mapping\n
> create_topology_mapping()\n File
> \"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py\",
> line 32, in create_topology_mapping\nonly_if=format(\"test -d
> {net_topology_script_dir}\"))\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 108, in action_create\nself.resource.group,
> mode=self.resource.mode, cd_access=self.resource.cd_access)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 40, in _ensure_metadata\nif user or group:\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 81, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'hadoop-env' was not found in configurations dictionary!",
> "stdout" : "2016-04-04 07:12:19,785 - Group['hadoop'] {}\n2016-04-04
> 07:12:19,787 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups':
> True, 'groups': ['users']}\n2016-04-04 07:12:19,788 - User['flume'] {'gid':
> 'hadoop', 'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}\n2016-04-04
> 07:12:19,789 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] {'content':
> StaticFile('changeToSecureUid.sh'), 'mode': 0555}\n2016-04-04 07:12:19,791 -
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}\n2016-04-04
> 07:12:19,796 - Skipping Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> due to not_if\n2016-04-04 07:12:19,807 - Execute[('setenforce
[jira] [Commented] (AMBARI-15714) Express Upgrade hung after FAILED step is retried
[
https://issues.apache.org/jira/browse/AMBARI-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226302#comment-15226302
]
Hadoop QA commented on AMBARI-15714:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797066/AMBARI-15714.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/6217//console
This message is automatically generated.
> Express Upgrade hung after FAILED step is retried
> -
>
> Key: AMBARI-15714
> URL: https://issues.apache.org/jira/browse/AMBARI-15714
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15714.patch
>
>
> *Steps:*
> # Start Express Upgrade from HDP 2.4.0.0 to 2.4.2.0-130
> # Reach till backup the Hive Metastore message and hit Proceed
> # Stop Ambari agent on one of the HBase RegionServer host
> (os-r7-kwjvku-ambari-eu-4-4.novalocal on the current cluster)
> # Wait for EU to report failure (status as HOLDING_TIMEDOUT)
> # Start ambari-agent on the RS host and wait 60 secs. for the heartbeat to be
> operational
> # Retry the failed step in EU wizard
>
> *Result*
> EU hangs
> ambari-server logs report below:
> {code}
> 05 Apr 2016 08:09:26,526 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:157
> - Heartbeat lost from host os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,563 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SECONDARY_NAMENODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,566 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,568 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_METASTORE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,571 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component WEBHCAT_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,574 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HIVE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,577 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component OOZIE_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,580 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,583 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DRPC_SERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,585 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component KAFKA_BROKER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,589 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SPARK_JOBHISTORYSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,592 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component METRICS_GRAFANA on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,595 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component DATANODE on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,597 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NFS_GATEWAY on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,600 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component NODEMANAGER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,603 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component HBASE_REGIONSERVER on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,606 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:172
> - Setting component state to UNKNOWN for component SUPERVISOR on
> os-r7-kwjvku-ambari-eu-4-4.novalocal
> 05 Apr 2016 08:09:26,609 WARN [ambari-hearbeat-monitor] HeartbeatMoni
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[
https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226308#comment-15226308
]
Hadoop QA commented on AMBARI-15649:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797057/AMBARI-15649_updated.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/6219//console
This message is automatically generated.
> Service Actions button is missing
> -
>
> Key: AMBARI-15649
> URL: https://issues.apache.org/jira/browse/AMBARI-15649
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch
>
>
> After couple of seconds Service Actions button is hidden
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14084) Ambari Views : each view should have separate log file for better troubleshooting
[
https://issues.apache.org/jira/browse/AMBARI-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226309#comment-15226309
]
Hadoop QA commented on AMBARI-14084:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797059/AMBARI-14084_trunk.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/6220//console
This message is automatically generated.
> Ambari Views : each view should have separate log file for better
> troubleshooting
> -
>
> Key: AMBARI-14084
> URL: https://issues.apache.org/jira/browse/AMBARI-14084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.2.2
>
> Attachments: AMBARI-14084_branch-2.1.patch,
> AMBARI-14084_branch-2.2.patch, AMBARI-14084_branch-2.2_1.patch,
> AMBARI-14084_branch-2.2_2.patch, AMBARI-14084_trunk.patch
>
>
> There should be separate log files for hive view, tez view for better
> debbugability
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226313#comment-15226313
]
Dmytro Sen commented on AMBARI-15708:
-
All tests passed locally
{code}
[INFO] Ambari Views .. SUCCESS [3.926s]
[INFO] Ambari Server . SUCCESS
[1:44:09.044s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{code}
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226305#comment-15226305
]
Hadoop QA commented on AMBARI-15713:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797058/AMBARI-15713.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/6218//console
This message is automatically generated.
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15707) Dev Deploy: Unexpected error, database check failed
[
https://issues.apache.org/jira/browse/AMBARI-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226304#comment-15226304
]
Hudson commented on AMBARI-15707:
-
ABORTED: Integrated in Ambari-trunk-Commit #4596 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4596/])
AMBARI-15707. Dev Deploy: Unexpected error, database check (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=074fe227b7fb53c5d565278c83411d02cd7f1e1b])
*
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDatabaseHelper.java
> Dev Deploy: Unexpected error, database check failed
> ---
>
> Key: AMBARI-15707
> URL: https://issues.apache.org/jira/browse/AMBARI-15707
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-15707.patch
>
>
> Database check failed with log:
> {noformat}
> 2016-04-04 05:31:05,522 ERROR - Unexpected error, database check failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:325)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:524)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.checks.CheckDatabaseHelper.main(CheckDatabaseHelper.java:523)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name
[ https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15703: --- Status: Open (was: Patch Available) > HostResourceProvider should include maintenance_state when a request is made > directly with the host name > > > Key: AMBARI-15703 > URL: https://issues.apache.org/jira/browse/AMBARI-15703 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb45714.patch > > > The property ** maintenance_state ** is not available in host response when > making a request directly on the host instead of via the clusters. > curl -u admin:admin -H "X-Requested-By: ambari" -X GET > http://localhost:8080/api/v1/hosts/c6403.ambari.apache.org > The above query does not return maintenance_state. > The following query does: > http://c6403.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6403.ambari.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name
[ https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15703: --- Status: Patch Available (was: Open) > HostResourceProvider should include maintenance_state when a request is made > directly with the host name > > > Key: AMBARI-15703 > URL: https://issues.apache.org/jira/browse/AMBARI-15703 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb45714.patch > > > The property ** maintenance_state ** is not available in host response when > making a request directly on the host instead of via the clusters. > curl -u admin:admin -H "X-Requested-By: ambari" -X GET > http://localhost:8080/api/v1/hosts/c6403.ambari.apache.org > The above query does not return maintenance_state. > The following query does: > http://c6403.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6403.ambari.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name
[ https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15703: --- Attachment: rb45714.patch > HostResourceProvider should include maintenance_state when a request is made > directly with the host name > > > Key: AMBARI-15703 > URL: https://issues.apache.org/jira/browse/AMBARI-15703 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb45714.patch > > > The property ** maintenance_state ** is not available in host response when > making a request directly on the host instead of via the clusters. > curl -u admin:admin -H "X-Requested-By: ambari" -X GET > http://localhost:8080/api/v1/hosts/c6403.ambari.apache.org > The above query does not return maintenance_state. > The following query does: > http://c6403.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6403.ambari.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name
[ https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15703: --- Attachment: (was: rb45714.patch) > HostResourceProvider should include maintenance_state when a request is made > directly with the host name > > > Key: AMBARI-15703 > URL: https://issues.apache.org/jira/browse/AMBARI-15703 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb45714.patch > > > The property ** maintenance_state ** is not available in host response when > making a request directly on the host instead of via the clusters. > curl -u admin:admin -H "X-Requested-By: ambari" -X GET > http://localhost:8080/api/v1/hosts/c6403.ambari.apache.org > The above query does not return maintenance_state. > The following query does: > http://c6403.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6403.ambari.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15713) Starting MapR History Server Fails When NameNode is SSL
[
https://issues.apache.org/jira/browse/AMBARI-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-15713:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Starting MapR History Server Fails When NameNode is SSL
> ---
>
> Key: AMBARI-15713
> URL: https://issues.apache.org/jira/browse/AMBARI-15713
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15713.patch
>
>
> The `namenode_ha_utils.py` uses the deprecated `hdfs-site/dfs.https.enable`
> property. As a result, when starting components like MapR History Server, they
> will fail when NameNode is protected by SSL:
>
>
>
> 2016-01-11 14:19:32,903 - checked_call['ambari-sudo.sh su nzhdfs -l -s
> /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmpxmvioB 2>/tmp/tmpZcxPOR''] {'quiet': False}
> 2016-01-11 14:19:32,980 - Getting jmx metrics from NN failed. URL:
> http://nhgab001.tst.server.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 49, in get_user_call_output
> func_result = func(shell.as_user(command_string, user), quiet=quiet,
> **call_kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 291, in _call
> raise Fail(err_msg)
>
> Instead, `hdfs-site/dfs.http.policy` should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15703) HostResourceProvider should include maintenance_state when a request is made directly with the host name
[
https://issues.apache.org/jira/browse/AMBARI-15703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226367#comment-15226367
]
Hadoop QA commented on AMBARI-15703:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797074/rb45714.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/6222//console
This message is automatically generated.
> HostResourceProvider should include maintenance_state when a request is made
> directly with the host name
>
>
> Key: AMBARI-15703
> URL: https://issues.apache.org/jira/browse/AMBARI-15703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.4.0
>
> Attachments: rb45714.patch
>
>
> The property ** maintenance_state ** is not available in host response when
> making a request directly on the host instead of via the clusters.
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/hosts/c6403.ambari.apache.org
> The above query does not return maintenance_state.
> The following query does:
> http://c6403.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6403.ambari.apache.org
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15682) Views: Provide refresh list of available views with newly deployed views w/o restart
[ https://issues.apache.org/jira/browse/AMBARI-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-15682: --- Status: Patch Available (was: Open) > Views: Provide refresh list of available views with newly deployed views w/o > restart > > > Key: AMBARI-15682 > URL: https://issues.apache.org/jira/browse/AMBARI-15682 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-15682.2.trunk.patch, AMBARI-15682.3.trunk.patch, > AMBARI-15682.branch-2.2.patch > > Original Estimate: 96h > Remaining Estimate: 96h > > Ambari is able to detect that there are new views available (dynamically). > However, there does not appear to be a mechanism to perform a refresh. > What makes the most sense is to refresh everytime the admin view page is > accessed and also provide a manual refresh button > User should be able to: > 1) Place a new view package on Ambari Server > 2) Do not restart Ambari Server > 3) While in Admin View, user clicks refresh in browser on Views section > 4) Newly deployed view is shown. User can create use the view to create > instances, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15682) Views: Provide refresh list of available views with newly deployed views w/o restart
[ https://issues.apache.org/jira/browse/AMBARI-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-15682: --- Status: Open (was: Patch Available) > Views: Provide refresh list of available views with newly deployed views w/o > restart > > > Key: AMBARI-15682 > URL: https://issues.apache.org/jira/browse/AMBARI-15682 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-15682.2.trunk.patch, AMBARI-15682.3.trunk.patch, > AMBARI-15682.branch-2.2.patch > > Original Estimate: 96h > Remaining Estimate: 96h > > Ambari is able to detect that there are new views available (dynamically). > However, there does not appear to be a mechanism to perform a refresh. > What makes the most sense is to refresh everytime the admin view page is > accessed and also provide a manual refresh button > User should be able to: > 1) Place a new view package on Ambari Server > 2) Do not restart Ambari Server > 3) While in Admin View, user clicks refresh in browser on Views section > 4) Newly deployed view is shown. User can create use the view to create > instances, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15682) Views: Provide refresh list of available views with newly deployed views w/o restart
[ https://issues.apache.org/jira/browse/AMBARI-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-15682: --- Attachment: AMBARI-15682.3.trunk.patch > Views: Provide refresh list of available views with newly deployed views w/o > restart > > > Key: AMBARI-15682 > URL: https://issues.apache.org/jira/browse/AMBARI-15682 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-15682.2.trunk.patch, AMBARI-15682.3.trunk.patch, > AMBARI-15682.branch-2.2.patch > > Original Estimate: 96h > Remaining Estimate: 96h > > Ambari is able to detect that there are new views available (dynamically). > However, there does not appear to be a mechanism to perform a refresh. > What makes the most sense is to refresh everytime the admin view page is > accessed and also provide a manual refresh button > User should be able to: > 1) Place a new view package on Ambari Server > 2) Do not restart Ambari Server > 3) While in Admin View, user clicks refresh in browser on Views section > 4) Newly deployed view is shown. User can create use the view to create > instances, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15715) ASW send invalid requests for config groups
Andrii Babiichuk created AMBARI-15715:
-
Summary: ASW send invalid requests for config groups
Key: AMBARI-15715
URL: https://issues.apache.org/jira/browse/AMBARI-15715
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Fix For: 2.4.0
There is a cluster with HDFS + ZK
HDFS has 3 config groups (and 1 Default)
Open ASW
Select YARN + MR2
Proceed to the step "Configure services"
Create 1 group for YARN and 1 for MR2
Proceed to "Install, Start and Test"
ASW sends requests to create all config groups (even already created for HDFS).
All this requests are failed (for existing groups and for new groups)
Example with TEZ:
{noformat}
curl 'http://HOST:8080/api/v1/clusters/tdk/config_groups/TEZ_1234' -X PUT -H
'Pragma: no-cache' -H 'Origin: http://HOST:8080' -H 'Accept-Encoding: gzip,
deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'X-Requested-By:
X-Requested-By' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36' -H
'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Accept:
application/json, text/javascript, */*; q=0.01' -H 'Cache-Control: no-cache' -H
'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' -H 'Referer:
http://HOST:8080/' --data
'[{"ConfigGroup":{"cluster_name":"tdk","group_name":"1234","tag":"TEZ","description":"","hosts":[],"desired_configs":[],"id":"TEZ_1234"}}]'
--compressed
{noformat}
{noformat}
{
"status" : 400,
"message" : "java.lang.NumberFormatException: For input string: \"TEZ_1234\""
}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15715) ASW send invalid requests for config groups
[
https://issues.apache.org/jira/browse/AMBARI-15715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-15715:
--
Status: Patch Available (was: Open)
25605 tests complete (20 seconds)
156 tests pending
> ASW send invalid requests for config groups
> ---
>
> Key: AMBARI-15715
> URL: https://issues.apache.org/jira/browse/AMBARI-15715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15715.patch
>
>
> There is a cluster with HDFS + ZK
> HDFS has 3 config groups (and 1 Default)
> Open ASW
> Select YARN + MR2
> Proceed to the step "Configure services"
> Create 1 group for YARN and 1 for MR2
> Proceed to "Install, Start and Test"
> ASW sends requests to create all config groups (even already created for
> HDFS).
> All this requests are failed (for existing groups and for new groups)
> Example with TEZ:
> {noformat}
> curl 'http://HOST:8080/api/v1/clusters/tdk/config_groups/TEZ_1234' -X PUT -H
> 'Pragma: no-cache' -H 'Origin: http://HOST:8080' -H 'Accept-Encoding: gzip,
> deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'X-Requested-By:
> X-Requested-By' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36' -H
> 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Accept:
> application/json, text/javascript, */*; q=0.01' -H 'Cache-Control: no-cache'
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' -H
> 'Referer: http://HOST:8080/' --data
> '[{"ConfigGroup":{"cluster_name":"tdk","group_name":"1234","tag":"TEZ","description":"","hosts":[],"desired_configs":[],"id":"TEZ_1234"}}]'
> --compressed
> {noformat}
> {noformat}
> {
> "status" : 400,
> "message" : "java.lang.NumberFormatException: For input string:
> \"TEZ_1234\""
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15715) ASW send invalid requests for config groups
[
https://issues.apache.org/jira/browse/AMBARI-15715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-15715:
--
Attachment: AMBARI-15715.patch
> ASW send invalid requests for config groups
> ---
>
> Key: AMBARI-15715
> URL: https://issues.apache.org/jira/browse/AMBARI-15715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15715.patch
>
>
> There is a cluster with HDFS + ZK
> HDFS has 3 config groups (and 1 Default)
> Open ASW
> Select YARN + MR2
> Proceed to the step "Configure services"
> Create 1 group for YARN and 1 for MR2
> Proceed to "Install, Start and Test"
> ASW sends requests to create all config groups (even already created for
> HDFS).
> All this requests are failed (for existing groups and for new groups)
> Example with TEZ:
> {noformat}
> curl 'http://HOST:8080/api/v1/clusters/tdk/config_groups/TEZ_1234' -X PUT -H
> 'Pragma: no-cache' -H 'Origin: http://HOST:8080' -H 'Accept-Encoding: gzip,
> deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'X-Requested-By:
> X-Requested-By' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36' -H
> 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Accept:
> application/json, text/javascript, */*; q=0.01' -H 'Cache-Control: no-cache'
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' -H
> 'Referer: http://HOST:8080/' --data
> '[{"ConfigGroup":{"cluster_name":"tdk","group_name":"1234","tag":"TEZ","description":"","hosts":[],"desired_configs":[],"id":"TEZ_1234"}}]'
> --compressed
> {noformat}
> {noformat}
> {
> "status" : 400,
> "message" : "java.lang.NumberFormatException: For input string:
> \"TEZ_1234\""
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15715) ASW send invalid requests for config groups
[
https://issues.apache.org/jira/browse/AMBARI-15715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226387#comment-15226387
]
Oleg Nechiporenko commented on AMBARI-15715:
+1 for patch
> ASW send invalid requests for config groups
> ---
>
> Key: AMBARI-15715
> URL: https://issues.apache.org/jira/browse/AMBARI-15715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15715.patch
>
>
> There is a cluster with HDFS + ZK
> HDFS has 3 config groups (and 1 Default)
> Open ASW
> Select YARN + MR2
> Proceed to the step "Configure services"
> Create 1 group for YARN and 1 for MR2
> Proceed to "Install, Start and Test"
> ASW sends requests to create all config groups (even already created for
> HDFS).
> All this requests are failed (for existing groups and for new groups)
> Example with TEZ:
> {noformat}
> curl 'http://HOST:8080/api/v1/clusters/tdk/config_groups/TEZ_1234' -X PUT -H
> 'Pragma: no-cache' -H 'Origin: http://HOST:8080' -H 'Accept-Encoding: gzip,
> deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'X-Requested-By:
> X-Requested-By' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36' -H
> 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Accept:
> application/json, text/javascript, */*; q=0.01' -H 'Cache-Control: no-cache'
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' -H
> 'Referer: http://HOST:8080/' --data
> '[{"ConfigGroup":{"cluster_name":"tdk","group_name":"1234","tag":"TEZ","description":"","hosts":[],"desired_configs":[],"id":"TEZ_1234"}}]'
> --compressed
> {noformat}
> {noformat}
> {
> "status" : 400,
> "message" : "java.lang.NumberFormatException: For input string:
> \"TEZ_1234\""
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15715) ASW send invalid requests for config groups
[
https://issues.apache.org/jira/browse/AMBARI-15715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226405#comment-15226405
]
Hadoop QA commented on AMBARI-15715:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797081/AMBARI-15715.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/6223//console
This message is automatically generated.
> ASW send invalid requests for config groups
> ---
>
> Key: AMBARI-15715
> URL: https://issues.apache.org/jira/browse/AMBARI-15715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15715.patch
>
>
> There is a cluster with HDFS + ZK
> HDFS has 3 config groups (and 1 Default)
> Open ASW
> Select YARN + MR2
> Proceed to the step "Configure services"
> Create 1 group for YARN and 1 for MR2
> Proceed to "Install, Start and Test"
> ASW sends requests to create all config groups (even already created for
> HDFS).
> All this requests are failed (for existing groups and for new groups)
> Example with TEZ:
> {noformat}
> curl 'http://HOST:8080/api/v1/clusters/tdk/config_groups/TEZ_1234' -X PUT -H
> 'Pragma: no-cache' -H 'Origin: http://HOST:8080' -H 'Accept-Encoding: gzip,
> deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'X-Requested-By:
> X-Requested-By' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36' -H
> 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Accept:
> application/json, text/javascript, */*; q=0.01' -H 'Cache-Control: no-cache'
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' -H
> 'Referer: http://HOST:8080/' --data
> '[{"ConfigGroup":{"cluster_name":"tdk","group_name":"1234","tag":"TEZ","description":"","hosts":[],"desired_configs":[],"id":"TEZ_1234"}}]'
> --compressed
> {noformat}
> {noformat}
> {
> "status" : 400,
> "message" : "java.lang.NumberFormatException: For input string:
> \"TEZ_1234\""
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226406#comment-15226406
]
Dmytro Sen commented on AMBARI-15708:
-
Hadoop QA fails to +1 due to npm install issues
{code}
[INFO] npm ERR!
[INFO] npm ERR! Additional logging details can be found in:
[INFO] npm ERR!
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-admin/src/main/resources/ui/admin-web/npm-debug.log
[INFO] npm ERR! not ok code 0
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ... SUCCESS [ 4.607 s]
[INFO] Apache Ambari Project POM . SUCCESS [ 0.116 s]
[INFO] Ambari Web SUCCESS [ 58.421 s]
[INFO] Ambari Views .. SUCCESS [ 2.101 s]
[INFO] Ambari Admin View . FAILURE [ 11.550 s]
[INFO] ambari-metrics SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
[INFO] Ambari Metrics Hadoop Sink SKIPPED
[INFO] Ambari Metrics Flume Sink . SKIPPED
[INFO] Ambari Metrics Kafka Sink . SKIPPED
[INFO] Ambari Metrics Storm Sink . SKIPPED
[INFO] Ambari Metrics Collector .. SKIPPED
[INFO] Ambari Metrics Monitor SKIPPED
[INFO] Ambari Metrics Grafana SKIPPED
[INFO] Ambari Metrics Assembly ... SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Functional Tests ... SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Python Client .. SKIPPED
[INFO] Ambari Groovy Client .. SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO] Ambari Python Shell ... SKIPPED
[INFO] Ambari Groovy Shell ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:17 min
[INFO] Finished at: 2016-04-05T14:57:20+00:00
[INFO] Final Memory: 27M/358M
[INFO]
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:0.0.16:npm (npm install) on project
ambari-admin: Failed to run task: 'npm install --unsafe-perm --color=false'
failed. (error code 1) -> [Help 1]
[ERROR]
{code}
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(T
[jira] [Commented] (AMBARI-15708) "Wrong metrics path " exceptions for JMX metrics
[
https://issues.apache.org/jira/browse/AMBARI-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226318#comment-15226318
]
Hadoop QA commented on AMBARI-15708:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797032/AMBARI-15708-trunk_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/6221//console
This message is automatically generated.
> "Wrong metrics path " exceptions for JMX metrics
>
>
> Key: AMBARI-15708
> URL: https://issues.apache.org/jira/browse/AMBARI-15708
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15708-trunk_2.patch
>
>
> {code}
> 04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 -
> Caught exception getting JMX metrics : Can not fetch 0th element of document
> path (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for
> next 5 minutes
> java.io.IOException: Can not fetch 0th element of document path
> (executorsTotal._sum) from json. Wrong metrics path:
> /api/v1/cluster/summary##executorsTotal._sum
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only
> for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15470) List of decommission-allowed components should be stack driven
[
https://issues.apache.org/jira/browse/AMBARI-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-15470:
---
Attachment: AMBARI-15470.patch
> List of decommission-allowed components should be stack driven
> --
>
> Key: AMBARI-15470
> URL: https://issues.apache.org/jira/browse/AMBARI-15470
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15470.patch
>
>
> decommission-allowed components are currently a hardcoded list in
> stack_service_component.js
> isDecommissionAllowed: Em.computed.existsIn('componentName', ['DATANODE',
> 'TASKTRACKER', 'NODEMANAGER', 'HBASE_REGIONSERVER']),
> This should be stack driven by examine metainfo.xml looking for DECOMMISSION
> custom command or a designated flag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15470) List of decommission-allowed components should be stack driven
[
https://issues.apache.org/jira/browse/AMBARI-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-15470:
---
Assignee: Di Li
Status: Patch Available (was: Open)
> List of decommission-allowed components should be stack driven
> --
>
> Key: AMBARI-15470
> URL: https://issues.apache.org/jira/browse/AMBARI-15470
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15470.patch
>
>
> decommission-allowed components are currently a hardcoded list in
> stack_service_component.js
> isDecommissionAllowed: Em.computed.existsIn('componentName', ['DATANODE',
> 'TASKTRACKER', 'NODEMANAGER', 'HBASE_REGIONSERVER']),
> This should be stack driven by examine metainfo.xml looking for DECOMMISSION
> custom command or a designated flag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-15649: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch, AMBARI-15649_updated.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
