You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/07/04 05:39:11 UTC

[jira] [Resolved] (HBASE-16156) In write heavy scenario creating in memory flushes leads to contention

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

Anoop Sam John resolved HBASE-16156.
------------------------------------
    Resolution: Duplicate
      Assignee:     (was: ramkrishna.s.vasudevan)

Cause is same as that of HBASE-16162.  Closing as dup.

> 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
>             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)