[jira] [Updated] (AMBARI-24886) Add stack feature constant to support Ranger admin users password change
[ https://issues.apache.org/jira/browse/AMBARI-24886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24886: Labels: pull-request-available (was: ) > Add stack feature constant to support Ranger admin users password change > > > Key: AMBARI-24886 > URL: https://issues.apache.org/jira/browse/AMBARI-24886 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > > Current Ambari stack for Ranger supports feature to change Ranger admin users > passwords through multiple calls. Ranger now supports ability to change all > admin users passwords in one call. Need to add stack feature support for the > same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685968#comment-16685968
]
Thejas M Nair commented on AMBARI-24582:
[~jonathan.hurley]
AFAIK, Ambari hasn't had a mechanism to specify username/password to connection
HS2, when HS2 is using username/password based authentication.
So it will fail to connect and do a positive healthcheck in such scenarios.
Is this positive check being enabled only for non password based authentication
cases ?
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24893) Add relevant NameNode start logic to OneFS mpack
David Tucker created AMBARI-24893:
-
Summary: Add relevant NameNode start logic to OneFS mpack
Key: AMBARI-24893
URL: https://issues.apache.org/jira/browse/AMBARI-24893
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Environment: HDP 3.0.1 + OneFS 8.1.2
Reporter: David Tucker
Deploying with OneFS using the mpack seems to omit setup steps. I'm not sure
exactly where the steps are defined in 2.7, but in 2.6 they seem to be here:
https://github.com/apache/ambari/blob/ac651d9d88d0c65d7ec1141ac5cd2af659781d79/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py#L102-L238
It's possible not all the steps are relevant, but at the very least these seem
to be:
https://github.com/apache/ambari/blob/ac651d9d88d0c65d7ec1141ac5cd2af659781d79/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py#L234-L235
According to
[Kiran|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kbhusanurmath],
"this is causing issue starting some of the services and importantly timeline
server V2 is unable to create necessary znode and start ats-hbase app."
It also appears to cause the YARN service check to fail with an ACE (since
{{/user/ambari-qa}} was not set up correctly).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24870) Allow blueprint install with partial YARN: no HISTORYSERVER and APP_TIMELINE_SERVER
[ https://issues.apache.org/jira/browse/AMBARI-24870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-24870: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Allow blueprint install with partial YARN: no HISTORYSERVER and > APP_TIMELINE_SERVER > --- > > Key: AMBARI-24870 > URL: https://issues.apache.org/jira/browse/AMBARI-24870 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > There is a need to install clusters with some components external to the > cluster. In this case the cluster has to have YARN but HISTORYSERVER and > APP_TIMELINE_SERVER should not be installed. > Even with blueprint validation turned off, installation stalls with > exceptions thrown in BlueprintConfigurationProcessor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24881) Implement JSON parsing code to handle Add Service request
[ https://issues.apache.org/jira/browse/AMBARI-24881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári resolved AMBARI-24881. Resolution: Fixed > Implement JSON parsing code to handle Add Service request > - > > Key: AMBARI-24881 > URL: https://issues.apache.org/jira/browse/AMBARI-24881 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: trunk > > Time Spent: 2.5h > Remaining Estimate: 0h > > This JIRA tracks the work involved to implement the parsing/handling code for > the JSON request and response elements of the "Add Service" API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24892) Warn During Upgrade When Plugin ClassLoader is not Found
[ https://issues.apache.org/jira/browse/AMBARI-24892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685615#comment-16685615 ] Hudson commented on AMBARI-24892: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10287 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10287/]) [AMBARI-24892] Warn During Upgrade When Plugin ClassLoader is not Found (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7caa2a54a5943b200765171edf32ea0337425b7a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog280.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistry.java > Warn During Upgrade When Plugin ClassLoader is not Found > > > Key: AMBARI-24892 > URL: https://issues.apache.org/jira/browse/AMBARI-24892 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > If a stack's plugin classloader is not found, all plugin classes should be > added to the set of failed plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24892) Warn During Upgrade When Plugin ClassLoader is not Found
[ https://issues.apache.org/jira/browse/AMBARI-24892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24892: Labels: pull-request-available (was: ) > Warn During Upgrade When Plugin ClassLoader is not Found > > > Key: AMBARI-24892 > URL: https://issues.apache.org/jira/browse/AMBARI-24892 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > If a stack's plugin classloader is not found, all plugin classes should be > added to the set of failed plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24892) Warn During Upgrade When Plugin ClassLoader is not Found
Jonathan Hurley created AMBARI-24892: Summary: Warn During Upgrade When Plugin ClassLoader is not Found Key: AMBARI-24892 URL: https://issues.apache.org/jira/browse/AMBARI-24892 Project: Ambari Issue Type: Bug Affects Versions: 2.8.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.8.0 If a stack's plugin classloader is not found, all plugin classes should be added to the set of failed plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24888) Fix SingleHostTopologyUpdater
[
https://issues.apache.org/jira/browse/AMBARI-24888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24888:
Labels: pull-request-available (was: )
> Fix SingleHostTopologyUpdater
> -
>
> Key: AMBARI-24888
> URL: https://issues.apache.org/jira/browse/AMBARI-24888
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: trunk
>
>
> Newer Ambari installations often require clusters with partially installed
> services (some required components missing). These clusters typically connect
> to other clusters and use some of the services from the external cluster.
> Ambari provides support for this by accepting blueprints with
> {{validate_topology=false}} flag, however the support is incomplete as
> usually exceptions are thrown later during the installation process with such
> blueprints.
> Most of the exceptions are thrown in the {{SingleHostTopologyUpdater}} class
> which acts as a validator in addition to being a property updater.
> The property update logic in {{SingleHostTopologyUpdater}} is the following:
> * All {{SingleHostTopologyUpdater}} instances are associated with a component
> (e.g. NAMENODE)
> * first, it does {{%HOSTGROUP%}} token replacement by calling the
> supertclas's method. *If this is successful, the replaced value is returned
> without any validation* (even with invalid topology)
> * if there is only one matching hostgroup for the updater's associated
> component, *validation will be skipped too*. If the property's value contains
> {{localhost}}, it will be replaced with the FQDN of one of the host from the
> matching host groups.
> * In all other cases, a validation process starts which tries to match a
> sequence of valid cases with the actual topology. If one of the cases match,
> the property will be returned unchanged. In none matches, an exception is
> thrown.
> As it can be seen above, the validation logic is not completely consistent.
> There are cases where validation is bypassed. E.g. if the updater encounters
> a {{%HOSTROUP%}} token, it will do the replacement even if the topology is
> broken and the associated component is missing.
> *Proposed solution*
> Features:
> * A general solution
> * Still protects from accidentally broken topology
> * Permits properties to point to external services
> * Very easy to implement (just a few lines).
> The proposed solution would simply leave the update logic in
> {{SingleHostTopologyUpdater}} as is and would restrict validation for the
> cases when the property contains {{localhost}}. This latter indicates that
> the property has the stack default value.
> This way, validation would still be performed in most cases when a component
> is left out from the blueprint by mistake.
> However, when a component is left out intentionally and the respective
> properties are intentionally set to point to an external FQDN or set to empty
> values, validation would be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24889) Pre-Upgrade Checklist: Components are Installed
[ https://issues.apache.org/jira/browse/AMBARI-24889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685479#comment-16685479 ] Hudson commented on AMBARI-24889: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10286 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10286/]) AMBARI-24889. Pre-Upgrade Checklist: Components are Installed (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=65bcbf7412805e68faa273d85b9d3b5e7472a6ed]) * (add) ambari-web/app/views/main/admin/stack_upgrade/custom_cluster_checks/custom_cluster_checks_components_installation.js * (edit) ambari-web/app/views/common/modal_popups/cluster_check_popup.js * (add) ambari-web/app/templates/main/admin/stack_upgrade/custom_cluster_checks/custom_cluster_checks_components_installation.hbs > Pre-Upgrade Checklist: Components are Installed > --- > > Key: AMBARI-24889 > URL: https://issues.apache.org/jira/browse/AMBARI-24889 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24889) Pre-Upgrade Checklist: Components are Installed
[ https://issues.apache.org/jira/browse/AMBARI-24889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24889. -- Resolution: Fixed Committed to trunk > Pre-Upgrade Checklist: Components are Installed > --- > > Key: AMBARI-24889 > URL: https://issues.apache.org/jira/browse/AMBARI-24889 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
[ https://issues.apache.org/jira/browse/AMBARI-24890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685372#comment-16685372 ] Hudson commented on AMBARI-24890: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10285 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10285/]) AMBARI-24890 Restart option should not be shown if service components (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a348fa257e7c188c63d1038fa92a1aae8c4902b2]) * (edit) ambari-web/app/views/main/service/info/configs.js * (edit) ambari-web/app/templates/main/service/info/configs.hbs > Restart option should not be shown if service components are not created in a > cluster > - > > Key: AMBARI-24890 > URL: https://issues.apache.org/jira/browse/AMBARI-24890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-12 at 10.40.42 PM.png, Screen Shot > 2018-11-12 at 10.42.58 PM.png > > Time Spent: 1h > Remaining Estimate: 0h > > In the attached screenshot "Restart Nodemanager" should not be shown because > NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
Istvan Tobias created AMBARI-24891: -- Summary: [Log Serach UI] The Log Index Filter panel does not work Key: AMBARI-24891 URL: https://issues.apache.org/jira/browse/AMBARI-24891 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias The Log Index Filter settings modal does not load the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685367#comment-16685367 ] ASF GitHub Bot commented on AMBARI-24551: - asfgit commented on issue #22: [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps URL: https://github.com/apache/ambari-logsearch/pull/22#issuecomment-438305725 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/45/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.8.0 > > Original Estimate: 4h > Time Spent: 3h 40m > Remaining Estimate: 20m > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685359#comment-16685359 ] ASF GitHub Bot commented on AMBARI-24551: - tobias-istvan opened a new pull request #22: [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps URL: https://github.com/apache/ambari-logsearch/pull/22 # What changes were proposed in this pull request? Branch fix for #5 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.8.0 > > Original Estimate: 4h > Time Spent: 3h 40m > Remaining Estimate: 20m > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
[ https://issues.apache.org/jira/browse/AMBARI-24890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-24890. --- Resolution: Fixed > Restart option should not be shown if service components are not created in a > cluster > - > > Key: AMBARI-24890 > URL: https://issues.apache.org/jira/browse/AMBARI-24890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-12 at 10.40.42 PM.png, Screen Shot > 2018-11-12 at 10.42.58 PM.png > > Time Spent: 1h > Remaining Estimate: 0h > > In the attached screenshot "Restart Nodemanager" should not be shown because > NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
[ https://issues.apache.org/jira/browse/AMBARI-24890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685333#comment-16685333 ] Andrii Tkach commented on AMBARI-24890: --- committed to trunk > Restart option should not be shown if service components are not created in a > cluster > - > > Key: AMBARI-24890 > URL: https://issues.apache.org/jira/browse/AMBARI-24890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-12 at 10.40.42 PM.png, Screen Shot > 2018-11-12 at 10.42.58 PM.png > > Time Spent: 1h > Remaining Estimate: 0h > > In the attached screenshot "Restart Nodemanager" should not be shown because > NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24877) Heatmap tab, metrics tab and QuickLinks section in summary tab should be hidden if service has only client service component
[ https://issues.apache.org/jira/browse/AMBARI-24877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685251#comment-16685251 ] Hudson commented on AMBARI-24877: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10284 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10284/]) AMBARI-24877 Heatmap tab, metrics tab and QuickLinks section in summary (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5f7ab52acc19a73fec5fa65ab3993ba3acd8c3bd]) * (edit) ambari-web/app/views/common/quick_view_link_view.js * (edit) ambari-web/app/views/main/service/item.js * (edit) ambari-web/test/views/common/quick_link_view_test.js * (edit) ambari-web/test/views/main/service/item_test.js > Heatmap tab, metrics tab and QuickLinks section in summary tab should be > hidden if service has only client service component > > > Key: AMBARI-24877 > URL: https://issues.apache.org/jira/browse/AMBARI-24877 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-06 at 2.20.16 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > HDFS client and YARN client service component is created but other HDFS/YARN > components are not created via blueprint deploy > *Expected behavior:* > Heatmap tab, metrics tab and QuickLinks section should be hidden if a service > does not have any non-client servicecomponent created in the cluster > *Actual behavior:* > Heatmap and metrics tab are shown with empty metrics and no graphs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685237#comment-16685237 ] Hudson commented on AMBARI-24551: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #29 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/29/]) [AMBARI-24551] [Log Search UI] get rid of redundant requests after (tobias.istvan: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=d09e5c320836b7b61edaa64c08ea1a7a75b3036d]) * (edit) ambari-logsearch-web/src/app/services/history-manager.service.ts [AMBARI-24551] [Log Search UI] get rid of redundant requests after (tobias.istvan: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=dcadc20a3d0479a8dd87b4f0e3a3787e12902695]) * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.html * (edit) ambari-logsearch-web/src/app/services/history-manager.service.ts * (edit) ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch-web/src/app/services/logs-filtering-utils.service.ts [AMBARI-24551] [Log Search UI] get rid of redundant requests after (tobias.istvan: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=30c315786837a9a89b164338c0ba4893d70bcd9a]) * (edit) ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts * (edit) ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.ts * (edit) ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts * (edit) ambari-logsearch-web/src/app/services/filter-history.guard.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts * (edit) ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts * (edit) ambari-logsearch-web/src/app/components/cluster-filter/cluster-filter.component.ts * (edit) ambari-logsearch-web/src/app/components/pagination-controls/pagination-controls.component.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/filter-dropdown/filter-dropdown.component.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch-web/src/app/services/history-manager.service.ts * (edit) ambari-logsearch-web/src/app/components/search-box/search-box.component.ts * (edit) ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts [AMBARI-24551] [Log Search UI] get rid of redundant requests after (tobias.istvan: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=1990a758cdd883d677c7a18899e4eedcf527106b]) * (edit) ambari-logsearch-web/src/app/classes/models/store.ts * (edit) ambari-logsearch-web/src/app/components/filter-history-manager/filter-history-manager.component.html * (edit) ambari-logsearch-web/src/app/modules/app-load/app-load.module.ts * (edit) ambari-logsearch-web/src/app/store/reducers/filter-history.reducers.ts * (edit) ambari-logsearch-web/src/app/app-routing.module.ts * (edit) ambari-logsearch-web/src/app/services/filter-history.guard.ts * (edit) ambari-logsearch-web/src/app/components/login-form/login-form.component.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch-web/src/app/store/selectors/data-availability.selectors.ts * (edit) ambari-logsearch-web/src/app/components/app.component.ts * (edit) ambari-logsearch-web/src/app/store/selectors/filter-history.selectors.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html * (edit) ambari-logsearch-web/src/app/components/filter-history-manager/filter-history-manager.component.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.less * (edit) ambari-logsearch-web/src/app/store/selectors/app-state.selectors.ts * (edit) ambari-logsearch-web/src/app/app.module.ts * (edit) ambari-logsearch-web/src/app/store/selectors/auth.selectors.ts [AMBARI-24551] [Log Search UI] get rid of redundant requests after (tobias.istvan: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=12fc1b7261d396c7d7c7774a9277c536c763e1c2]) * (edit) ambari-logsearch-web/src/app/components/filter-history-manager/filter-history-manager.component.ts * (add) ambari-logsearch-web/src/app/services/filter-labels.service.ts * (edit) ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (add) ambari-logsearch-web/src/app/store/selectors/components.selectors.ts * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch-web/src/app/store/selectors/filter-history.selectors.ts * (edit) ambari-logsearch-web/src/app/store/selectors/app-state.selectors.ts * (edit) ambari-logsearch-web/src/assets/i18n/en.json * (add)
[jira] [Commented] (AMBARI-24877) Heatmap tab, metrics tab and QuickLinks section in summary tab should be hidden if service has only client service component
[ https://issues.apache.org/jira/browse/AMBARI-24877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685212#comment-16685212 ] Andrii Tkach commented on AMBARI-24877: --- committed to trunk > Heatmap tab, metrics tab and QuickLinks section in summary tab should be > hidden if service has only client service component > > > Key: AMBARI-24877 > URL: https://issues.apache.org/jira/browse/AMBARI-24877 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-06 at 2.20.16 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > HDFS client and YARN client service component is created but other HDFS/YARN > components are not created via blueprint deploy > *Expected behavior:* > Heatmap tab, metrics tab and QuickLinks section should be hidden if a service > does not have any non-client servicecomponent created in the cluster > *Actual behavior:* > Heatmap and metrics tab are shown with empty metrics and no graphs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24877) Heatmap tab, metrics tab and QuickLinks section in summary tab should be hidden if service has only client service component
[ https://issues.apache.org/jira/browse/AMBARI-24877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-24877. --- Resolution: Fixed > Heatmap tab, metrics tab and QuickLinks section in summary tab should be > hidden if service has only client service component > > > Key: AMBARI-24877 > URL: https://issues.apache.org/jira/browse/AMBARI-24877 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-06 at 2.20.16 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > HDFS client and YARN client service component is created but other HDFS/YARN > components are not created via blueprint deploy > *Expected behavior:* > Heatmap tab, metrics tab and QuickLinks section should be hidden if a service > does not have any non-client servicecomponent created in the cluster > *Actual behavior:* > Heatmap and metrics tab are shown with empty metrics and no graphs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item
[ https://issues.apache.org/jira/browse/AMBARI-24887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685196#comment-16685196 ] Hudson commented on AMBARI-24887: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #406 (See [https://builds.apache.org/job/Ambari-branch-2.7/406/]) [AMBARI-24887] [Log Search UI] The component filter dropdown does not (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4295bb16c439cbc8fb0e7362f19768dde1477868]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/cluster-filter/cluster-filter.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/pagination-controls/pagination-controls.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/filter-dropdown/filter-dropdown.component.ts > [Log Search UI] The component filter dropdown does not select any item > -- > > Key: AMBARI-24887 > URL: https://issues.apache.org/jira/browse/AMBARI-24887 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The user can not select any components from the component filter dropdown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24881) Implement JSON parsing code to handle Add Service request
[ https://issues.apache.org/jira/browse/AMBARI-24881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685197#comment-16685197 ] Hudson commented on AMBARI-24881: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10283 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10283/]) AMBARI-24881 Add Service Request JSON (benyoka) (#2594) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=664d14dae54655a092a304400944bae7e24d1275]) * (add) ambari-server/src/test/resources/add_service_api/request2.json * (add) ambari-server/src/test/resources/add_service_api/request4.json * (add) ambari-server/src/test/resources/add_service_api/request3.json * (add) ambari-server/src/test/resources/add_service_api/configurable2.json * (add) ambari-server/src/test/java/org/apache/ambari/server/controller/AddServiceRequestTest.java * (add) ambari-server/src/test/resources/add_service_api/request1.json * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/AddServiceRequest.java * (add) ambari-server/src/test/resources/add_service_api/request_invalid_2.json * (add) ambari-server/src/test/resources/add_service_api/configurable.json * (add) ambari-server/src/test/resources/add_service_api/request_invalid_1.json * (add) ambari-server/src/main/java/org/apache/ambari/server/topology/Configurable.java * (add) ambari-server/src/test/java/org/apache/ambari/server/topology/ConfigurableTest.java > Implement JSON parsing code to handle Add Service request > - > > Key: AMBARI-24881 > URL: https://issues.apache.org/jira/browse/AMBARI-24881 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: trunk > > Time Spent: 2.5h > Remaining Estimate: 0h > > This JIRA tracks the work involved to implement the parsing/handling code for > the JSON request and response elements of the "Add Service" API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685185#comment-16685185 ] ASF GitHub Bot commented on AMBARI-24551: - asfgit commented on issue #5: [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps URL: https://github.com/apache/ambari-logsearch/pull/5#issuecomment-438263607 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/44/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.8.0 > > Original Estimate: 4h > Time Spent: 3h 40m > Remaining Estimate: 20m > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685195#comment-16685195 ] Hudson commented on AMBARI-24572: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #406 (See [https://builds.apache.org/job/Ambari-branch-2.7/406/]) AMBARI-24572 Fixing the cluster name alignment (sjanardhanhw via (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=56ffa1e2236a517741ef22fb6ea19ff2a3414341]) * (edit) ambari-web/app/styles/top-nav.less > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
[ https://issues.apache.org/jira/browse/AMBARI-24890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24890: Labels: pull-request-available (was: ) > Restart option should not be shown if service components are not created in a > cluster > - > > Key: AMBARI-24890 > URL: https://issues.apache.org/jira/browse/AMBARI-24890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-12 at 10.40.42 PM.png, Screen Shot > 2018-11-12 at 10.42.58 PM.png > > > In the attached screenshot "Restart Nodemanager" should not be shown because > NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24889) Pre-Upgrade Checklist: Components are Installed
[ https://issues.apache.org/jira/browse/AMBARI-24889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24889: Labels: pull-request-available (was: ) > Pre-Upgrade Checklist: Components are Installed > --- > > Key: AMBARI-24889 > URL: https://issues.apache.org/jira/browse/AMBARI-24889 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
[ https://issues.apache.org/jira/browse/AMBARI-24890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24890: -- Attachment: Screen Shot 2018-11-12 at 10.42.58 PM.png Screen Shot 2018-11-12 at 10.40.42 PM.png > Restart option should not be shown if service components are not created in a > cluster > - > > Key: AMBARI-24890 > URL: https://issues.apache.org/jira/browse/AMBARI-24890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-12 at 10.40.42 PM.png, Screen Shot > 2018-11-12 at 10.42.58 PM.png > > > In the attached screenshot "Restart Nodemanager" should not be shown because > NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24890) Restart option should not be shown if service components are not created in a cluster
Andrii Tkach created AMBARI-24890: - Summary: Restart option should not be shown if service components are not created in a cluster Key: AMBARI-24890 URL: https://issues.apache.org/jira/browse/AMBARI-24890 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.8.0 In the attached screenshot "Restart Nodemanager" should not be shown because NodeManager service component is not present in the cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24889) Pre-Upgrade Checklist: Components are Installed
[ https://issues.apache.org/jira/browse/AMBARI-24889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24889: Assignee: Antonenko Alexander > Pre-Upgrade Checklist: Components are Installed > --- > > Key: AMBARI-24889 > URL: https://issues.apache.org/jira/browse/AMBARI-24889 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24889) Pre-Upgrade Checklist: Components are Installed
Antonenko Alexander created AMBARI-24889: Summary: Pre-Upgrade Checklist: Components are Installed Key: AMBARI-24889 URL: https://issues.apache.org/jira/browse/AMBARI-24889 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685158#comment-16685158 ] Hudson commented on AMBARI-24572: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10282 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10282/]) AMBARI-24572 Fixing the cluster name alignment (sjanardhanhw via (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ccdac060f9b0e3e8a17d58b30f4aca9c9362741c]) * (edit) ambari-web/app/styles/top-nav.less > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[
https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685147#comment-16685147
]
ASF GitHub Bot commented on AMBARI-24551:
-
aBabiichuk commented on a change in pull request #5: [AMBARI-24551] [Log Search
UI] get rid of redundant requests after undoing or redoing several history steps
URL: https://github.com/apache/ambari-logsearch/pull/5#discussion_r233022631
##
File path:
ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
##
@@ -74,27 +72,13 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
}
ngOnInit() {
-this.subscriptions.push(
- this.selectedClusterName$.subscribe(
-(clusterName: string) => this.setModalSubmitDisabled(!(!!clusterName))
- )
+this.selectedClusterName$.takeUntil(this.destroyed$).subscribe(
+ (clusterName: string) => this.setModalSubmitDisabled(!(!!clusterName))
Review comment:
Why not just `setModalSubmitDisabled(!clusterName)`?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] get rid of redundant requests after undoing or redoing
> several history steps
>
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Original Estimate: 4h
> Time Spent: 3h 40m
> Remaining Estimate: 20m
>
> After undoing or redoing more than one history items several redundant API
> requests are sent. This occurs because changes for several filter controls
> are applied step-by-step, and each control change generates new request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[
https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685145#comment-16685145
]
ASF GitHub Bot commented on AMBARI-24551:
-
aBabiichuk commented on a change in pull request #5: [AMBARI-24551] [Log Search
UI] get rid of redundant requests after undoing or redoing several history steps
URL: https://github.com/apache/ambari-logsearch/pull/5#discussion_r233011840
##
File path:
ambari-logsearch-web/src/app/components/filter-history-manager/filter-history-manager.component.ts
##
@@ -0,0 +1,382 @@
+import { Component, OnInit, OnDestroy, Input } from '@angular/core';
+import { Subject } from 'rxjs/Subject';
+import { Observable } from 'rxjs/Observable';
+import { Store } from '@ngrx/store';
+import { AppStore } from '@app/classes/models/store';
+import {
+ selectActiveFilterHistoryChangesUndoItems,
+ selectActiveFilterHistoryChangesRedoItems,
+ selectActiveFilterHistoryChanges,
+ selectActiveFilterHistoryChangeIndex
+} from '@app/store/selectors/filter-history.selectors';
+import { FilterUrlParamChange } from
'@app/classes/models/filter-url-param-change.interface';
+import { Router, UrlTree, UrlSegmentGroup } from '@angular/router';
+import {
+ LogsFilteringUtilsService,
+ defaultUrlParamsForFiltersByLogsType,
+ UrlParamDifferences,
+ UrlParamsDifferenceType
+} from '@app/services/logs-filtering-utils.service';
+import { selectActiveLogsType } from
'@app/store/selectors/app-state.selectors';
+import { LogsType } from '@app/classes/string';
+import { TranslateService } from '@ngx-translate/core';
+import { selectComponentsLabels } from
'@app/store/selectors/components.selectors';
+import { selectDefaultAuditLogsFields } from
'@app/store/selectors/audit-logs-fields.selectors';
+import { selectServiceLogsFieldState } from
'@app/store/selectors/service-logs-fields.selectors';
+import { BehaviorSubject } from 'rxjs/BehaviorSubject';
+import { ListItem } from '@app/classes/list-item';
+
+import * as moment from 'moment';
+import { SearchBoxParameter } from '@app/classes/filtering';
+import { LogField } from '@app/classes/object';
+
+export const urlParamsActionType = {
+ clusters: 'multiple',
+ timeRange: 'single',
+ components: 'multiple',
+ levels: 'multiple',
+ hosts: 'multiple',
+ sortingKey: 'single',
+ sortingType: 'single',
+ pageSize: 'single',
+ page: 'single',
+ query: 'query',
+ users: 'multiple'
+};
+
+@Component({
+ selector: 'filter-history-manager',
+ templateUrl: './filter-history-manager.component.html',
+ styleUrls: ['./filter-history-manager.component.less']
+})
+export class FilterHistoryManagerComponent implements OnInit, OnDestroy {
+
+ @Input()
+ labelSeparator = ' | ';
+
+ activeLogsType$: Observable =
this.store.select(selectActiveLogsType);
+
+ componentsLabels$: Observable<{[key: string]: string}> =
this.store.select(selectComponentsLabels);
+ componentsLabelsLocalCopy$: BehaviorSubject<{[key: string]: string}> = new
BehaviorSubject({});
+
+ activeHistoryChangeIndex$: Observable =
this.store.select(selectActiveFilterHistoryChangeIndex);
+
+ activeHistoryItems$: Observable =
this.store.select(selectActiveFilterHistoryChanges);
+ hasActiveHistoryItems$: Observable = this.activeHistoryItems$
+.map(items => items && items.length > 0).startWith(false);
+ activeHistoryItemLabels$: Observable<{[key: string]: string}[]> =
Observable.combineLatest(
+this.activeHistoryItems$,
+this.activeLogsType$,
+this.componentsLabels$ // this is just to recalculate the labels when the
components arrived
+ ).map(result => this.mapHistoryItemsToHistoryItemLabels(result));
+ activeHistoryListItems$: Observable = Observable.combineLatest(
+this.activeHistoryItemLabels$.map((items) =>
this.mapHistoryItemLabelsToListItems(items, this.labelSeparator)),
+this.store.select(selectActiveFilterHistoryChangeIndex)
+ ).map(([listItems, changeIndex]: [ListItem[], number]): ListItem[] =>
listItems.map((item, index) => {
+item.cssClass = index === changeIndex ? 'active' : (index === 0 ?
'initial' : '');
+return item;
+ }));
+
+ activeUndoHistoryItems$: Observable =
this.store.select(selectActiveFilterHistoryChangesUndoItems);
+ hasActiveUndoHistoryItems$: Observable =
this.activeUndoHistoryItems$
+.map(items => items && items.length > 0).startWith(false);
+ activeUndoHistoryListItems$: Observable =
Observable.combineLatest(
+this.activeHistoryListItems$,
+this.store.select(selectActiveFilterHistoryChangeIndex)
+ ).map(([listItems, activeChangeIndex]: [ListItem[], number]): ListItem[] =>
listItems.slice(0, activeChangeIndex));
+
+ activeRedoHistoryItems$: Observable =
this.store.select(selectActiveFilterHistoryChangesRedoItems);
+ hasActiveRedoHistoryItems$: Observable =
this.activeRedoHistoryItems$
+.map(items => items && items.length > 0).startWith(false);
+
[jira] [Commented] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685143#comment-16685143 ] Hudson commented on AMBARI-24603: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #405 (See [https://builds.apache.org/job/Ambari-branch-2.7/405/]) AMBARI-24603 Better scrolling for long list of components in dropdown in (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=25ab8d75d24c125a0cd09a42e78c7a136d5698fe]) * (edit) ambari-web/app/styles/hosts.less > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685130#comment-16685130 ] Hudson commented on AMBARI-24603: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10281 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10281/]) AMBARI-24603 Better scrolling for long list of components in dropdown in (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a22df8ad540fa9fbe7034d6d7ef87beec29414a4]) * (edit) ambari-web/app/styles/hosts.less > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item
[ https://issues.apache.org/jira/browse/AMBARI-24887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24887: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] The component filter dropdown does not select any item > -- > > Key: AMBARI-24887 > URL: https://issues.apache.org/jira/browse/AMBARI-24887 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The user can not select any components from the component filter dropdown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24603. - Resolution: Fixed > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24572. - Resolution: Fixed > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24603: Fix Version/s: (was: 2.8.0) 2.7.3 > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24572: Fix Version/s: (was: 2.8.0) 2.7.3 > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24845) Sometimes host status still in heartbeat lost after agent become heartbeating
[ https://issues.apache.org/jira/browse/AMBARI-24845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24845. --- Resolution: Fixed > Sometimes host status still in heartbeat lost after agent become heartbeating > - > > Key: AMBARI-24845 > URL: https://issues.apache.org/jira/browse/AMBARI-24845 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Sometimes initial component states update does not fire host status recheck > and host still in heartbeat lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24784:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch,
> AMBARI-24784.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24859) Admin View: Apache Ambari logo and favicon does not show when using Knox Gateway
[ https://issues.apache.org/jira/browse/AMBARI-24859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24859. --- Resolution: Fixed > Admin View: Apache Ambari logo and favicon does not show when using Knox > Gateway > > > Key: AMBARI-24859 > URL: https://issues.apache.org/jira/browse/AMBARI-24859 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item
[ https://issues.apache.org/jira/browse/AMBARI-24887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24887: --- Status: Patch Available (was: In Progress) > [Log Search UI] The component filter dropdown does not select any item > -- > > Key: AMBARI-24887 > URL: https://issues.apache.org/jira/browse/AMBARI-24887 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > The user can not select any components from the component filter dropdown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24883) Previous config versions view of HBase service has missing configs
[ https://issues.apache.org/jira/browse/AMBARI-24883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24883: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Previous config versions view of HBase service has missing configs > -- > > Key: AMBARI-24883 > URL: https://issues.apache.org/jira/browse/AMBARI-24883 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24888) Fix SingleHostTopologyUpdater
Balázs Bence Sári created AMBARI-24888:
--
Summary: Fix SingleHostTopologyUpdater
Key: AMBARI-24888
URL: https://issues.apache.org/jira/browse/AMBARI-24888
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Balázs Bence Sári
Assignee: Balázs Bence Sári
Fix For: trunk
Newer Ambari installations often require clusters with partially installed
services (some required components missing). These clusters typically connect
to other clusters and use some of the services from the external cluster.
Ambari provides support for this by accepting blueprints with
{{validate_topology=false}} flag, however the support is incomplete as usually
exceptions are thrown later during the installation process with such
blueprints.
Most of the exceptions are thrown in the {{SingleHostTopologyUpdater}} class
which acts as a validator in addition to being a property updater.
The property update logic in {{SingleHostTopologyUpdater}} is the following:
* All {{SingleHostTopologyUpdater}} instances are associated with a component
(e.g. NAMENODE)
* first, it does {{%HOSTGROUP%}} token replacement by calling the supertclas's
method. *If this is successful, the replaced value is returned without any
validation* (even with invalid topology)
* if there is only one matching hostgroup for the updater's associated
component, *validation will be skipped too*. If the property's value contains
{{localhost}}, it will be replaced with the FQDN of one of the host from the
matching host groups.
* In all other cases, a validation process starts which tries to match a
sequence of valid cases with the actual topology. If one of the cases match,
the property will be returned unchanged. In none matches, an exception is
thrown.
As it can be seen above, the validation logic is not completely consistent.
There are cases where validation is bypassed. E.g. if the updater encounters a
{{%HOSTROUP%}} token, it will do the replacement even if the topology is broken
and the associated component is missing.
*Proposed solution*
Features:
* A general solution
* Still protects from accidentally broken topology
* Permits properties to point to external services
* Very easy to implement (just a few lines).
The proposed solution would simply leave the update logic in
{{SingleHostTopologyUpdater}} as is and would restrict validation for the cases
when the property contains {{localhost}}. This latter indicates that the
property has the stack default value.
This way, validation would still be performed in most cases when a component is
left out from the blueprint by mistake.
However, when a component is left out intentionally and the respective
properties are intentionally set to point to an external FQDN or set to empty
values, validation would be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24877) Heatmap tab, metrics tab and QuickLinks section in summary tab should be hidden if service has only client service component
[ https://issues.apache.org/jira/browse/AMBARI-24877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24877: Labels: pull-request-available (was: ) > Heatmap tab, metrics tab and QuickLinks section in summary tab should be > hidden if service has only client service component > > > Key: AMBARI-24877 > URL: https://issues.apache.org/jira/browse/AMBARI-24877 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-11-06 at 2.20.16 PM.png > > > HDFS client and YARN client service component is created but other HDFS/YARN > components are not created via blueprint deploy > *Expected behavior:* > Heatmap tab, metrics tab and QuickLinks section should be hidden if a service > does not have any non-client servicecomponent created in the cluster > *Actual behavior:* > Heatmap and metrics tab are shown with empty metrics and no graphs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24833. --- Resolution: Fixed > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685012#comment-16685012 ] Hudson commented on AMBARI-24833: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #28 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/28/]) AMBARI-24833. Simplify HDFS client usage + use core-site.xml (#21) (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=db5fb3db496beec489a55704eaf9b58d9d683bac]) * (delete) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/AbstractCloudClient.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CloudStorageUploader.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/UploadClientFactory.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/HDFSUploadClient.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/RolloverConfig.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/LogFeederHDFSUtil.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/UploadClient.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CloudStorageLoggerFactory.java * (delete) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/OutputConfig.java * (add) ambari-logsearch-logfeeder/src/main/resources/core-site.xml * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/HDFSS3UploadClient.java * (edit) ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties * (delete) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/CloudStorageOutputConfig.java * (delete) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/HdfsOutputConfig.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/S3OutputConfig.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/BucketConfig.java * (add) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/ExternalHDFSUploadClient.java * (add) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/ExternalHdfsOutputConfig.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/S3UploadClient.java * (add) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/AbstractS3CloudClient.java > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24875) Log Search: cannot build sub-modules separately
[ https://issues.apache.org/jira/browse/AMBARI-24875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24875. --- Resolution: Fixed > Log Search: cannot build sub-modules separately > --- > > Key: AMBARI-24875 > URL: https://issues.apache.org/jira/browse/AMBARI-24875 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[
https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684998#comment-16684998
]
ASF GitHub Bot commented on AMBARI-24833:
-
oleewere closed pull request #21: AMBARI-24833. Simplify HDFS client usage +
use core-site.xml
URL: https://github.com/apache/ambari-logsearch/pull/21
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
index f528c45a02..11d351f23d 100644
---
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
+++
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
@@ -113,9 +113,13 @@
public static final String CLOUD_STORAGE_DESTINATION =
"logfeeder.cloud.storage.destination";
public static final String CLOUD_STORAGE_UPLOAD_ON_SHUTDOWN =
"logfeeder.cloud.storage.upload.on.shutdown";
public static final String CLOUD_STORAGE_UPLOADER_INTERVAL_SECONDS =
"logfeeder.cloud.storage.uploader.interval.seconds";
+ public static final String CLOUD_STORAGE_BUCKET =
"logfeeder.cloud.storage.bucket";
public static final String CLOUD_STORAGE_BUCKET_BOOTSTRAP =
"logfeeder.cloud.storage.bucket.bootstrap";
public static final String CLOUD_STORAGE_USE_HDFS_CLIENT =
"logfeeder.cloud.storage.use.hdfs.client";
+ public static final String CLOUD_STORAGE_CUSTOM_FS =
"logfeeder.cloud.storage.custom.fs";
+ public static final String CLOUD_STORAGE_BASE_PATH =
"logfeeder.cloud.storage.base.path";
+ public static final String CLOUD_ROLLOVER_ARCHIVE_LOCATION =
"logfeeder.cloud.rollover.archive.base.dir";
public static final String CLOUD_ROLLOVER_THRESHOLD_TIME_MIN =
"logfeeder.cloud.rollover.threshold.min";
public static final String CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE =
"logfeeder.cloud.rollover.threshold.size";
public static final String CLOUD_ROLLOVER_USE_GZIP =
"logfeeder.cloud.rollover.use.gzip";
@@ -126,14 +130,12 @@
public static final String HDFS_HOST = "logfeeder.hdfs.host";
public static final String HDFS_PORT = "logfeeder.hdfs.port";
public static final String HDFS_USER = "logfeeder.hdfs.user";
- public static final String HDFS_OUTPUT_BASE_DIR =
"logfeeder.hdfs.output.base.dir";
public static final String HDFS_FILE_PERMISSIONS =
"logfeeder.hdfs.file.permissions";
public static final String HDFS_KERBEROS = "logfeeder.hdfs.kerberos";
public static final String S3_ENDPOINT = "logfeeder.s3.endpoint";
public static final String S3_ENDPOINT_DEFAULT = "https://s3.amazonaws.com;;
public static final String S3_REGION = "logfeeder.s3.region";
- public static final String S3_BUCKET = "logfeeder.s3.bucket";
public static final String S3_OBJECT_ACL = "logfeeder.s3.object.acl";
public static final String S3_PATH_STYLE_ACCESS =
"logfeeder.s3.path.style.access";
public static final String S3_MULTIOBJECT_DELETE_ENABLE =
"logfeeder.s3.multiobject.delete.enable";
diff --git
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
index e89f7f4ca0..d32e1df9db 100644
---
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
+++
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
@@ -19,7 +19,7 @@
package org.apache.ambari.logfeeder.conf;
import org.apache.ambari.logfeeder.common.LogFeederConstants;
-import org.apache.ambari.logfeeder.conf.output.HdfsOutputConfig;
+import org.apache.ambari.logfeeder.conf.output.ExternalHdfsOutputConfig;
import org.apache.ambari.logfeeder.conf.output.RolloverConfig;
import org.apache.ambari.logfeeder.conf.output.S3OutputConfig;
import org.apache.ambari.logfeeder.plugin.common.LogFeederProperties;
@@ -47,13 +47,13 @@
private Environment env;
@Inject
- private HdfsOutputConfig hdfsOutputConfig;
+ private RolloverConfig rolloverConfig;
@Inject
private S3OutputConfig s3OutputConfig;
@Inject
- private RolloverConfig rolloverConfig;
+ private ExternalHdfsOutputConfig hdfsOutputConfig;
private Properties properties;
@@ -238,7 +238,7 @@
sources = {LogFeederConstants.LOGFEEDER_PROPERTIES_FILE}
)
@Value("${" + LogFeederConstants.CLOUD_STORAGE_UPLOAD_ON_SHUTDOWN +
":false}")
- public boolean cloudStorageUploadOnShutdown;
+ private boolean cloudStorageUploadOnShutdown;
@LogSearchPropertyDescription(
[jira] [Created] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item
Istvan Tobias created AMBARI-24887: -- Summary: [Log Search UI] The component filter dropdown does not select any item Key: AMBARI-24887 URL: https://issues.apache.org/jira/browse/AMBARI-24887 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias Fix For: 2.7.3 The user can not select any components from the component filter dropdown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item
[ https://issues.apache.org/jira/browse/AMBARI-24887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24887: Labels: pull-request-available (was: ) > [Log Search UI] The component filter dropdown does not select any item > -- > > Key: AMBARI-24887 > URL: https://issues.apache.org/jira/browse/AMBARI-24887 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 4h > Remaining Estimate: 4h > > The user can not select any components from the component filter dropdown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24885) Views Page redirecting to Home page when User doesn't have access to any group and just have access to view
[ https://issues.apache.org/jira/browse/AMBARI-24885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-24885: -- Summary: Views Page redirecting to Home page when User doesn't have access to any group and just have access to view (was: Ambari Files view not working when User doesnt have access to any group and just have access to Filesview) > Views Page redirecting to Home page when User doesn't have access to any > group and just have access to view > --- > > Key: AMBARI-24885 > URL: https://issues.apache.org/jira/browse/AMBARI-24885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: pull-request-available > Attachments: Views Issue.mov > > Time Spent: 40m > Remaining Estimate: 0h > > Ambari Files view not working when User doesnt have access to any group and > just have access to Filesview > The Page redirects to View's Home Page each time when I click on the files > view. > The issue is with javascript > attached video of the issue. [^Views Issue.mov] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
