[
https://issues.apache.org/jira/browse/HBASE-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-19389:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 2.0.0)
2.1.0
3.0.0
Release Note: After HBASE-19389 we introduced a RegionServer
self-protection mechanism to prevent write handler getting exhausted by high
concurrency put with dense columns, mainly through two new properties:
hbase.region.store.parallel.put.limit.min.column.count to decide what kind of
put (with how many columns within a single column family) to limit (100 by
default) and hbase.region.store.parallel.put.limit to limit the concurrency (10
by default). There's another property for advanced user and please check source
and javadoc of StoreHotnessProtector for more details.
Status: Resolved (was: Patch Available)
Add release note and close issue. Thanks for the great job [~chancelq]
Setting fix version to 2.1.0/3.0.0 and please let us know if you'd like to
include it in 2.0.0/1.4 bosses [~stack] [~apurtell]. Thanks.
> Limit concurrency of put with dense (hundreds) columns to prevent write
> handler exhausted
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-19389
> URL: https://issues.apache.org/jira/browse/HBASE-19389
> Project: HBase
> Issue Type: Improvement
> Components: Performance
> Affects Versions: 2.0.0
> Environment: 2000+ Region Servers
> PCI-E ssd
> Reporter: Chance Li
> Assignee: Chance Li
> Priority: Critical
> Fix For: 3.0.0, 2.1.0
>
> Attachments: CSLM-concurrent-write.png,
> HBASE-19389-branch-2-V10.patch, HBASE-19389-branch-2-V2.patch,
> HBASE-19389-branch-2-V3.patch, HBASE-19389-branch-2-V4.patch,
> HBASE-19389-branch-2-V5.patch, HBASE-19389-branch-2-V6.patch,
> HBASE-19389-branch-2-V7.patch, HBASE-19389-branch-2-V8.patch,
> HBASE-19389-branch-2-V9.patch, HBASE-19389-branch-2.patch,
> HBASE-19389.master.patch, HBASE-19389.master.v2.patch, metrics-1.png,
> ycsb-result.png
>
>
> In a large cluster, with a large number of clients, we found the RS's
> handlers are all busy sometimes. And after investigation we found the root
> cause is about CSLM, such as compare function heavy load. We reviewed the
> related WALs, and found that there were many columns (more than 1000 columns)
> were writing at that time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
