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

Yu Li commented on HBASE-19389:
-------------------------------

Ah I see, you meant the {{hbase.region.store.parallel.put.print.threshold}} 
property which is for controlling the log frequency. Yes this is default by 50 
but not mentioned in the release note (in RN we only introduce 
{{hbase.region.store.parallel.put.limit}}).

And yes personally I think we could directly use  
{{hbase.region.store.parallel.put.limit}} as the print limit instead of 
introducing a new property, unless the new property supports online 
configuration change for more flexible debugging. [~stack]

> 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)

Reply via email to