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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/05/12 05:41:15 UTC

[jira] [Resolved] (HBASE-6434) Document effect of slow compressors on the flush path and workaround in the online book

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

Andrew Purtell resolved HBASE-6434.
-----------------------------------

    Resolution: Not a Problem

> Document effect of slow compressors on the flush path and workaround in the online book
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-6434
>                 URL: https://issues.apache.org/jira/browse/HBASE-6434
>             Project: HBase
>          Issue Type: Task
>            Reporter: Andrew Purtell
>            Priority: Minor
>
> In HBASE-6423 Karthik writes
> bq. 1. flushing a memstore takes a while (GZIP compression)
> [... and the memstore gate comes crashing down]
> We once sidestepped this issue by specifying different compression options for flushes (LZO or none) and major compaction (BZIP2), disabling automatic major compaction, and managing major compaction from a shell based process that iterates over each region on disk and makes some application specific decisions.
> I go back and forth on whether this is a hack or legitimate HBase ops given how things currently work.



--
This message was sent by Atlassian JIRA
(v6.2#6252)