Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Recently, while I worked on KMS-o-meter tool, a workload replay tool for KMS, I added opentracing in it and in KMS server/client.(courtesy of Elek, Marton's tracing work in ozone, I simply took a part of it). The ability to understand system performance in such details is unprecedented. We were able to fix a system scalability bug, verify it in record time.
File this jira to contribute the opentracing code in KMS server/client back to the community.