[
https://issues.apache.org/jira/browse/HBASE-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382560#comment-16382560
]
stack commented on HBASE-19389:
-------------------------------
[~chancelq] Thanks for the quality work. The chart on how CSLM degrades when
concurrency goes up is interesting. Also of note is how your compares show the
asyncwal being slightly better than old wal.
As I read the ycsb diagrams, less throughput, but way less CPU used (better
95th percentiles, etc), and handlers free for other tasks. Am I reading it
right. Would it make sense to put this limit behind a configuration gate?
Thanks.
[~uagashe] An issue of yours is referenced above and you might be interested in
this one sir.
> 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: 2.0.0
>
> Attachments: CSLM-concurrent-write.png,
> 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.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)
