You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2014/12/19 21:08:17 UTC
[jira] [Comment Edited] (HBASE-5699) Run with > 1 WAL in
HRegionServer
[ https://issues.apache.org/jira/browse/HBASE-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253936#comment-14253936 ]
Sean Busbey edited comment on HBASE-5699 at 12/19/14 8:07 PM:
--------------------------------------------------------------
{quote}
bq. Altering the WAL provider used by a particular RegionServer requires restarting that instance.
It requires restarting the cluster, right? Otherwise when an RS dies there might another up still with a different wal provider.
{quote}
In general, yes. In the case of the providers we currently allow via configuration parameters (as opposed to user-provided custom FQCN), they all are compatible on the recovery side. So it doesn't matter if a RS dies while there are different providers around. That's why a rolling restart can be used to change from default to multiwal.
In the release note I was focused on the specific case of default vs multiwal. Should I note the general case?
was (Author: busbey):
{quote}
bq. Altering the WAL provider used by a particular RegionServer requires restarting that instance.
It requires restarting the cluster, right? Otherwise when an RS dies there might another up still with a different wal provider.
{quote}
In general, yes. In the case of the providers we currently allow via configuration parameters (as opposed to user customer FQCN), they all are compatible on the recovery side. So it doesn't matter if a RS dies while there are different providers around. That's why a rolling restart can be used to change from default to multiwal.
In the release note I was focused on the specific case of default vs multiwal. Should I note the general case?
> Run with > 1 WAL in HRegionServer
> ---------------------------------
>
> Key: HBASE-5699
> URL: https://issues.apache.org/jira/browse/HBASE-5699
> Project: HBase
> Issue Type: Improvement
> Components: Performance, wal
> Reporter: binlijin
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 2.0.0, 1.1.0
>
> Attachments: HBASE-5699.3.patch.txt, HBASE-5699.4.patch.txt, HBASE-5699_#workers_vs_MiB_per_s_1x1col_512Bval_wal_count_1,2,4.tiff, HBASE-5699_disabled_and_regular_#workers_vs_MiB_per_s_1x1col_512Bval_wal_count_1,2,4.tiff, HBASE-5699_write_iops_multiwal-1_1_to_200_threads.tiff, HBASE-5699_write_iops_multiwal-2_10,50,120,190,260,330,400_threads.tiff, HBASE-5699_write_iops_multiwal-4_10,50,120,190,260,330,400_threads.tiff, HBASE-5699_write_iops_multiwal-6_10,50,120,190,260,330,400_threads.tiff, HBASE-5699_write_iops_upstream_1_to_200_threads.tiff, PerfHbase.txt, hbase-5699_multiwal_400-threads_stats_sync_heavy.txt, hbase-5699_total_throughput_sync_heavy.txt, results-hbase5699-upstream.txt.bz2, results-hbase5699-wals-1.txt.bz2, results-updated-hbase5699-wals-2.txt.bz2, results-updated-hbase5699-wals-4.txt.bz2, results-updated-hbase5699-wals-6.txt.bz2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)