hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16156) In write heavy scenario creating in memory flushes leads to contention
Date Fri, 01 Jul 2016 06:43:10 GMT

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

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

{code}
getRegionServices().blockUpdates();
    try {
      MutableSegment active = getActive();
      LOG.info("IN-MEMORY FLUSH: Pushing active segment into compaction pipeline, "
            + "and initiating compaction.");
      pushActiveToPipeline(active);
    } finally {
      getRegionServices().unblockUpdates();
    }
{code}
It was this way.  So under the lock we do log also !!!!   Now I changed level to debug so
that u will see better.   Even we need change that also. After the lock is released we can
debug log that the active is pushed.

> In write heavy scenario creating in memory flushes leads to contention
> ----------------------------------------------------------------------
>
>                 Key: HBASE-16156
>                 URL: https://issues.apache.org/jira/browse/HBASE-16156
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0
>
>
> In write heavy cases, the inmemory flushes blocks the write because it takes a update
lock. Dumps show that it is causing heavy contention and leads to memstore filling up and
so intern blocks the flush from happening sooner. This JIRA is to discuss optimal settings
and then make suitable changes.



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

Mime
View raw message