[jira] [Updated] (AMBARI-25457) Hive 3 Grafana dashboards showing outdated metrics

2022-11-07 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu updated AMBARI-25457:
---
Fix Version/s: 2.8.0

> Hive 3 Grafana dashboards showing outdated metrics 
> ---
>
> Key: AMBARI-25457
> URL: https://issues.apache.org/jira/browse/AMBARI-25457
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.7.3, 2.7.4, 2.7.5
>Reporter: Tamas Payer
>Assignee: Tamas Payer
>Priority: Major
>  Labels: grafana, hive, metrics, pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some of the metrics' name has been changed in Hive 3. Due to this change many 
> graphs shows no data on Hive Home, HiveServer2 and HiveMetastore dashboards.
> Suggested changes: 
> +HiveSever2+
> The _default.General.api_get_all_databases_ and 
> _default.General.api_get_partitions_by_names_ metrics are not provided by 
> HiveServer2 anymore - only by HiveMetastore - so the "API Times" row with the 
> two charts has been removed.
> +Hive Metastore+
> |*Original Name*| *New Name*|
> |default.General.api_get_all_databases_75thpercentile|default.General.api_get_databases_75thpercentile|
> |default.General.api_get_all_databases_999thpercentile|default.General.api_get_databases_999thpercentile|
> |default.General.memory.heap.max|default.General.heap.max|
> |default.General.memory.heap.used|default.General.heap.used|
> |default.General.memory.heap.committed|default.General.heap.committed|
> |default.General.memory.non-heap.max|default.General.non-heap.max|
> |default.General.memory.non-heap.used|default.General.non-heap.used|
> |default.General.memory.non-heap.committed|default.General.non-heap.committed|
>  
> +Hive Home+
>  
> | *Original Name*| *New Name*|
> |default.General.init_total_count_db|default.General.total_count_dbs|
> |default.General.init_total_count_tables|default.General.total_count_tables|
> |default.General.init_total_count_partitions|default.General.total_count_partitions|
> |default.General.api_create_table_count|api_create_table_req_count|
> |default.General.memory.heap.max|default.General.heap.max|
> |default.General.memory.heap.used|default.General.heap.used|
> |default.General.memory.heap.committed|default.General.heap.committed|
> |default.General.memory.non-heap.max|default.General.non-heap.max|



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Updated] (AMBARI-25405) Remove dependency on com.fasterxml.jackson.core:jackson-databind:2.9.6-2.9.9.1 in Ambari

2022-11-07 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu updated AMBARI-25405:
---
Fix Version/s: 2.8.0

> Remove dependency on 
> com.fasterxml.jackson.core:jackson-databind:2.9.6-2.9.9.1 in Ambari
> 
>
> Key: AMBARI-25405
> URL: https://issues.apache.org/jira/browse/AMBARI-25405
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: Gabor Boros
>Assignee: Éberhardt Péter
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.8.0, 2.7.5
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Updated] (AMBARI-25400) Issue while determining live collector in case of HA

2022-11-07 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu updated AMBARI-25400:
---
Fix Version/s: 2.8.0

> Issue while determining live collector in case of HA
> 
>
> Key: AMBARI-25400
> URL: https://issues.apache.org/jira/browse/AMBARI-25400
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.6.2, 2.7.4
>Reporter: amarnath reddy pappu
>Assignee: Éberhardt Péter
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0, 2.7.5
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> If collector throws 
> http://collectorhost:port/{color:#032f62}/ws/v1/timeline/metrics/livenodes{color}
>  500 error then sink is unable to determine live/healthy collector.
>  
> sink will try to connect to another collector only if it is not 
> reachable/IOException to first collector.  if any other response code other 
> than 200 then still it should consider as 1st Collector not reachable.
>  
> [https://github.com/apache/ambari/blob/release-2.7.4/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java#L629]
>  
>  Possible fix
>  
> {code:java}
>   if (responseCode == 200) {
> try (InputStream in = connection.getInputStream()) {
>   StringWriter writer = new StringWriter();
>   IOUtils.copy(in, writer);
>   try {
> collectors = gson.fromJson(writer.toString(), new 
> TypeToken>(){}.getType());
>   } catch (JsonSyntaxException jse) {
> // Swallow this at the behest of still trying to POST
> LOG.debug("Exception deserializing the json data on live " +
>   "collector nodes.", jse);
>   }
> }
>   } else if (responseCode == 500){
> String warnMsg = "Unable to connect to collector to find live nodes, 
> Internal server error";
> throw new MetricCollectorUnavailableException(warnMsg);
>   }
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org