[jira] [Updated] (AMBARI-25930) Fix for test_hbase_master.py failure for Python 3
[ https://issues.apache.org/jira/browse/AMBARI-25930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Maurya updated AMBARI-25930: - Status: Patch Available (was: Open) > Fix for test_hbase_master.py failure for Python 3 > - > > Key: AMBARI-25930 > URL: https://issues.apache.org/jira/browse/AMBARI-25930 > Project: Ambari > Issue Type: Bug >Reporter: Himanshu Maurya >Assignee: Himanshu Maurya >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In the patch for upgrade to python3 AMBARI-25854, mode correction is missed > in hbase_master.py file, due to which all python test cases inside > test_hbase_master are getting failed. -- 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] [Assigned] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] D M Murali Krishna Reddy reassigned AMBARI-25956: - Assignee: D M Murali Krishna Reddy > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- 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-25959) Ambari Metrics Grafana rpm missing some grafana tarball files
[ https://issues.apache.org/jira/browse/AMBARI-25959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25959: Labels: pull-request-available (was: ) > Ambari Metrics Grafana rpm missing some grafana tarball files > - > > Key: AMBARI-25959 > URL: https://issues.apache.org/jira/browse/AMBARI-25959 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > grafana-9.3.2.linux-amd64.tar.gz is extracted in folder > ambari-metrics-grafana/target/grafana/grafana-9.3.2 then all files inside > grafana-9.3.2 are used while building the rpm. But while extracting > grafana-9.3.2.linux-amd64.tar.gz some files are getting extracted in inside > ambari-metrics-grafana/target/grafana which then are not part of the rpm > > Grafana tarball extraction script to be changed so all files are placed > inside correct folder. > -- 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] [Created] (AMBARI-25959) Ambari Metrics Grafana rpm missing some grafana tarball files
Mohammad Arshad created AMBARI-25959: Summary: Ambari Metrics Grafana rpm missing some grafana tarball files Key: AMBARI-25959 URL: https://issues.apache.org/jira/browse/AMBARI-25959 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad grafana-9.3.2.linux-amd64.tar.gz is extracted in folder ambari-metrics-grafana/target/grafana/grafana-9.3.2 then all files inside grafana-9.3.2 are used while building the rpm. But while extracting grafana-9.3.2.linux-amd64.tar.gz some files are getting extracted in inside ambari-metrics-grafana/target/grafana which then are not part of the rpm Grafana tarball extraction script to be changed so all files are placed inside correct folder. -- 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-25958) Ambari metrics returns Infinity when rate transformation is used
[
https://issues.apache.org/jira/browse/AMBARI-25958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25958:
Labels: pull-request-available (was: )
> Ambari metrics returns Infinity when rate transformation is used
>
>
> Key: AMBARI-25958
> URL: https://issues.apache.org/jira/browse/AMBARI-25958
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
>
> rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give
> value as Infinity. This is incorrect.
> For example invoking below URL returned Infinity along with other values
> http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate&precision=seconds&grouped=true&startTime=1686815115333&appId=hbase&endTime=1686815945333
>
> Output:
> {noformat}
> 1686796983505:679
> 1686797040051: 0.8214285714285714
> 1686797040144:"Infinity"
> 1686797042427:55
> 1686797043504:2027
> 1686797100144:"Infinity"
> 1686797102426:55{noformat}
--
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] [Commented] (AMBARI-25958) Ambari metrics returns Infinity when rate transformation is used
[
https://issues.apache.org/jira/browse/AMBARI-25958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735323#comment-17735323
]
Mohammad Arshad commented on AMBARI-25958:
--
When time interval is less than 1000 ms following code in class
org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService is causing
division by 0
{code:java}
Double rate = isDiff ? diff : (diff / TimeUnit.MILLISECONDS.toSeconds(step));
timeValueEntry.setValue(rate);
{code}
When step is less than 1000, TimeUnit.MILLISECONDS.toSeconds(step)) returns 0,
resulting in devision by 0 which give value Infinity
> Ambari metrics returns Infinity when rate transformation is used
>
>
> Key: AMBARI-25958
> URL: https://issues.apache.org/jira/browse/AMBARI-25958
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give
> value as Infinity. This is incorrect.
> For example invoking below URL returned Infinity along with other values
> http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate&precision=seconds&grouped=true&startTime=1686815115333&appId=hbase&endTime=1686815945333
>
> Output:
> {noformat}
> 1686796983505:679
> 1686797040051: 0.8214285714285714
> 1686797040144:"Infinity"
> 1686797042427:55
> 1686797043504:2027
> 1686797100144:"Infinity"
> 1686797102426:55{noformat}
--
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] [Created] (AMBARI-25958) Ambari metrics returns Infinity when rate transformation is used
Mohammad Arshad created AMBARI-25958:
Summary: Ambari metrics returns Infinity when rate transformation
is used
Key: AMBARI-25958
URL: https://issues.apache.org/jira/browse/AMBARI-25958
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give
value as Infinity. This is incorrect.
For example invoking below URL returned Infinity along with other values
http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate&precision=seconds&grouped=true&startTime=1686815115333&appId=hbase&endTime=1686815945333
Output:
{noformat}
1686796983505:679
1686797040051: 0.8214285714285714
1686797040144:"Infinity"
1686797042427:55
1686797043504:2027
1686797100144:"Infinity"
1686797102426:55{noformat}
--
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] [Commented] (AMBARI-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735282#comment-17735282
]
Mohammad Arshad commented on AMBARI-25945:
--
Added hbase.rpc.rows.warning.threshold in section Advanced ams-hbase-site with
default value as 1
!image-2023-06-20-18-36-37-450.png!
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: image-2023-06-20-18-36-37-450.png
>
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25945:
-
Attachment: image-2023-06-20-18-36-37-450.png
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: image-2023-06-20-18-36-37-450.png
>
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25945:
-
Description:
In metrics collector phoenix batch size is 1, but in ams hbase batch size
is 5000. Because of this following warning message is constantly getting logged
{noformat}
2023-05-19 05:49:04,899 WARN
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first region in
multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
2023-05-19 05:50:05,136 WARN
[RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first region in
multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
{noformat}
To fix this problem, either we should decrease phoenix batch size in collector
or increase batch size in ams hbase.
I propose to increase the batch size in ams hbase
was:
In metrics collector phoenix batch size is 1, but in ams hbase batch size
is 5000. Because of this following warning message is constantly getting logged
{noformat}
2023-05-19 05:49:04,899 WARN
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first region in
multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
2023-05-19 05:50:05,136 WARN
[RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first region in
multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
{noformat}
To fix this problem, either we should decrease phoenix batch size in collector
in increase batch size in ams hbase.
I propose to increase the batch size in ams hbase
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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] [Commented] (AMBARI-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735254#comment-17735254 ] Mohammad Arshad commented on AMBARI-25944: -- Thanks [~vjasani] for reviewing and merging the PR. > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Fix For: 2.8.0 > > Attachments: screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is updated. -- 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-25957) Ambari Metrics Grafana Datasource is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25957: Labels: pull-request-available (was: ) > Ambari Metrics Grafana Datasource is not working > > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- 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-25957) Ambari Metrics Grafana Datasource is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25957: - Summary: Ambari Metrics Grafana Datasource is not working (was: Ambari Metrics Grafana Datasource plugin is not working) > Ambari Metrics Grafana Datasource is not working > > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- 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] [Commented] (AMBARI-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735248#comment-17735248 ] Mohammad Arshad commented on AMBARI-25957: -- After fix, ambari metrics data source working fine. Fetched data from collector successfully. !image-2023-06-20-16-36-00-878.png! > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- 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-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25957: - Attachment: image-2023-06-20-16-36-00-878.png > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- 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-25941) Metrics Grafana Datasource plugin is not loading
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Summary: Metrics Grafana Datasource plugin is not loading (was: Ambari grafana ams-hbase-home dashboard values are wrong) > Metrics Grafana Datasource plugin is not loading > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.png! -- 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-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Attachment: image-2023-06-20-13-33-14-546.png > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.png! -- 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] [Commented] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735173#comment-17735173 ] Mohammad Arshad commented on AMBARI-25941: -- After fix, following configuration gets added by default and ambari metrics data source plugin is loaded successfully !image-2023-06-20-13-33-14-546.png! > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.png! -- 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] [Commented] (AMBARI-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735161#comment-17735161 ] Mohammad Arshad commented on AMBARI-25957: -- Seems AMBARI-20391 fixed this issue in branch-2. We should take that change in metrics master branch as well. > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- 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
