[
https://issues.apache.org/jira/browse/CASSANDRA-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-11402:
-----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0-beta3
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/2dbba13fdb555b3a297a7677896091cc880b5da5
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Fair enough, it can't get any more broken than it was. I think we could still
do an 'improper' test in a unit test, but we'll leave it for now.
> 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-beta3
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
