cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Knighton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11402) Alignment wrong in tpstats output for PerDiskMemtableFlushWriter
Date Mon, 25 Apr 2016 21:34:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257093#comment-15257093
] 

Joel Knighton commented on CASSANDRA-11402:
-------------------------------------------

That looks like the right approach - as I mentioned in the comment above, it would be great
if we also fixed the output in org.apache.cassandra.utils.StatusLogger.

That said, since he is Assignee, let me check with [~RyanMagnusson] - do you have a problem
with [~nkelkar] taking over this ticket or would you prefer to revise your patch based on
my comment above?

> Alignment wrong in tpstats output for PerDiskMemtableFlushWriter
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-11402
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11402
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joel Knighton
>            Assignee: Ryan Magnusson
>            Priority: Trivial
>              Labels: lhf
>             Fix For: 3.x
>
>         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
(v6.3.4#6332)

Mime
View raw message