[jira] [Updated] (AMBARI-24902) ATS 1.5 does not start in DL cluster without HDFS
[ https://issues.apache.org/jira/browse/AMBARI-24902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24902: - Status: Patch Available (was: Open) > ATS 1.5 does not start in DL cluster without HDFS > - > > Key: AMBARI-24902 > URL: https://issues.apache.org/jira/browse/AMBARI-24902 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24902.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24902) ATS 1.5 does not start in DL cluster without HDFS
Andrew Onischuk created AMBARI-24902: Summary: ATS 1.5 does not start in DL cluster without HDFS Key: AMBARI-24902 URL: https://issues.apache.org/jira/browse/AMBARI-24902 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.8.0 Attachments: AMBARI-24902.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24902) ATS 1.5 does not start in DL cluster without HDFS
[ https://issues.apache.org/jira/browse/AMBARI-24902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24902: - Attachment: AMBARI-24902.patch > ATS 1.5 does not start in DL cluster without HDFS > - > > Key: AMBARI-24902 > URL: https://issues.apache.org/jira/browse/AMBARI-24902 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24902.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24807) Infra Manager: unable to restart job
[ https://issues.apache.org/jira/browse/AMBARI-24807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24807: Resolution: Fixed Status: Resolved (was: Patch Available) > Infra Manager: unable to restart job > > > Key: AMBARI-24807 > URL: https://issues.apache.org/jira/browse/AMBARI-24807 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > When a job is running, a stop signal is sent and just right after the infra > manager process is killed the job remains in Stopping/Unknown state. > In this case the job won't be restarted when Infra Manager is restarted and > also a new instance of the job can not be scheduled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24838) Infra Manager: zookeper connection string
[
https://issues.apache.org/jira/browse/AMBARI-24838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24838:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Infra Manager: zookeper connection string
> -
>
> Key: AMBARI-24838
> URL: https://issues.apache.org/jira/browse/AMBARI-24838
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Infra Manager can not connect to zookeeper if it is installed into a node
> where there is no zookeeper server instance, or the local instance is down.
> * This is caused by that the infra manager stack code does not set the
> zookeeper quorum and the CloudSolrClient falls back to localhost:2181
> * Also the builder which is used for construct an
> org.apache.solr.client.solrj.impl.CloudSolrClient instance is deprecated: it
> does not handle the zookeper connection string fromat which sould be set in
> the stack code.
> {code}
> zkhost0:port[,zkhost1:port...zkhostn:port][/solr_znode]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24895) Infra Manager: code clean up
[ https://issues.apache.org/jira/browse/AMBARI-24895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687580#comment-16687580 ] ASF GitHub Bot commented on AMBARI-24895: - kasakrisz opened a new pull request #15: AMBARI-24895 - Infra Manager: code clean up URL: https://github.com/apache/ambari-infra/pull/15 ## What changes were proposed in this pull request? - rename LOG -> logger - remove slf4j use log4j2 - merge Job Properties and Job Parameter classes ## How was this patch tested? ITs passed Manually: 1. Deploy Ambari and a cluster: zookeeper, infra-solr, logsearch, hdfs, infra-manager 2. Kerberize the cluster 3. Enable archiving for service_logs and set the destination to hdfs on Ambari UI, Infra Manager config 4. Run archiving of service_logs using infra managers rest api 5. check hdfs for archived service logs 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 > Infra Manager: code clean up > > > Key: AMBARI-24895 > URL: https://issues.apache.org/jira/browse/AMBARI-24895 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > * rename LOG -> logger > * remove slf4j use log4j2 > * merge Job Properties and Job Parameter classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24831) Infra Manager: upgrade spring to 5.1.1
[ https://issues.apache.org/jira/browse/AMBARI-24831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-24831. - Resolution: Fixed > Infra Manager: upgrade spring to 5.1.1 > -- > > Key: AMBARI-24831 > URL: https://issues.apache.org/jira/browse/AMBARI-24831 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24832) Infra Manager: set archive file permission on hdfs to 640
[ https://issues.apache.org/jira/browse/AMBARI-24832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-24832. - Resolution: Fixed > Infra Manager: set archive file permission on hdfs to 640 > - > > Key: AMBARI-24832 > URL: https://issues.apache.org/jira/browse/AMBARI-24832 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24878) Infra Manager: kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-24878. - Resolution: Fixed > Infra Manager: kerberos support > --- > > Key: AMBARI-24878 > URL: https://issues.apache.org/jira/browse/AMBARI-24878 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24847) Logsearch: Cannot search for a term that includes spaces or dashes
[ https://issues.apache.org/jira/browse/AMBARI-24847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-24847. - Resolution: Fixed > Logsearch: Cannot search for a term that includes spaces or dashes > -- > > Key: AMBARI-24847 > URL: https://issues.apache.org/jira/browse/AMBARI-24847 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > If I type the following "Some terrible error has happened" I got a huge > amount irrelevant results from Logsearch, this is mainly because the search > term is tokenized and finds every line that contains any of the words even if > I am using ". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24851) Logsearch: debug mode using java 8 and 11
[ https://issues.apache.org/jira/browse/AMBARI-24851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-24851. - Resolution: Fixed > Logsearch: debug mode using java 8 and 11 > - > > Key: AMBARI-24851 > URL: https://issues.apache.org/jira/browse/AMBARI-24851 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Logsearch server can not be started in debug mode if Logsearch is running in > an Ambari managed cluster using java 8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24895) Infra Manager: code clean up
[ https://issues.apache.org/jira/browse/AMBARI-24895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687582#comment-16687582 ] ASF GitHub Bot commented on AMBARI-24895: - asfgit commented on issue #15: AMBARI-24895 - Infra Manager: code clean up URL: https://github.com/apache/ambari-infra/pull/15#issuecomment-438942589 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/22/ 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 > Infra Manager: code clean up > > > Key: AMBARI-24895 > URL: https://issues.apache.org/jira/browse/AMBARI-24895 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > * rename LOG -> logger > * remove slf4j use log4j2 > * merge Job Properties and Job Parameter classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24895) Infra Manager: code clean up
[ https://issues.apache.org/jira/browse/AMBARI-24895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24895: Labels: pull-request-available (was: ) > Infra Manager: code clean up > > > Key: AMBARI-24895 > URL: https://issues.apache.org/jira/browse/AMBARI-24895 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > * rename LOG -> logger > * remove slf4j use log4j2 > * merge Job Properties and Job Parameter classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24901) Handle complex "Add Service" request in ServiceResourceProvider
Doroszlai, Attila created AMBARI-24901:
--
Summary: Handle complex "Add Service" request in
ServiceResourceProvider
Key: AMBARI-24901
URL: https://issues.apache.org/jira/browse/AMBARI-24901
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.8.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 2.8.0
Related to AMBARI-24881, change {{ServiceResourceProvider}} to handle the
complex "Add Service" request. So far only stub logic is needed, details of
the service creation will be filled later.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24878) Infra Manager: kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687472#comment-16687472 ] Hudson commented on AMBARI-24878: - SUCCESS: Integrated in Jenkins build Ambari-Infra-master-Commit #17 (See [https://builds.apache.org/job/Ambari-Infra-master-Commit/17/]) AMBARI-24878 - Infra Manager: kerberos support (#14) (github: [https://gitbox.apache.org/repos/asf?p=ambari-infra.git=commit=d309efe50de7d1bddb6b33a9bad0bf452b8f784a]) * (add) ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/HdfsProperties.java * (edit) ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/ArchivingParameters.java * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentArchivingProperties.java * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentArchivingConfiguration.java * (edit) pom.xml * (edit) ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/HdfsUploader.java > Infra Manager: kerberos support > --- > > Key: AMBARI-24878 > URL: https://issues.apache.org/jira/browse/AMBARI-24878 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24878) Infra Manager: kerberos support
[
https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687469#comment-16687469
]
ASF GitHub Bot commented on AMBARI-24878:
-
kasakrisz closed pull request #14: AMBARI-24878 - Infra Manager: kerberos
support
URL: https://github.com/apache/ambari-infra/pull/14
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-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java
b/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java
index 0118c769..ddc4f000 100644
---
a/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java
+++
b/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java
@@ -18,10 +18,16 @@
*/
package org.apache.ambari.infra;
-import com.fasterxml.jackson.core.JsonParseException;
-import com.fasterxml.jackson.core.type.TypeReference;
-import com.fasterxml.jackson.databind.JsonMappingException;
-import com.fasterxml.jackson.databind.ObjectMapper;
+import static org.apache.commons.lang.StringUtils.isBlank;
+
+import java.io.IOException;
+import java.io.UncheckedIOException;
+import java.net.URI;
+import java.net.URISyntaxException;
+import java.nio.charset.Charset;
+import java.util.HashMap;
+import java.util.Map;
+
import org.apache.commons.io.IOUtils;
import org.apache.http.client.ClientProtocolException;
import org.apache.http.client.methods.CloseableHttpResponse;
@@ -36,15 +42,10 @@
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
-import java.io.IOException;
-import java.io.UncheckedIOException;
-import java.net.URI;
-import java.net.URISyntaxException;
-import java.nio.charset.Charset;
-import java.util.HashMap;
-import java.util.Map;
-
-import static org.apache.commons.lang.StringUtils.isBlank;
+import com.fasterxml.jackson.core.JsonParseException;
+import com.fasterxml.jackson.core.type.TypeReference;
+import com.fasterxml.jackson.databind.JsonMappingException;
+import com.fasterxml.jackson.databind.ObjectMapper;
// TODO: use swagger
public class InfraClient implements AutoCloseable {
@@ -96,6 +97,12 @@ public JobExecutionInfo startJob(String jobName, String
parameters) {
try {
String responseText = execute(new
HttpPost(uriBuilder.build())).getBody();
Map responseContent = new
ObjectMapper().readValue(responseText, new
TypeReference>() {});
+ if (!responseContent.containsKey("jobId"))
+throw new NullPointerException("jobId is not found in start job
responseContent");
+ if (!responseContent.containsKey("jobExecutionData"))
+throw new NullPointerException("jobExecutionData is not found in start
job responseContent");
+ if (!((Map)responseContent.get("jobExecutionData")).containsKey("id"))
+throw new NullPointerException("id is not found in jobExecutionData");
return new JobExecutionInfo(responseContent.get("jobId").toString(),
((Map)responseContent.get("jobExecutionData")).get("id").toString());
} catch (URISyntaxException | JsonParseException | JsonMappingException e)
{
throw new RuntimeException(e);
diff --git
a/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/ArchivingParameters.java
b/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/ArchivingParameters.java
index 6a36f724..5c783d6e 100644
---
a/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/ArchivingParameters.java
+++
b/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/ArchivingParameters.java
@@ -54,6 +54,8 @@
@JsonSerialize(converter = FsPermissionToStringConverter.class)
@JsonDeserialize(converter = StringToFsPermissionConverter.class)
private FsPermission hdfsFilePermission;
+ private String hdfsKerberosPrincipal;
+ private String hdfsKerberosKeytabPath;
private String start;
private String end;
@JsonSerialize(converter = DurationToStringConverter.class)
@@ -172,6 +174,22 @@ public void setHdfsFilePermission(FsPermission
hdfsFilePermission) {
this.hdfsFilePermission = hdfsFilePermission;
}
+ public String getHdfsKerberosPrincipal() {
+return hdfsKerberosPrincipal;
+ }
+
+ public void setHdfsKerberosPrincipal(String hdfsKerberosPrincipal) {
+this.hdfsKerberosPrincipal = hdfsKerberosPrincipal;
+ }
+
+ public String getHdfsKerberosKeytabPath() {
+return hdfsKerberosKeytabPath;
+ }
+
+ public void setHdfsKerberosKeytabPath(String hdfsKerberosKeytabPath) {
+this.hdfsKerberosKeytabPath = hdfsKerberosKeytabPath;
+ }
+
public Optional s3Properties() {
if (isBlank(s3BucketName))
return Optional.empty();
@@ -183,6 +201,18 @@ public
[jira] [Resolved] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24898. -- Resolution: Fixed > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687319#comment-16687319 ] ASF GitHub Bot commented on AMBARI-24899: - asfgit commented on issue #24: [AMBARI-24899] [Log Search UI] Change capture countdown text URL: https://github.com/apache/ambari-logsearch/pull/24#issuecomment-438869660 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/47/ 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] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24899: Labels: pull-request-available (was: ) > [Log Search UI] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24900) [Log Search UI] Display the number of selection for the multiple selection dropdowns
Istvan Tobias created AMBARI-24900: -- Summary: [Log Search UI] Display the number of selection for the multiple selection dropdowns Key: AMBARI-24900 URL: https://issues.apache.org/jira/browse/AMBARI-24900 Project: Ambari Issue Type: Task Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687308#comment-16687308 ] ASF GitHub Bot commented on AMBARI-24899: - tobias-istvan opened a new pull request #24: [AMBARI-24899] [Log Search UI] Change capture countdown text URL: https://github.com/apache/ambari-logsearch/pull/24 # What changes were proposed in this pull request? Simple text change. ## How was this patch tested? Manually and by unit tests: ``` PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 292 of 292 SUCCESS (9.172 secs / 9.074 secs) ✨ Done in 35.67s. ``` Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. 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] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24899: --- Status: Patch Available (was: In Progress) > [Log Search UI] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24899) [Log Search UI] Change capture countdown text
Istvan Tobias created AMBARI-24899: -- Summary: [Log Search UI] Change capture countdown text Key: AMBARI-24899 URL: https://issues.apache.org/jira/browse/AMBARI-24899 Project: Ambari Issue Type: Task Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias The text should be: "Please wait while the logs for your capture period are indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24891: --- Status: Patch Available (was: Open) > [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 >Priority: Blocker > Labels: pull-request-available > > 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-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687282#comment-16687282 ] Hudson commented on AMBARI-24898: - SUCCESS: Integrated in Jenkins build Ambari-Metrics-master-Commit #14 (See [https://builds.apache.org/job/Ambari-Metrics-master-Commit/14/]) [AMBARI-24898] Add cluster drop down to Grafana aggregate dashboards. (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari-metrics.git=commit=881d4d1c66e5350fa0c0e2f980817068e8db13af]) * (edit) ambari-metrics-grafana/ambari-metrics/datasource.js > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687279#comment-16687279
]
ASF GitHub Bot commented on AMBARI-24898:
-
ishanbha closed pull request #10: [AMBARI-24898] Add cluster drop down to
Grafana aggregate dashboards.
URL: https://github.com/apache/ambari-metrics/pull/10
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-metrics-grafana/ambari-metrics/datasource.js
b/ambari-metrics-grafana/ambari-metrics/datasource.js
index 6e14f33..c6885da 100644
--- a/ambari-metrics-grafana/ambari-metrics/datasource.js
+++ b/ambari-metrics-grafana/ambari-metrics/datasource.js
@@ -689,14 +689,9 @@ define([
});
}
// To speed up querying on templatized dashboards.
- var indexOfHosts = -1;
- for (var i = 0; i < templateSrv.variables.length; i++) {
-if (templateSrv.variables[i].name == 'hosts' &&
templateSrv.index.hosts) {
- indexOfHosts = i;
-}
- }
- if (indexOfHosts >= 0) {
-let allHosts = [];
+ let allHosts;
+ if (templateSrv.index.hosts) {
+allHosts = [];
const hosts = templateSrv.index.hosts.options
for (let host of hosts) {
if (host.text.toLowerCase() === "all" && host.selected) {
@@ -705,13 +700,13 @@ define([
} else if (host.selected) {
allHosts.push(host.text);
}
-};
-metricsPromises.push(_.map(options.targets, function (target) {
- target.templatedHost = allHosts ? allHosts : '';
- target.templatedCluster = templatedCluster;
- return getAllHostData(target);
-}));
+}
}
+ metricsPromises.push(_.map(options.targets, function (target) {
+target.templatedHost = allHosts ? allHosts : '';
+target.templatedCluster = templatedCluster;
+return getAllHostData(target);
+ }));
metricsPromises = _.flatten(metricsPromises);
} else {
// Non Templatized Dashboards
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
> Add cluster drop down to Grafana aggregate dashboards.
> --
>
> Key: AMBARI-24898
> URL: https://issues.apache.org/jira/browse/AMBARI-24898
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Currently, the HOST based dashboards (System-Servers, HDFS Namenodes,
> HBase-Regionservers etc) have a dropdown for the cluster level selection.
> This selection determines the set of hosts in the HOST dropdown, and the
> cluster is tagged in the API call made by every graph in the dashboard
> through the "instanceId" query parameter.
> We need to add the cluster dropdown to aggregate dashboards as well. This
> cluster selection will also be tagged in the API call (instanceId) like in
> other dashboards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687094#comment-16687094 ] ASF GitHub Bot commented on AMBARI-24898: - asfgit commented on issue #10: [AMBARI-24898] Add cluster drop down to Grafana aggregate dashboards. URL: https://github.com/apache/ambari-metrics/pull/10#issuecomment-438811143 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/22/ 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 > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[ https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24884. -- Resolution: Fixed > AMS Grafana query editor panel does not work in upgraded version. > - > > Key: AMBARI-24884 > URL: https://issues.apache.org/jira/browse/AMBARI-24884 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Following issues are encountered > - Dropdown list not appearing. > - Metrics not automatically refreshed > - Error on collapsing a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
Ishan Bhatt created AMBARI-24898: Summary: Add cluster drop down to Grafana aggregate dashboards. Key: AMBARI-24898 URL: https://issues.apache.org/jira/browse/AMBARI-24898 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, HBase-Regionservers etc) have a dropdown for the cluster level selection. This selection determines the set of hosts in the HOST dropdown, and the cluster is tagged in the API call made by every graph in the dashboard through the "instanceId" query parameter. We need to add the cluster dropdown to aggregate dashboards as well. This cluster selection will also be tagged in the API call (instanceId) like in other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687087#comment-16687087 ] ASF GitHub Bot commented on AMBARI-24898: - ishanbha opened a new pull request #10: [AMBARI-24898] Add cluster drop down to Grafana aggregate dashboards. URL: https://github.com/apache/ambari-metrics/pull/10 ## What changes were proposed in this pull request? Added logic to include templatized dashboards to proceed without the host variable. 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 > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24898: Labels: pull-request-available (was: ) > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687044#comment-16687044
]
Hudson commented on AMBARI-23478:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10290 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10290/])
[AMBARI-23478] YARN Cluster CPU Usage Graph Always Shows High CPU Usage
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8fee8ce8429229b587e2227f3fd73db474432459])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsDataTransferMethodFactory.java
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24738) Update grafana datasource to get values from new object
[ https://issues.apache.org/jira/browse/AMBARI-24738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24738: --- Fix Version/s: (was: trunk) 2.8.0 > Update grafana datasource to get values from new object > --- > > Key: AMBARI-24738 > URL: https://issues.apache.org/jira/browse/AMBARI-24738 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > In the new grafana version templateSrv doesn't have some fields. We need to > get these values from a different fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[ https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687012#comment-16687012 ] Hudson commented on AMBARI-24884: - SUCCESS: Integrated in Jenkins build Ambari-Metrics-master-Commit #13 (See [https://builds.apache.org/job/Ambari-Metrics-master-Commit/13/]) [AMBARI-24884] Grafana New dashboard edit errors. (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari-metrics.git=commit=63eb69fa8166e93a142629205d88bb4f5f35cca8]) * (edit) ambari-metrics-grafana/ambari-metrics/query_ctrl.js * (edit) ambari-metrics-grafana/ambari-metrics/query_ctrl.ts > AMS Grafana query editor panel does not work in upgraded version. > - > > Key: AMBARI-24884 > URL: https://issues.apache.org/jira/browse/AMBARI-24884 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Following issues are encountered > - Dropdown list not appearing. > - Metrics not automatically refreshed > - Error on collapsing a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-23478.
Resolution: Fixed
PR merged to trunk.
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[
https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687001#comment-16687001
]
ASF GitHub Bot commented on AMBARI-24884:
-
ishanbha closed pull request #9: [AMBARI-24884] AMS Grafana query editor panel
does not work in upgraded version.
URL: https://github.com/apache/ambari-metrics/pull/9
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-metrics-grafana/ambari-metrics/query_ctrl.js
b/ambari-metrics-grafana/ambari-metrics/query_ctrl.js
index 5b5c4a9..b466167 100644
--- a/ambari-metrics-grafana/ambari-metrics/query_ctrl.js
+++ b/ambari-metrics-grafana/ambari-metrics/query_ctrl.js
@@ -31,7 +31,7 @@ var __extends = (this && this.__extends) || (function () {
})();
exports.__esModule = true;
///
-var angular_1 = require("angular");
+require("angular");
var lodash_1 = require("lodash");
var sdk_1 = require("app/plugins/sdk");
var AmbariMetricsQueryCtrl = /** @class */ (function (_super) {
@@ -39,75 +39,6 @@ var AmbariMetricsQueryCtrl = /** @class */ (function
(_super) {
/** @ngInject **/
function AmbariMetricsQueryCtrl($scope, $injector) {
var _this = _super.call(this, $scope, $injector) || this;
-_this.targetBlur = function () {
-this.target.errors = this.validateTarget(this.target);
-// this does not work so good
-if (!lodash_1["default"].isEqual(this.oldTarget, this.target) &&
lodash_1["default"].isEmpty(this.target.errors)) {
-this.oldTarget = angular_1["default"].copy(this.target);
-this.get_data();
-}
-};
-_this.getTextValues = function (metricFindResult) {
-return lodash_1["default"].map(metricFindResult, function (value)
{ return value.text; });
-};
-_this.suggestApps = function (query, callback) {
-this.datasource.suggestApps(query)
-.then(this.getTextValues)
-.then(callback);
-};
-_this.suggestClusters = function (query, callback) {
-this.datasource.suggestClusters(this.target.app)
-.then(this.getTextValues)
-.then(callback);
-};
-_this.suggestHosts = function (query, callback) {
-this.datasource.suggestHosts(this.target.app, this.target.cluster)
-.then(this.getTextValues)
-.then(callback);
-};
-_this.suggestMetrics = function (query, callback) {
-this.datasource.suggestMetrics(query, this.target.app)
-.then(this.getTextValues)
-.then(callback);
-};
-_this.suggestTagKeys = function (query, callback) {
-this.datasource.metricFindQuery('tag_names(' + this.target.metric
+ ')')
-.then(this.getTextValues)
-.then(callback);
-};
-_this.suggestTagValues = function (query, callback) {
-this.datasource.metricFindQuery('tag_values(' + this.target.metric
+ ',' + this.target.currentTagKey + ')')
-.then(this.getTextValues)
-.then(callback);
-};
-_this.addTag = function () {
-if (!this.addTagMode) {
-this.addTagMode = true;
-return;
-}
-if (!this.target.tags) {
-this.target.tags = {};
-}
-this.target.errors = this.validateTarget(this.target);
-if (!this.target.errors.tags) {
-this.target.tags[this.target.currentTagKey] =
this.target.currentTagValue;
-this.target.currentTagKey = '';
-this.target.currentTagValue = '';
-this.targetBlur();
-}
-this.addTagMode = false;
-};
-_this.removeTag = function (key) {
-delete this.target.tags[key];
-this.targetBlur();
-};
-_this.validateTarget = function (target) {
-var errs = {};
-if (target.tags && lodash_1["default"].has(target.tags,
target.currentTagKey)) {
-errs.tags = "Duplicate tag key '" + target.currentTagKey +
"'.";
-}
-return errs;
-};
_this.errors = _this.validateTarget(_this.target);
_this.aggregators = ['none', 'avg', 'sum', 'min', 'max'];
_this.precisions = ['default', 'seconds', 'minutes', 'hours', 'days'];
@@ -131,7 +62,7 @@ var AmbariMetricsQueryCtrl = /** @class */ (function
(_super) {
this.target.seriesAggregator = "none";
}
};
-_this.$watch('target.app', function (newValue) {
+
[jira] [Commented] (AMBARI-24897) Reduce Visible Artifacts from the SPI
[
https://issues.apache.org/jira/browse/AMBARI-24897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686992#comment-16686992
]
Hudson commented on AMBARI-24897:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10289 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10289/])
[AMBARI-24897] Reduce Visible Artifacts from the SPI (#2607) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e6e749d86210ebf0366e2cbb86d5daa0691a477b])
* (edit) ambari-server-spi/pom.xml
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/annotations/UpgradeCheckInfo.java
> Reduce Visible Artifacts from the SPI
> -
>
> Key: AMBARI-24897
> URL: https://issues.apache.org/jira/browse/AMBARI-24897
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The SPI exposes too many internal dependencies to its consumers. Some
> dependencies, such as {{commons-lang}} might be useful and should still be
> provided. Others, such as {{gson}} should be hidden.
> - Remove non-essential dependencies from being seen by consumers of the SPI
> - Prevent consumers of the SPI from double-copying dependencies which Ambari
> Server already has
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23478:
Labels: pull-request-available (was: )
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24897) Reduce Visible Artifacts from the SPI
[
https://issues.apache.org/jira/browse/AMBARI-24897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24897.
--
Resolution: Fixed
> Reduce Visible Artifacts from the SPI
> -
>
> Key: AMBARI-24897
> URL: https://issues.apache.org/jira/browse/AMBARI-24897
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The SPI exposes too many internal dependencies to its consumers. Some
> dependencies, such as {{commons-lang}} might be useful and should still be
> provided. Others, such as {{gson}} should be hidden.
> - Remove non-essential dependencies from being seen by consumers of the SPI
> - Prevent consumers of the SPI from double-copying dependencies which Ambari
> Server already has
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24897) Reduce Visible Artifacts from the SPI
[
https://issues.apache.org/jira/browse/AMBARI-24897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24897:
Labels: pull-request-available (was: )
> Reduce Visible Artifacts from the SPI
> -
>
> Key: AMBARI-24897
> URL: https://issues.apache.org/jira/browse/AMBARI-24897
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> The SPI exposes too many internal dependencies to its consumers. Some
> dependencies, such as {{commons-lang}} might be useful and should still be
> provided. Others, such as {{gson}} should be hidden.
> - Remove non-essential dependencies from being seen by consumers of the SPI
> - Prevent consumers of the SPI from double-copying dependencies which Ambari
> Server already has
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24897) Reduce Visible Artifacts from the SPI
Jonathan Hurley created AMBARI-24897:
Summary: Reduce Visible Artifacts from the SPI
Key: AMBARI-24897
URL: https://issues.apache.org/jira/browse/AMBARI-24897
Project: Ambari
Issue Type: Task
Components: ambari-server-spi
Affects Versions: 2.8.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.8.0
The SPI exposes too many internal dependencies to its consumers. Some
dependencies, such as {{commons-lang}} might be useful and should still be
provided. Others, such as {{gson}} should be hidden.
- Remove non-essential dependencies from being seen by consumers of the SPI
- Prevent consumers of the SPI from double-copying dependencies which Ambari
Server already has
--
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=16686759#comment-16686759
]
Jonathan Hurley commented on AMBARI-24582:
--
This check is used for all cases, including Kerberos. Ambari does pass a
credential string when connecting. Can you elaborate more on the HS2
username/password case you are referring to?
> 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-24896) [Log Search UI] Turn off features in the client when it is not available on backend
Istvan Tobias created AMBARI-24896: -- Summary: [Log Search UI] Turn off features in the client when it is not available on backend Key: AMBARI-24896 URL: https://issues.apache.org/jira/browse/AMBARI-24896 Project: Ambari Issue Type: Task Components: ambari-logsearch, logsearch Affects Versions: 2.7.3 Reporter: Istvan Tobias Assignee: Istvan Tobias Turn off features when it is not available on backend. The list of features and their available status is under `/info/features`. Turn off `Configuration Editor` when `metadata_patterns` is `false`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686639#comment-16686639 ] ASF GitHub Bot commented on AMBARI-24891: - asfgit commented on issue #23: [AMBARI-24891] [Log Serach UI] The Log Index Filter panel does not work URL: https://github.com/apache/ambari-logsearch/pull/23#issuecomment-438691842 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/46/ 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 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 >Priority: Blocker > Labels: pull-request-available > > 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-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686629#comment-16686629 ] ASF GitHub Bot commented on AMBARI-24891: - tobias-istvan commented on issue #23: [AMBARI-24891] [Log Serach UI] The Log Index Filter panel does not work URL: https://github.com/apache/ambari-logsearch/pull/23#issuecomment-438689807 retest this please 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 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 >Priority: Blocker > Labels: pull-request-available > > 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-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686623#comment-16686623 ] ASF GitHub Bot commented on AMBARI-24891: - tobias-istvan opened a new pull request #23: [AMBARI-24891] [Log Serach UI] The Log Index Filter panel does not work URL: https://github.com/apache/ambari-logsearch/pull/23 # What changes were proposed in this pull request? The default selection has not been set by the parent component (ActionMenuComponent). This auto selection has been added to the `ngOnInit`. ## How was this patch tested? It was tested manually and by unit tests: ``` PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 292 of 292 SUCCESS (11.807 secs / 11.638 secs) ✨ Done in 39.18s. ``` Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. 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 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 >Priority: Blocker > Labels: pull-request-available > > The Log Index Filter settings modal does not load the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24891: Labels: pull-request-available (was: ) > [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 >Priority: Blocker > Labels: pull-request-available > > The Log Index Filter settings modal does not load the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23252) Update service metainfo to declare SSO integration support
[
https://issues.apache.org/jira/browse/AMBARI-23252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23252:
--
Description:
Update service metainfo to declare SSO integration support. The following tag
may be optionally set in a service's {{metainfo.xml}} file:
{code:java}
true
config-type/sso.enabled.property
{code}
was:
Update service metainfo to declare SSO integration support. The following tag
may be optionally set in a service's \{{metainfo.xml}} file:
{code}
true
config-type/sso.enabled.property
{code}
> Update service metainfo to declare SSO integration support
> --
>
> Key: AMBARI-23252
> URL: https://issues.apache.org/jira/browse/AMBARI-23252
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available, sso
> Fix For: 2.7.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Update service metainfo to declare SSO integration support. The following tag
> may be optionally set in a service's {{metainfo.xml}} file:
> {code:java}
>
> true
> config-type/sso.enabled.property
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24895) Infra Manager: code clean up
Krisztian Kasa created AMBARI-24895: --- Summary: Infra Manager: code clean up Key: AMBARI-24895 URL: https://issues.apache.org/jira/browse/AMBARI-24895 Project: Ambari Issue Type: Task Components: ambari-infra Affects Versions: 2.8.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.8.0 * rename LOG -> logger * remove slf4j use log4j2 * merge Job Properties and Job Parameter classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24888) Fix SingleHostTopologyUpdater
[
https://issues.apache.org/jira/browse/AMBARI-24888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686397#comment-16686397
]
Hudson commented on AMBARI-24888:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10288 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10288/])
AMBARI-24888 fix SingleHostTopologyUpdater (benyoka) (#2603) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6395167a5a74d44b9d86dabeb2c0860df450ec67])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
> 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
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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] [Resolved] (AMBARI-24888) Fix SingleHostTopologyUpdater
[
https://issues.apache.org/jira/browse/AMBARI-24888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári resolved AMBARI-24888.
Resolution: Fixed
> 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
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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-24878) Infra Manager: kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686322#comment-16686322 ] ASF GitHub Bot commented on AMBARI-24878: - asfgit commented on issue #14: AMBARI-24878 - Infra Manager: kerberos support URL: https://github.com/apache/ambari-infra/pull/14#issuecomment-438614068 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/21/ 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 > Infra Manager: kerberos support > --- > > Key: AMBARI-24878 > URL: https://issues.apache.org/jira/browse/AMBARI-24878 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24878) Infra Manager: kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686321#comment-16686321 ] ASF GitHub Bot commented on AMBARI-24878: - kasakrisz opened a new pull request #14: AMBARI-24878 - Infra Manager: kerberos support URL: https://github.com/apache/ambari-infra/pull/14 ## What changes were proposed in this pull request? Infra Manager was not able to export documents from solr and save them to hdfs in a kerberized cluster ## How was this patch tested? ITs passed Manually: 1. Deploy Ambari and a cluster: zookeeper, infra-solr, logsearch, hdfs, infra-manager 2. Kerberize the cluster 3. Enable archiving for service_logs and set the destination to hdfs on Ambari UI, Infra Manager config 4. Run archiving of service_logs using infra managers rest api 5. check hdfs for archived service logs 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 > Infra Manager: kerberos support > --- > > Key: AMBARI-24878 > URL: https://issues.apache.org/jira/browse/AMBARI-24878 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24878) Infra Manager: kerberos support
[ https://issues.apache.org/jira/browse/AMBARI-24878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24878: Labels: pull-request-available (was: ) > Infra Manager: kerberos support > --- > > Key: AMBARI-24878 > URL: https://issues.apache.org/jira/browse/AMBARI-24878 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24894) Sensitive service configuration values should be decrypted when processing the Ambari agent command script, if enabled
Attila Magyar created AMBARI-24894:
--
Summary: Sensitive service configuration values should be
decrypted when processing the Ambari agent command script, if enabled
Key: AMBARI-24894
URL: https://issues.apache.org/jira/browse/AMBARI-24894
Project: Ambari
Issue Type: Task
Components: ambari-agent, ambari-server
Reporter: Attila Magyar
Assignee: Attila Magyar
Fix For: 2.8.0
Sensitive service configuration values should be decrypted when processing the
Ambari agent command script, if enabled.
During the processing of
resource_management.libraries.script.script.Script#execute, the command data
file is to be read in and the encrypted values in the JSON document are to be
decrypted before executing the command.
Each encrypted value will be in the form of
${enc=, value=}
For example:
${enc=aes265_hex, value=5248...303d}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
