[
https://issues.apache.org/jira/browse/HBASE-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273004#comment-16273004
]
Chance Li commented on HBASE-19389:
-----------------------------------
bq. For metrics-1.png, was the stat collected with or without protection ?
Only with protection, sir. The three parts is about #SKIP_WAL, #ASYNC_WAL and
#SYNC_WAL. Without protection, all handlers were always busy.
bq. Does that mean the other half handlers were idle ?
yes sir. Maybe the reason is client do some sleep when it receive exception.
I'll check it.
But actually, we aim to ensure that the #handler avoiding to do slower
call(This actually reduces the performance of the server). All handlers are
busy is not a problem. The other calls come from other client for normal
region(store) will be have chance to be handled. In my test, there are no the
other calls .
Thanks, sir. [[email protected]]
> RS's handlers are all busy when writing many columns (more than 1000 columns)
> ------------------------------------------------------------------------------
>
> Key: HBASE-19389
> URL: https://issues.apache.org/jira/browse/HBASE-19389
> Project: HBase
> Issue Type: Improvement
> Components: hbase
> Affects Versions: 2.0.0
> Environment: 2000+ Region Servers
> PCI-E ssd
> Reporter: Chance Li
> Assignee: Chance Li
> Priority: Minor
> Fix For: 2.0.0, 3.0.0
>
> Attachments: CSLM-concurrent-write.png, 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
(v6.4.14#64029)
