[ 
https://issues.apache.org/jira/browse/CASSANDRA-12776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kurt Greaves updated CASSANDRA-12776:
-------------------------------------
    Attachment: 12776.patch

Looks like this was just a typo in the patch for #9681. It only affects the 
debug log message so only a minor issue. Attached a patch (against 3.0) with 
the suggested change. [~benedict] seeing as you made the change can you 
confirm/deny? Thanks.

> when memtable flush Statistics thisOffHeap error
> ------------------------------------------------
>
>                 Key: CASSANDRA-12776
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12776
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: 翟玉勇
>            Priority: Trivial
>              Labels: lhf
>         Attachments: 12776.patch
>
>
> {code}
> if (largest != null)
>             {
>                 float usedOnHeap = Memtable.MEMORY_POOL.onHeap.usedRatio();
>                 float usedOffHeap = Memtable.MEMORY_POOL.offHeap.usedRatio();
>                 float flushingOnHeap = 
> Memtable.MEMORY_POOL.onHeap.reclaimingRatio();
>                 float flushingOffHeap = 
> Memtable.MEMORY_POOL.offHeap.reclaimingRatio();
>                 float thisOnHeap = 
> largest.getAllocator().onHeap().ownershipRatio();
>                 float thisOffHeap = 
> largest.getAllocator().onHeap().ownershipRatio();
>                 logger.info("Flushing largest {} to free up room. Used total: 
> {}, live: {}, flushing: {}, this: {}",
>                             largest.cfs, ratio(usedOnHeap, usedOffHeap), 
> ratio(liveOnHeap, liveOffHeap),
>                             ratio(flushingOnHeap, flushingOffHeap), 
> ratio(thisOnHeap, thisOffHeap));
>                 largest.cfs.switchMemtableIfCurrent(largest);
>             }
> {code}
> Should:
> {code}
> float thisOffHeap = largest.getAllocator().onHeap().ownershipRatio();
> {code}
> Be:
> {{offHeap().ownershipRatio();}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to