hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14457) Umbrella: Improve Multiple WAL for production usage
Date Mon, 21 Sep 2015 18:39:04 GMT

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

Vladimir Rodionov commented on HBASE-14457:
-------------------------------------------

I am aware about this feature, but it does not help when periodic memstore flusher makes its
decision based on a global periodic flush interval (one for all tables/cf). It would be nice
to have different flush intervals for different types of column families but this will be
possible only when we will be able to assign different WALs to them. One of the major reason
for periodic memstore flush is to guarantee that we do not have runaway wal files.

> Umbrella: Improve Multiple WAL for production usage
> ---------------------------------------------------
>
>                 Key: HBASE-14457
>                 URL: https://issues.apache.org/jira/browse/HBASE-14457
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Yu Li
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.3.0
>
>
> HBASE-5699 proposed the idea to run with multiple WAL in regionserver and did a great
initial work there, but when trying to use it in our production cluster, we still found several
issues to resolve, like tracking multiple WAL paths in replication (HBASE-6617), fixing UT
with multiwal provider (HBASE-14411), introducing a namespace-based strategy for RegionGroupingProvider
(HBASE-14456), etc. This is an umbrella including(but not limited of) all these works and
efforts to make multiple wal ready for production usage and give user a clear picture about
it.
> Besides the developing works done, I'd also like to share some scenarios and testing/online
data in this JIRA about our usage/performance of multiple wal, to(hopefully) help people better
judge whether to enable multiple wal or not in their own cluster and what they might gain.



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

Mime
View raw message