[
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 10000, 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: 10000 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 10000, 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: 10000 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 10000, 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: 10000 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
