[ https://issues.apache.org/jira/browse/KUDU-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-3020: -------------------------------- Summary: Add metric gauges for the size of incoming RPC request payload and number of RPC rejections due to payload size (was: Add metric gauge for size of incoming RPC request payload and number RPC rejections due to payload size) > Add metric gauges for the size of incoming RPC request payload and number of > RPC rejections due to payload size > --------------------------------------------------------------------------------------------------------------- > > Key: KUDU-3020 > URL: https://issues.apache.org/jira/browse/KUDU-3020 > Project: Kudu > Issue Type: Improvement > Components: master, tserver > Reporter: Alexey Serbin > Priority: Major > Labels: guidelines, observability, scalability, troubleshooting > > Kudu servers have a limit on the size of RPC's payload they accept: > {{\-\-rpc_max_message_size}}. > It would be nice to introduce corresponding metrics to gauge how relevant the > current setting for the maximum RPC size is with regard to the incoming > requests. That can help with a pro-active tuning of a Kudu cluster to > sustain planned increase in workload. This is especially useful for tuning > parameters of Kudu masters to accommodate higher number of tables/tablets in > a cluster (e.g., adding new tables or creating new partitions for already > existing tables). -- This message was sent by Atlassian Jira (v8.3.4#803005)