[jira] [Resolved] (AMBARI-21336) Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput
[ https://issues.apache.org/jira/browse/AMBARI-21336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh resolved AMBARI-21336. -- Resolution: Invalid Created at wrong location > Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput > - > > Key: AMBARI-21336 > URL: https://issues.apache.org/jira/browse/AMBARI-21336 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: 246113686.png > > > Raw Log - > https://s3.amazonaws.com/archive.travis-ci.org/jobs/246113686/log.txt?X-Amz-Expires=30=20170624T042931Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170624/us-east-1/s3/aws4_request=host=6ad442e67857da5228e08363229dc2a6748506c14fd3f17c2fcb8cf826ce9c64 > Travis seems to be failing at times with the paragraph state as Running and > expecting Finished. I believe we can increase this MAX_PARAGRAPH_TIMEOUT_SEC > to say 2min should solve this problem. > Increase MAX_PARAGRAPH_TIMEOUT_SEC in AbstractZeppelinIT for Selenium test > cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21336) Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput
[ https://issues.apache.org/jira/browse/AMBARI-21336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061795#comment-16061795 ] Prabhjyot Singh edited comment on AMBARI-21336 at 6/24/17 4:45 AM: --- Here is a screen shot from travis, that failed with timeout; ParagraphActionsIT.testSingleDynamicFormTextInput:553->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94 » Timeout !246113686.png|width=100%! was (Author: prabhjyotsingh): Here is a screen shot from travis, that failed with timeout; ParagraphActionsIT.testSingleDynamicFormTextInput:553->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94 » Timeout !246113686.png|thumbnail! > Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput > - > > Key: AMBARI-21336 > URL: https://issues.apache.org/jira/browse/AMBARI-21336 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: 246113686.png > > > Raw Log - > https://s3.amazonaws.com/archive.travis-ci.org/jobs/246113686/log.txt?X-Amz-Expires=30=20170624T042931Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170624/us-east-1/s3/aws4_request=host=6ad442e67857da5228e08363229dc2a6748506c14fd3f17c2fcb8cf826ce9c64 > Travis seems to be failing at times with the paragraph state as Running and > expecting Finished. I believe we can increase this MAX_PARAGRAPH_TIMEOUT_SEC > to say 2min should solve this problem. > Increase MAX_PARAGRAPH_TIMEOUT_SEC in AbstractZeppelinIT for Selenium test > cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21336) Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput
[ https://issues.apache.org/jira/browse/AMBARI-21336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21336: - Attachment: 246113686.png Here is a screen shot from travis, that failed with timeout; ParagraphActionsIT.testSingleDynamicFormTextInput:553->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94 » Timeout !246113686.png|thumbnail! > Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput > - > > Key: AMBARI-21336 > URL: https://issues.apache.org/jira/browse/AMBARI-21336 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: 246113686.png > > > Raw Log - > https://s3.amazonaws.com/archive.travis-ci.org/jobs/246113686/log.txt?X-Amz-Expires=30=20170624T042931Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170624/us-east-1/s3/aws4_request=host=6ad442e67857da5228e08363229dc2a6748506c14fd3f17c2fcb8cf826ce9c64 > Travis seems to be failing at times with the paragraph state as Running and > expecting Finished. I believe we can increase this MAX_PARAGRAPH_TIMEOUT_SEC > to say 2min should solve this problem. > Increase MAX_PARAGRAPH_TIMEOUT_SEC in AbstractZeppelinIT for Selenium test > cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21336) Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput
Prabhjyot Singh created AMBARI-21336: Summary: Flaky Test: ParagraphActionsIT.testSingleDynamicFormTextInput Key: AMBARI-21336 URL: https://issues.apache.org/jira/browse/AMBARI-21336 Project: Ambari Issue Type: Bug Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh Raw Log - https://s3.amazonaws.com/archive.travis-ci.org/jobs/246113686/log.txt?X-Amz-Expires=30=20170624T042931Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170624/us-east-1/s3/aws4_request=host=6ad442e67857da5228e08363229dc2a6748506c14fd3f17c2fcb8cf826ce9c64 Travis seems to be failing at times with the paragraph state as Running and expecting Finished. I believe we can increase this MAX_PARAGRAPH_TIMEOUT_SEC to say 2min should solve this problem. Increase MAX_PARAGRAPH_TIMEOUT_SEC in AbstractZeppelinIT for Selenium test cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21335) Cannot start ambari server
[
https://issues.apache.org/jira/browse/AMBARI-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061744#comment-16061744
]
Hudson commented on AMBARI-21335:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7679 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7679/])
AMBARI-21335. Cannot start ambari server (Vitaly Brodetskyi via (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3acf9082c4dccc06e5131496f36213e8728e2260])
* (edit) ambari-server/src/main/assemblies/server.xml
> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
>
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> 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.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21335) Cannot start ambari server
[
https://issues.apache.org/jira/browse/AMBARI-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21335:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed.
> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
>
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> 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.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21335) Cannot start ambari server
[
https://issues.apache.org/jira/browse/AMBARI-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061724#comment-16061724
]
Sumit Mohanty commented on AMBARI-21335:
LGTM, +1
> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
>
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> 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.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21335) Cannot start ambari server
[
https://issues.apache.org/jira/browse/AMBARI-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21335:
---
Status: Patch Available (was: Open)
> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
>
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> 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.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21335) Cannot start ambari server
[
https://issues.apache.org/jira/browse/AMBARI-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21335:
---
Attachment: AMBARI-21335.patch
> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
>
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> 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.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21335) Cannot start ambari server
Vitaly Brodetskyi created AMBARI-21335:
--
Summary: Cannot start ambari server
Key: AMBARI-21335
URL: https://issues.apache.org/jira/browse/AMBARI-21335
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 3.0.0
ambari-server start fails with following error
{Code}
ambari-server start
Using python /usr/bin/python
Starting ambari-server
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.Unable to determine server PID. Retrying...
..Unable to determine server PID. Retrying...
..Unable to determine server PID. Retrying...
ERROR: Exiting with exit code -1.
REASON: Ambari Server java process died with exitcode 1. Check
/var/log/ambari-server/ambari-server.out for more information.
{Code}
logs in /var/log/ambari-server/ambari-server.out shows
{code}
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
INFO: Reading password from existing file
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration
getHostsMapFile
INFO: Hosts Mapping File null
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
INFO: Using hostsmap file null
Exception in thread "main" java.lang.NoSuchMethodError:
org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
at
org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
at
org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
at
org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
at
com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
at com.google.inject.spi.Elements.getElements(Elements.java:101)
at
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
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.controller.AmbariServer.main(AmbariServer.java:1060)
~
{code}
Ambari build used - 3.0.0.0-871
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21329) No data on templated Grafana dashboards on HDF cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061571#comment-16061571 ] Hudson commented on AMBARI-21329: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7677 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7677/]) AMBARI-21329 : No data on templated Grafana dashboards on HDF cluster. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8b90145caadf73c550c2d209eec4044ba924de9a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsServiceImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/DatabaseMetricsSource.java * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java > No data on templated Grafana dashboards on HDF cluster. > --- > > Key: AMBARI-21329 > URL: https://issues.apache.org/jira/browse/AMBARI-21329 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.2 > > > On a cluster with HDF 3.0 and Ambari 2.5.1.0, no data is seen in Grafana > dashboards with Hosts dropdown selection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21329) No data on templated Grafana dashboards on HDF cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061553#comment-16061553 ] Hudson commented on AMBARI-21329: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1628 (See [https://builds.apache.org/job/Ambari-branch-2.5/1628/]) AMBARI-21329 : No data on templated Grafana dashboards on HDF cluster. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=57a1fd11c36ec9e5fd6ccd3952bce4809d8ee16d]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/DatabaseMetricsSource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsServiceImpl.java > No data on templated Grafana dashboards on HDF cluster. > --- > > Key: AMBARI-21329 > URL: https://issues.apache.org/jira/browse/AMBARI-21329 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.2 > > > On a cluster with HDF 3.0 and Ambari 2.5.1.0, no data is seen in Grafana > dashboards with Hosts dropdown selection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21328) NameNode alerts in Unknown state after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061554#comment-16061554
]
Hudson commented on AMBARI-21328:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1628 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1628/])
AMBARI-21328 : NameNode alerts in Unknown state after Ambari upgrade.
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=802e8c6dde449f35d145ff9db0608767b2aa8e10])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/templates/hadoop-metrics2.properties.j2
> NameNode alerts in Unknown state after Ambari upgrade
> -
>
> Key: AMBARI-21328
> URL: https://issues.apache.org/jira/browse/AMBARI-21328
> Project: Ambari
> Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Attachments: AMBARI-21328.patch
>
>
> PROBLEM:
> When ambari is upgraded to Ambari-2.5, the NameNode alerts in Ambari becomes
> in UNKNOWN state stating the error:
>
> Message
> {code}
> Properties file doesn't contain namenode.sink.timeline.collector.hosts
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21329) No data on templated Grafana dashboards on HDF cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-21329. Resolution: Fixed Pushed to branch-2.5 and trunk. > No data on templated Grafana dashboards on HDF cluster. > --- > > Key: AMBARI-21329 > URL: https://issues.apache.org/jira/browse/AMBARI-21329 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.2 > > > On a cluster with HDF 3.0 and Ambari 2.5.1.0, no data is seen in Grafana > dashboards with Hosts dropdown selection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21328) NameNode alerts in Unknown state after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21328:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5
> NameNode alerts in Unknown state after Ambari upgrade
> -
>
> Key: AMBARI-21328
> URL: https://issues.apache.org/jira/browse/AMBARI-21328
> Project: Ambari
> Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Attachments: AMBARI-21328.patch
>
>
> PROBLEM:
> When ambari is upgraded to Ambari-2.5, the NameNode alerts in Ambari becomes
> in UNKNOWN state stating the error:
>
> Message
> {code}
> Properties file doesn't contain namenode.sink.timeline.collector.hosts
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[
https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061417#comment-16061417
]
Hadoop QA commented on AMBARI-17898:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12874128/AMBARI-17898_trunk_june.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11675//console
This message is automatically generated.
> Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
> -
>
> Key: AMBARI-17898
> URL: https://issues.apache.org/jira/browse/AMBARI-17898
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.2.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does
> not support Kerberos HTTP SPNEGO authentication.
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server:
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-21287) Cannot install Datanode/AppTimeLine server from ambari 3.0
[
https://issues.apache.org/jira/browse/AMBARI-21287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish reopened AMBARI-21287:
-
> Cannot install Datanode/AppTimeLine server from ambari 3.0
> --
>
> Key: AMBARI-21287
> URL: https://issues.apache.org/jira/browse/AMBARI-21287
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21287.patch
>
>
> Fails to install datanode and apptimeline server with the following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/3.0.0.3.0/package/scripts/datanode.py",
> line 120, in
> DataNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/3.0.0.3.0/package/scripts/datanode.py",
> line 49, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 740, in install_packages
> retry_count=agent_stack_retry_count)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
> line 54, in action_install
> self.install_package(package_name, self.resource.use_repos,
> self.resource.skip_repos)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py",
> line 43, in install_package
> if is_upgrade or use_repos or not self._check_existence(name):
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py",
> line 93, in _check_existence
> return self.yum_check_package_available(name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
> line 150, in yum_check_package_available
> name_regex = re.escape(name).replace("\\?", ".").replace("\\*", ".*") + '$'
> File "/usr/lib64/python2.7/re.py", line 206, in escape
> s = list(pattern)
> TypeError: 'NoneType' object is not iterable
> {code}
> Ambari version
> {code}
> ambari-server --version
> 3.0.0.0-855
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21334) Ability to disable Container metrics in AMS
[ https://issues.apache.org/jira/browse/AMBARI-21334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21334: -- Description: Yarn container metrics may flood the AMS collector with too many metrics which may cause AMS collector to crash. Hence, it would be helpful if we can disable these container metrics. (was: Yarn container metrics may flood the AMS collector with too many metrics which may cause AMS collector to crash. Hence, it would be helpful to disable these container metrics.) > Ability to disable Container metrics in AMS > --- > > Key: AMBARI-21334 > URL: https://issues.apache.org/jira/browse/AMBARI-21334 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Krishnama Raju K > > Yarn container metrics may flood the AMS collector with too many metrics > which may cause AMS collector to crash. Hence, it would be helpful if we can > disable these container metrics. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21334) Ability to disable Container metrics in AMS
Krishnama Raju K created AMBARI-21334: - Summary: Ability to disable Container metrics in AMS Key: AMBARI-21334 URL: https://issues.apache.org/jira/browse/AMBARI-21334 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Krishnama Raju K Yarn container metrics may flood the AMS collector with too many metrics which may cause AMS collector to crash. Hence, it would be helpful to disable these container metrics. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21291) Schema error during upgrade related to request table
[
https://issues.apache.org/jira/browse/AMBARI-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061170#comment-16061170
]
Hudson commented on AMBARI-21291:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7676 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7676/])
AMBARI-21291. Schema error during upgrade related to request table -
(adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8f80fe733dc3a69a83abad2cb8f2ee499cab7da3])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
> Schema error during upgrade related to request table
>
>
> Key: AMBARI-21291
> URL: https://issues.apache.org/jira/browse/AMBARI-21291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21291.patch
>
>
> During an upgrade from 2.4.1 to 2. 5.1 we experience the following error:
> {code}
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Data truncation: Invalid use of NULL value
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:425)
>
> Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Invalid use
> of NULL value
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3833)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2531)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2489)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:848)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:742)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:844)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:836)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1086)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1098)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.moveColumnToAnotherTable(DBAccessorImpl.java:1340)
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.moveClusterHostColumnFromStageToRequest(UpgradeCatalog251.ja
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.executeDDLUpdates(UpgradeCatalog251.java:90)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:925)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
>
> {code}
> Problem were that cluster_host_info had null value
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21210) Add ability to Log Search to test a log entry if it is parseable
[ https://issues.apache.org/jira/browse/AMBARI-21210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061069#comment-16061069 ] Hudson commented on AMBARI-21210: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7675 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7675/]) AMBARI-21210 Add ability to Log Search to test a log entry if it is (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=943c1b0d375a2d92b75be1be7158e8643692b1df]) * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/FilterGrokDescriptor.java * (edit) ambari-logsearch/ambari-logsearch-server/pom.xml * (edit) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigClass1.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogEntryParseTester.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/AliasUtil.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/metrics/MetricsManagerTest.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/FilterGrokDescriptorImpl.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterGrok.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/metrics/MetrcisManagerTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/run.sh * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeederCommandLine.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/ShipperConfigResource.java * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/LogSearchConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/logconfig/LogConfigHandlerTest.java * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/LogSearchConfigZK.java * (edit) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigClass2.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/FileUtil.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/ConfigHandler.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/LogFeederUtil.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/ShipperConfigManager.java > Add ability to Log Search to test a log entry if it is parseable > > > Key: AMBARI-21210 > URL: https://issues.apache.org/jira/browse/AMBARI-21210 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21210.patch > > > Add a REST API endpoint to the server, and a command line option to the Log > Feeder to check if the provided log entry is parseable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[
https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060957#comment-16060957
]
Hadoop QA commented on AMBARI-21332:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12874259/AMBARI-21332.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11674//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11674//console
This message is automatically generated.
> Wizard's Minimized State - Show Who Initiated
> -
>
> Key: AMBARI-21332
> URL: https://issues.apache.org/jira/browse/AMBARI-21332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21332.patch
>
>
> We need to keep track of who initiated the wizard in "persist" and show it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21256) As part of START_ALL of services Ranger kms starts after hbase and hive causing operation failure
[ https://issues.apache.org/jira/browse/AMBARI-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060953#comment-16060953 ] Sumit Mohanty commented on AMBARI-21256: LGTM, +1 > As part of START_ALL of services Ranger kms starts after hbase and hive > causing operation failure > - > > Key: AMBARI-21256 > URL: https://issues.apache.org/jira/browse/AMBARI-21256 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.2 > > Attachments: AMBARI-21256_branch-2.5.patch, AMBARI-21256_trunk.patch > > > As part of START_ALL of services Ranger-KMS starts after Hbase and Hive > causing their start failure. > In an encrypted cluster where TDE is on, Hbase service seems to be dependent > on the Ranger-KMS service, but for a start-all services action Hbase service > starts before Ranger-KMS. > So Hbase master goes down while connecting to KMS, since at the time of Hbase > start KMS is down , connection to KMS fails, and Hbase-Master fails to become > active. > This in-turn causes Atlas service start failure which actually depends on > HBase and start_all flow fails for HBASE and HIVE. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21210) Add ability to Log Search to test a log entry if it is parseable
[ https://issues.apache.org/jira/browse/AMBARI-21210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21210: Resolution: Fixed Status: Resolved (was: Patch Available) > Add ability to Log Search to test a log entry if it is parseable > > > Key: AMBARI-21210 > URL: https://issues.apache.org/jira/browse/AMBARI-21210 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21210.patch > > > Add a REST API endpoint to the server, and a command line option to the Log > Feeder to check if the provided log entry is parseable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21333) Extract Log Search part from stack advisor to a separate service advisor
[ https://issues.apache.org/jira/browse/AMBARI-21333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21333: Status: Patch Available (was: Open) > Extract Log Search part from stack advisor to a separate service advisor > > > Key: AMBARI-21333 > URL: https://issues.apache.org/jira/browse/AMBARI-21333 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21333.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21333) Extract Log Search part from stack advisor to a separate service advisor
[ https://issues.apache.org/jira/browse/AMBARI-21333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21333: Attachment: AMBARI-21333.patch > Extract Log Search part from stack advisor to a separate service advisor > > > Key: AMBARI-21333 > URL: https://issues.apache.org/jira/browse/AMBARI-21333 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21333.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21210) Add ability to Log Search to test a log entry if it is parseable
[
https://issues.apache.org/jira/browse/AMBARI-21210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060940#comment-16060940
]
Miklos Gergely commented on AMBARI-21210:
-
committed to trunk:
{code:java}
commit 943c1b0d375a2d92b75be1be7158e8643692b1df
Author: Miklos Gergely
Date: Fri Jun 23 16:03:51 2017 +0200
AMBARI-21210 Add ability to Log Search to test a log entry if it is
parseable (mgergely)
Change-Id: I545d7ade76beb3b8ce75dda9d66ca1c36b38a691
{code}
> Add ability to Log Search to test a log entry if it is parseable
>
>
> Key: AMBARI-21210
> URL: https://issues.apache.org/jira/browse/AMBARI-21210
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21210.patch
>
>
> Add a REST API endpoint to the server, and a command line option to the Log
> Feeder to check if the provided log entry is parseable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[
https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060927#comment-16060927
]
Hadoop QA commented on AMBARI-21332:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12874259/AMBARI-21332.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11673//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11673//console
This message is automatically generated.
> Wizard's Minimized State - Show Who Initiated
> -
>
> Key: AMBARI-21332
> URL: https://issues.apache.org/jira/browse/AMBARI-21332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21332.patch
>
>
> We need to keep track of who initiated the wizard in "persist" and show it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060924#comment-16060924 ] Andrii Tkach commented on AMBARI-21331: --- committed to branch-3.0-perf > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21331: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21333) Extract Log Search part from stack advisor to a separate service advisor
Miklos Gergely created AMBARI-21333: --- Summary: Extract Log Search part from stack advisor to a separate service advisor Key: AMBARI-21333 URL: https://issues.apache.org/jira/browse/AMBARI-21333 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060915#comment-16060915 ] Aleksandr Kovalenko commented on AMBARI-21332: -- +1 for the patch > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21332.patch > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21332: - Status: Patch Available (was: Open) > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21332.patch > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21332: - Attachment: AMBARI-21332.patch > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21332.patch > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21332: - Description: We need to keep track of who initiated the wizard in "persist" and show it. was: During the upgrade we have checks to ensure that we can enter the upgrade. We need to take a second look at the user experience of those checks to make sure that where we can run a command on behalf of the user to fix the issue: Service Checks, Package Re-Install, Link to Documentation - we should give them the option to do that. That way they don't have to remember everything/take a screenshot and then try again and again until everything is correct. > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21332: - Summary: Wizard's Minimized State - Show Who Initiated (was: Pre-Upgrade Checklist Changes) > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > > During the upgrade we have checks to ensure that we can enter the upgrade. We > need to take a second look at the user experience of those checks to make > sure that where we can run a command on behalf of the user to fix the issue: > Service Checks, Package Re-Install, Link to Documentation - we should give > them the option to do that. That way they don't have to remember > everything/take a screenshot and then try again and again until everything is > correct. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21332) Pre-Upgrade Checklist Changes
Antonenko Alexander created AMBARI-21332: Summary: Pre-Upgrade Checklist Changes Key: AMBARI-21332 URL: https://issues.apache.org/jira/browse/AMBARI-21332 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 During the upgrade we have checks to ensure that we can enter the upgrade. We need to take a second look at the user experience of those checks to make sure that where we can run a command on behalf of the user to fix the issue: Service Checks, Package Re-Install, Link to Documentation - we should give them the option to do that. That way they don't have to remember everything/take a screenshot and then try again and again until everything is correct. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060878#comment-16060878 ] Andrii Babiichuk commented on AMBARI-21331: --- +1 for the patch > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060872#comment-16060872 ] Andrii Tkach commented on AMBARI-21331: --- 20729 passing (26s) 128 pending > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21331: -- Status: Patch Available (was: Open) > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21256) As part of START_ALL of services Ranger kms starts after hbase and hive causing operation failure
[ https://issues.apache.org/jira/browse/AMBARI-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21256: Status: Patch Available (was: In Progress) > As part of START_ALL of services Ranger kms starts after hbase and hive > causing operation failure > - > > Key: AMBARI-21256 > URL: https://issues.apache.org/jira/browse/AMBARI-21256 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.2 > > Attachments: AMBARI-21256_branch-2.5.patch, AMBARI-21256_trunk.patch > > > As part of START_ALL of services Ranger-KMS starts after Hbase and Hive > causing their start failure. > In an encrypted cluster where TDE is on, Hbase service seems to be dependent > on the Ranger-KMS service, but for a start-all services action Hbase service > starts before Ranger-KMS. > So Hbase master goes down while connecting to KMS, since at the time of Hbase > start KMS is down , connection to KMS fails, and Hbase-Master fails to become > active. > This in-turn causes Atlas service start failure which actually depends on > HBase and start_all flow fails for HBASE and HIVE. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21331) Integrate Services status with websocket events
[ https://issues.apache.org/jira/browse/AMBARI-21331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21331: -- Attachment: AMBARI-21331.patch > Integrate Services status with websocket events > --- > > Key: AMBARI-21331 > URL: https://issues.apache.org/jira/browse/AMBARI-21331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-21331.patch > > > Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21256) As part of START_ALL of services Ranger kms starts after hbase and hive causing operation failure
[ https://issues.apache.org/jira/browse/AMBARI-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21256: Attachment: AMBARI-21256_branch-2.5.patch AMBARI-21256_trunk.patch > As part of START_ALL of services Ranger kms starts after hbase and hive > causing operation failure > - > > Key: AMBARI-21256 > URL: https://issues.apache.org/jira/browse/AMBARI-21256 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.2 > > Attachments: AMBARI-21256_branch-2.5.patch, AMBARI-21256_trunk.patch > > > As part of START_ALL of services Ranger-KMS starts after Hbase and Hive > causing their start failure. > In an encrypted cluster where TDE is on, Hbase service seems to be dependent > on the Ranger-KMS service, but for a start-all services action Hbase service > starts before Ranger-KMS. > So Hbase master goes down while connecting to KMS, since at the time of Hbase > start KMS is down , connection to KMS fails, and Hbase-Master fails to become > active. > This in-turn causes Atlas service start failure which actually depends on > HBase and start_all flow fails for HBASE and HIVE. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21331) Integrate Services status with websocket events
Andrii Tkach created AMBARI-21331: - Summary: Integrate Services status with websocket events Key: AMBARI-21331 URL: https://issues.apache.org/jira/browse/AMBARI-21331 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Subscribe to /events/services, which will update service status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21327) Ambari server to print error messages if NN HA namenode services properties use diff FQDN (dual network cards) than FQDN in the HostComponentState table
[
https://issues.apache.org/jira/browse/AMBARI-21327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060858#comment-16060858
]
Hadoop QA commented on AMBARI-21327:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12874135/AMBARI-21327.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11672//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11672//console
This message is automatically generated.
> Ambari server to print error messages if NN HA namenode services properties
> use diff FQDN (dual network cards) than FQDN in the HostComponentState table
>
>
> Key: AMBARI-21327
> URL: https://issues.apache.org/jira/browse/AMBARI-21327
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-21327.patch
>
>
> For hosts with dual network cards and configured with two FQDN, it's possible
> to manually config NN HA with alternative FQDN than the ones recorded in the
> Ambari database. This caused an issue for EU/RU when upon kicking off the
> upgrade via UI, the UI immediately posts the following error:
> "An internal system exception occurred: Request specifies host X but it
> is not a valid host based on the target service=null and component=null"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21327) Ambari server to print error messages if NN HA namenode services properties use diff FQDN (dual network cards) than FQDN in the HostComponentState table
[ https://issues.apache.org/jira/browse/AMBARI-21327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21327: --- Status: Patch Available (was: Open) > Ambari server to print error messages if NN HA namenode services properties > use diff FQDN (dual network cards) than FQDN in the HostComponentState table > > > Key: AMBARI-21327 > URL: https://issues.apache.org/jira/browse/AMBARI-21327 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-21327.patch > > > For hosts with dual network cards and configured with two FQDN, it's possible > to manually config NN HA with alternative FQDN than the ones recorded in the > Ambari database. This caused an issue for EU/RU when upon kicking off the > upgrade via UI, the UI immediately posts the following error: > "An internal system exception occurred: Request specifies host X but it > is not a valid host based on the target service=null and component=null" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21154) Add JAAS config properties for Atlas Hive hook in HiveCli to use kerberos ticket-cache
[
https://issues.apache.org/jira/browse/AMBARI-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-21154:
Attachment: AMBARI-21154-branch-2.5.patch
AMBARI-21154-trunk.patch
> Add JAAS config properties for Atlas Hive hook in HiveCli to use kerberos
> ticket-cache
> --
>
> Key: AMBARI-21154
> URL: https://issues.apache.org/jira/browse/AMBARI-21154
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Minor
> Fix For: 2.5.2
>
> Attachments: AMBARI-21154-branch-2.5.patch, AMBARI-21154.patch,
> AMBARI-21154-trunk.patch
>
>
> In a kerberized environment, Atlas hook uses JAAS configuration section named
> "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment
> this configuration section is set to use the keytab and principal of
> HiveServer2 process. The hook running in HiveCLI might fail to authenticate
> with Kafka if the user can't read the configured keytab.
> Given that HiveCLI users would have performed kinit, the hook in HiveCLI
> should use the ticket-cache generated by kinit. When ticket cache is not
> available (for example in HiveServer2), the hook should use the configuration
> provided in KafkaClient JAAS section
> As a solution need to add below in {{hive atlas-application.properties}} by
> default if atlas-hive hook is enabled in secure mode
> {code:none}
> atlas.jaas.ticketBased-KafkaClient.loginModuleControlFlag=required
> atlas.jaas.ticketBased-KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
> atlas.jaas.ticketBased-KafkaClient.option.useTicketCache=true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21296) Python tests fail with local variable 'os_family_provider' referenced before assignment on ppc64le
[
https://issues.apache.org/jira/browse/AMBARI-21296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pravin Dsilva updated AMBARI-21296:
---
Component/s: ambari-server
> Python tests fail with local variable 'os_family_provider' referenced before
> assignment on ppc64le
> --
>
> Key: AMBARI-21296
> URL: https://issues.apache.org/jira/browse/AMBARI-21296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Environment: $ uname -a
> Linux pts00607-vm4 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Pravin Dsilva
> Labels: powerpc, ppc64le
>
> There are 78 python test failures in Ambari agent for ppc64le
> Error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py",
> line 68, in test_action_create_empty_xml_config
> configuration_attributes={}
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 118, in run_action
> resource.provider)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/providers/__init__.py",
> line 93, in find_provider
> if resource in os_family_provider:
> UnboundLocalError: local variable 'os_family_provider' referenced before
> assignment
> {code}
> In Ambari-server, the below tests fail:
> {code:java}
> ERROR: test_configure_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 37, in test_configure_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permission()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 93, in change_permission
> Directory(params.dwoo_path,
> AttributeError: 'module' object has no attribute 'dwoo_path'
> ERROR: test_install_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 79, in test_install_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 41, in install
> self.configure(env)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permission()
> File
>
[jira] [Updated] (AMBARI-21296) Python tests fail with local variable 'os_family_provider' referenced before assignment on ppc64le
[
https://issues.apache.org/jira/browse/AMBARI-21296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pravin Dsilva updated AMBARI-21296:
---
Description:
There are 78 python test failures in Ambari agent for ppc64le
Error:
{code:java}
Traceback (most recent call last):
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py",
line 68, in test_action_create_empty_xml_config
configuration_attributes={}
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
line 118, in run_action
resource.provider)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/providers/__init__.py",
line 93, in find_provider
if resource in os_family_provider:
UnboundLocalError: local variable 'os_family_provider' referenced before
assignment
{code}
In Ambari-server, the below tests fail:
{code:java}
ERROR: test_configure_default (test_ganglia_server.TestGangliaServer)
--
Traceback (most recent call last):
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
line 37, in test_configure_default
target = RMFTestCase.TARGET_COMMON_SERVICES
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 155, in executeScript
method(RMFTestCase.env, *command_args)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
line 78, in configure
change_permission()
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
line 93, in change_permission
Directory(params.dwoo_path,
AttributeError: 'module' object has no attribute 'dwoo_path'
ERROR: test_install_default (test_ganglia_server.TestGangliaServer)
--
Traceback (most recent call last):
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
line 79, in test_install_default
target = RMFTestCase.TARGET_COMMON_SERVICES
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 155, in executeScript
method(RMFTestCase.env, *command_args)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
line 41, in install
self.configure(env)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
line 78, in configure
change_permission()
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
line 93, in change_permission
Directory(params.dwoo_path,
AttributeError: 'module' object has no attribute 'dwoo_path'
ERROR: test_start_default (test_ganglia_server.TestGangliaServer)
--
Traceback (most recent call last):
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
line 48, in test_start_default
target = RMFTestCase.TARGET_COMMON_SERVICES
File
"/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 155, in executeScript
method(RMFTestCase.env, *command_args)
File
[jira] [Commented] (AMBARI-21298) Pausing An Upgrade In Progress Does Not Resume PENDING Tasks
[ https://issues.apache.org/jira/browse/AMBARI-21298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060601#comment-16060601 ] Hudson commented on AMBARI-21298: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7674 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7674/]) AMBARI-21298. Pausing An Upgrade In Progress Does Not Resume PENDING (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0dbc7976d95dd0bb25232a4fc4d204e55929eb9a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java > Pausing An Upgrade In Progress Does Not Resume PENDING Tasks > > > Key: AMBARI-21298 > URL: https://issues.apache.org/jira/browse/AMBARI-21298 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21298.patch > > > when upgrade is paused at a first time: > upgrade is paused > request:ABORTED > Stages (all):ABORTED > host_role_commands(all):ABORTED > If I resume upgrade and then stop it again, often (not always) I see the > following state: > upgrade is paused, current command shows up as failed (with cancel/retry) > request:ABORTED > Stages (all):ABORTED > host_role_commands(current):HOLDING_FAILED > host_role_commands(all):ABORTED > Resume does not transition ABORTED stages back to pending -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21298) Pausing An Upgrade In Progress Does Not Resume PENDING Tasks
[ https://issues.apache.org/jira/browse/AMBARI-21298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21298: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To https://git-wip-us.apache.org/repos/asf/ambari.git ec8deeba20..0dbc7976d9 trunk -> trunk > Pausing An Upgrade In Progress Does Not Resume PENDING Tasks > > > Key: AMBARI-21298 > URL: https://issues.apache.org/jira/browse/AMBARI-21298 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21298.patch > > > when upgrade is paused at a first time: > upgrade is paused > request:ABORTED > Stages (all):ABORTED > host_role_commands(all):ABORTED > If I resume upgrade and then stop it again, often (not always) I see the > following state: > upgrade is paused, current command shows up as failed (with cancel/retry) > request:ABORTED > Stages (all):ABORTED > host_role_commands(current):HOLDING_FAILED > host_role_commands(all):ABORTED > Resume does not transition ABORTED stages back to pending -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21330) Remove slider view from Ambari-3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060525#comment-16060525 ] Hudson commented on AMBARI-21330: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7673/]) AMBARI-21330.Remove slider view from Ambari-3.0.0(Venkata Sairam) (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ec8deeba201bfceb646d6d4a6e0e6fb97e9bc102]) * (delete) contrib/views/slider/src/main/resources/ui/app/templates/slider_app/configs.hbs * (delete) contrib/views/slider/src/main/resources/ui/app/components/.gitkeep * (delete) contrib/views/slider/src/main/resources/ui/app/templates/createAppWizard/step3.hbs * (delete) contrib/views/slider/src/main/resources/ui/vendor/scripts/common/bs-button.min.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/img/jquery-ui-bootstrap/ui-icons_22_256x240.png * (delete) contrib/views/slider/src/main/resources/ui/generators/arraycontroller/arraycontroller.js.hbs * (delete) contrib/views/slider/src/main/resources/ui/app/models/host.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/crossdomain.xml * (delete) contrib/views/slider/src/main/resources/ui/app/views/slider_app/destroy_popup_view.js * (delete) contrib/views/slider/gzip-content.ps1 * (delete) contrib/views/slider/src/main/resources/ui/app/assets/font/fontawesome-webfont.svg * (delete) contrib/views/slider/src/main/resources/ui/app/assets/tests.html * (delete) contrib/views/slider/src/main/resources/ui/test/unit/models/slider_app_test.js * (delete) contrib/views/slider/src/main/resources/ui/app/mappers/mapper.js * (delete) contrib/views/slider/src/main/resources/ui/app/views/slider_app/configs_view.js * (delete) contrib/views/slider/src/main/resources/ui/generators/controller/controller.js.hbs * (delete) contrib/views/slider/src/main/resources/ui/test/unit/controllers/createAppWizard/step3_controller_test.js * (delete) contrib/views/slider/src/main/resources/ui/app/templates/unavailable_apps.hbs * (delete) contrib/views/slider/src/main/resources/ui/app/assets/data/resource/status_true.json * (delete) contrib/views/slider/src/main/resources/ui/app/templates/slider_app/destroy/destroy_popup.hbs * (delete) contrib/views/slider/src/main/resources/ui/vendor/scripts/production/ember.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/img/jquery-ui-bootstrap/ui-icons_2e83ff_256x240.png * (delete) contrib/views/slider/src/main/resources/ui/app/controllers/slider_apps_controller.js * (delete) contrib/views/slider/src/main/resources/ui/app/translations.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/img/jquery-ui-bootstrap/ui-icons_f6cf3b_256x240.png * (delete) contrib/views/slider/src/main/resources/ui/vendor/styles/font-awesome-ie7.css * (delete) contrib/views/slider/src/main/resources/ui/app/assets/font/fontawesome-webfont.eot * (delete) contrib/views/slider/src/main/resources/ui/vendor/scripts/development/ember-data.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/javascripts/jquery.mockjax.js * (delete) contrib/views/slider/src/main/resources/ui/app/views/createAppWizard/step4_view.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/img/jquery-ui-bootstrap/ui-bg_glass_75_dadada_1x400.png * (delete) contrib/views/slider/src/main/resources/ui/vendor/styles/rickshaw.css * (delete) contrib/views/slider/src/main/resources/ui/app/helpers/.gitkeep * (delete) contrib/views/slider/src/main/resources/ui/test/unit/controllers/slider_app_controller_test.js * (delete) contrib/views/slider/src/main/resources/ui/app/templates/common/ajax_error.hbs * (delete) contrib/views/slider/src/main/resources/ui/app/controllers/createAppWizard/step2_controller.js * (delete) contrib/views/slider/src/main/resources/ui/app/views/slider_app/metrics/metric_view.js * (delete) contrib/views/slider/src/main/java/org/apache/ambari/view/slider/SliderAppsViewController.java * (delete) contrib/views/slider/src/main/resources/ui/app/templates/common/chart.hbs * (delete) contrib/views/slider/src/main/resources/ui/test/integration/pages/index_test.js * (delete) contrib/views/slider/src/main/resources/ui/setup.js * (delete) contrib/views/slider/src/main/resources/ui/app/controllers/createAppWizard/step4_controller.js * (delete) contrib/views/slider/src/main/resources/ui/app/assets/index.html * (delete) contrib/views/slider/src/main/resources/ui/app/mappers/slider_apps_mapper.js * (delete) contrib/views/slider/src/main/resources/ui/vendor/scripts/common/console-polyfill.js * (delete) contrib/views/slider/src/main/java/org/apache/ambari/view/slider/rest/client/Metric.java * (delete) contrib/views/slider/src/main/resources/ui/app/models/slider_app_type.js * (delete)
[jira] [Commented] (AMBARI-21328) NameNode alerts in Unknown state after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060488#comment-16060488
]
Dmytro Sen commented on AMBARI-21328:
-
+1
> NameNode alerts in Unknown state after Ambari upgrade
> -
>
> Key: AMBARI-21328
> URL: https://issues.apache.org/jira/browse/AMBARI-21328
> Project: Ambari
> Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Attachments: AMBARI-21328.patch
>
>
> PROBLEM:
> When ambari is upgraded to Ambari-2.5, the NameNode alerts in Ambari becomes
> in UNKNOWN state stating the error:
>
> Message
> {code}
> Properties file doesn't contain namenode.sink.timeline.collector.hosts
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21084) Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI.
[ https://issues.apache.org/jira/browse/AMBARI-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060484#comment-16060484 ] Hudson commented on AMBARI-21084: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1627 (See [https://builds.apache.org/job/Ambari-branch-2.5/1627/]) AMBARI-21084.Files view on IE 11- On Concatenating files or downloading, (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=75cb56ef7384ef733d4338e221ce3675f7241b3a]) * (edit) contrib/views/files/src/main/java/org/apache/ambari/view/filebrowser/DownloadService.java > Files view on IE 11- On Concatenating files or downloading, the concatenated > or downloaded file occupies the entire UI. > --- > > Key: AMBARI-21084 > URL: https://issues.apache.org/jira/browse/AMBARI-21084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21084-trunk.patch > > > The same behaviour is observed while we are trying to download the file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21084) Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI.
[ https://issues.apache.org/jira/browse/AMBARI-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-21084. - Resolution: Fixed > Files view on IE 11- On Concatenating files or downloading, the concatenated > or downloaded file occupies the entire UI. > --- > > Key: AMBARI-21084 > URL: https://issues.apache.org/jira/browse/AMBARI-21084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21084-trunk.patch > > > The same behaviour is observed while we are trying to download the file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21330) Remove slider view from Ambari-3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-21330. - Resolution: Fixed > Remove slider view from Ambari-3.0.0 > > > Key: AMBARI-21330 > URL: https://issues.apache.org/jira/browse/AMBARI-21330 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21330-trunk.patch > > > 1. Remove Slider View from trunk (Slider View is deprecated as of Ambari > 2.5.0, so it can be removed in 3.0.0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21255) Remove YARN client mode option from WFM
[ https://issues.apache.org/jira/browse/AMBARI-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21255: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove YARN client mode option from WFM > --- > > Key: AMBARI-21255 > URL: https://issues.apache.org/jira/browse/AMBARI-21255 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21255-branch-2.5.2-updated.patch > > > Today, Spark does not support YARN Client mode and hence, WFM/Oozie should > not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Resolution: Fixed Status: Resolved (was: Patch Available) > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20139) Need to show data in sorted order in Hive view
[ https://issues.apache.org/jira/browse/AMBARI-20139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20139: Resolution: Fixed Status: Resolved (was: Patch Available) > Need to show data in sorted order in Hive view > -- > > Key: AMBARI-20139 > URL: https://issues.apache.org/jira/browse/AMBARI-20139 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: HiveView2.0 > Attachments: AMBARI-20139-trunk.01.patch, AMBARI-20139-trunk.patch > > > Need to show data in sorted order in Hive view. > Case 1: Tables list view in 'Query' Tab and 'Tables' tab > Tables should be listed in alphabetical order > Case 2: Jobs should be sorted based on Job Id in 'Jobs' tab. I guess > descending order makes sense. > Case 3 : 'Saved Queries' and 'UDFs' tab > Result should be sorted based on user action time. Recent action should come > first. > Case 4: 'Settings' tab : > Lexicographical order based on KEY. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20702) User should be prompted for confirmation before closing the browser window
[ https://issues.apache.org/jira/browse/AMBARI-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20702: - Attachment: AMBARI-20702-branch-2-5.patch > User should be prompted for confirmation before closing the browser window > -- > > Key: AMBARI-20702 > URL: https://issues.apache.org/jira/browse/AMBARI-20702 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-20702-branch-2-5.patch > > > User should be prompted for confirmation before closing the browser window. > If user is in designer page and in middle of workflow creation and he clicks > on closing browser window or browser instance, he should be prompted for > confirmation before actually closing the window. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20702) User should be prompted for confirmation before closing the browser window
[ https://issues.apache.org/jira/browse/AMBARI-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20702: - Status: Patch Available (was: Open) > User should be prompted for confirmation before closing the browser window > -- > > Key: AMBARI-20702 > URL: https://issues.apache.org/jira/browse/AMBARI-20702 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-20702-branch-2-5.patch > > > User should be prompted for confirmation before closing the browser window. > If user is in designer page and in middle of workflow creation and he clicks > on closing browser window or browser instance, he should be prompted for > confirmation before actually closing the window. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20702) User should be prompted for confirmation before closing the browser window
[ https://issues.apache.org/jira/browse/AMBARI-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20702: - Component/s: (was: ambari-views) ambari-web > User should be prompted for confirmation before closing the browser window > -- > > Key: AMBARI-20702 > URL: https://issues.apache.org/jira/browse/AMBARI-20702 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha > Labels: WFD, WFM > Fix For: 2.5.2 > > > User should be prompted for confirmation before closing the browser window. > If user is in designer page and in middle of workflow creation and he clicks > on closing browser window or browser instance, he should be prompted for > confirmation before actually closing the window. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21291) Schema error during upgrade related to request table
[
https://issues.apache.org/jira/browse/AMBARI-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060449#comment-16060449
]
Hudson commented on AMBARI-21291:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7672 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7672/])
AMBARI-21291 Schema error during upgrade related to request table (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8f06a5b01719b825e8bcee2a2a56545a1c3052a9])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/H2Helper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog251.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/GenericDbmsHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/DbmsHelper.java
> Schema error during upgrade related to request table
>
>
> Key: AMBARI-21291
> URL: https://issues.apache.org/jira/browse/AMBARI-21291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21291.patch
>
>
> During an upgrade from 2.4.1 to 2. 5.1 we experience the following error:
> {code}
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Data truncation: Invalid use of NULL value
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:425)
>
> Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Invalid use
> of NULL value
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3833)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2531)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2489)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:848)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:742)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:844)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:836)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1086)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1098)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.moveColumnToAnotherTable(DBAccessorImpl.java:1340)
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.moveClusterHostColumnFromStageToRequest(UpgradeCatalog251.ja
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.executeDDLUpdates(UpgradeCatalog251.java:90)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:925)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
>
> {code}
> Problem were that cluster_host_info had null value
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21291) Schema error during upgrade related to request table
[
https://issues.apache.org/jira/browse/AMBARI-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060446#comment-16060446
]
Hudson commented on AMBARI-21291:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1626 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1626/])
AMBARI-21291 Schema error during upgrade related to request table (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=462a3e8b4c2a8026490a8bf056f51f10e866503d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/GenericDbmsHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog251.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/H2Helper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/DbmsHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
> Schema error during upgrade related to request table
>
>
> Key: AMBARI-21291
> URL: https://issues.apache.org/jira/browse/AMBARI-21291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21291.patch
>
>
> During an upgrade from 2.4.1 to 2. 5.1 we experience the following error:
> {code}
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> Data truncation: Invalid use of NULL value
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:425)
>
> Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Invalid use
> of NULL value
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3833)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2531)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2489)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:848)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:742)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:844)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:836)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1086)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.setColumnNullable(DBAccessorImpl.java:1098)
>
> at
> org.apache.ambari.server.orm.DBAccessorImpl.moveColumnToAnotherTable(DBAccessorImpl.java:1340)
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.moveClusterHostColumnFromStageToRequest(UpgradeCatalog251.ja
>
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog251.executeDDLUpdates(UpgradeCatalog251.java:90)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:925)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
>
> {code}
> Problem were that cluster_host_info had null value
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
