You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/12/29 02:53:58 UTC

[jira] [Commented] (HBASE-17383) Improve log msg when offheap memstore breaches higher water mark

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

Anoop Sam John commented on HBASE-17383:
----------------------------------------

Noticed this while doing patch for HBASE-17338..  Latest patch there having this fix already. Pls have a look..  I did not check the test failures.. Will do that soon.

> Improve log msg when offheap memstore breaches higher water mark
> ----------------------------------------------------------------
>
>                 Key: HBASE-17383
>                 URL: https://issues.apache.org/jira/browse/HBASE-17383
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> Currently we get this log
> {code}
> 2016-12-28 21:11:14,349 INFO  [RpcServer.deafult.FPBQ.Fifo.handler=39,queue=9,port=16041] regionserver.MemStoreFlusher: Blocking updates on stobdtserver5,16041,1482938527980: the global offheap memstore size 12.6 G + global memstore heap overhead 4.0 G is >= than blocking 12.6 G size
> {code}
> Here the global offheap memstore size is greater than the blocking size. The memstore heap overhead need not be included in this log unless the higher water mark breach is only due to the heap overhead.



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