[
https://issues.apache.org/jira/browse/CASSANDRA-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182161#comment-17182161
]
Stefan Miklosovic commented on CASSANDRA-11402:
-----------------------------------------------
Indeed, the most proper test would consist of starting a node via dtest api and
invoking nodetool tpstats dumping that yaml, parsing the output of that command
and feeding it back to yaml to close that loop.
The required bits to do this (nodetool output against a node) is introduced in
CASSANDRA-15406 which is under review of [~dcapwell] so as soon as that one is
merged, I ll finish this one.
> Alignment wrong in tpstats output for PerDiskMemtableFlushWriter and format
> to YAML is broken
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11402
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11402
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joel Knighton
> Assignee: Stefan Miklosovic
> Priority: Low
> Labels: lhf
> Fix For: 4.0-beta2
>
> Attachments: 11402-3_5_patch1.patch, 11402-trunk.txt
>
>
> With the accompanying designation of which memtableflushwriter it is, this
> threadpool name is too long for the hardcoded padding in tpstats output.
> We should dynamically calculate padding so that we don't need to check this
> every time we add a threadpool.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
