[
https://issues.apache.org/jira/browse/KUDU-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240349#comment-15240349
]
Todd Lipcon commented on KUDU-1410:
-----------------------------------
I put some work-in-progress code on my github at
https://github.com/toddlipcon/kudu/tree/kudu-1410 and testing it on a local
workload. Will work on cleaning this up into some nicer patches, and improving
a bit, over the next couple days.
[~bruceSz] if you are interested in trying it out, you could build from this
branch and visit /rpcz on the tablet server during a workload to see some
example collected traces.
> Improve diagnosability of performance problems
> ----------------------------------------------
>
> Key: KUDU-1410
> URL: https://issues.apache.org/jira/browse/KUDU-1410
> Project: Kudu
> Issue Type: Bug
> Components: supportability
> Affects Versions: 0.8.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> Although Kudu has been relatively stable for most users, we are starting to
> see more and more questions about performance. In internal test clusters
> we're also struggling to understand performance issues or timeouts in some
> cases from logs only, and it can require gathering a daemon trace to see
> what's going on.
> This is an umbrella ticket for various improvements we can make so that
> performance is easier to understand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
