[ https://issues.apache.org/jira/browse/KUDU-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-3148: ------------------------------ Labels: roadmap-candidate supportability (was: supportability) > Add Java client metrics > ----------------------- > > Key: KUDU-3148 > URL: https://issues.apache.org/jira/browse/KUDU-3148 > Project: Kudu > Issue Type: Improvement > Components: client > Affects Versions: 1.12.0 > Reporter: Grant Henke > Assignee: Grant Henke > Priority: Major > Labels: roadmap-candidate, supportability > > This Jira is to track adding complete metrics to the Java client. There are > many cases where applications using the client have issues that are difficult > to debug. The primary reason is that it's hard to reason about what the > application is doing with the Kudu client without inspecting the code, and > even then it can be easy to miss an issue in the code as well. > For example we have seen many cases where an application creates a Kudu > client, sends a few messages, and then closes the client in a loop. Creating > many clients over an over not only impacts performance/stability of the > application but can also put unwelcome load on the servers. If we had request > metrics with a client id tag periodically logged, then it would be easy to > grep the application logs for unique client ids and spot the issue and the > offending application. -- This message was sent by Atlassian Jira (v8.3.4#803005)