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

stack commented on HBASE-12116:
-------------------------------

[~apurtell] Chatting w/ Esteban, its an audit CP that is run in CDH.  Yeah on 
CSLM worth digging in on -- big payback especially if can save a f few compares 
(in // with work to compress CSLM snapshots). On CRC, have work to do in HDFS 
if we want to continue doing our own CRC on read path so can read blocks that 
have been natively CRC'd and decompressed all offheap. On write path ditto 
(more awkward here even given no BB interface at write time). A hbase native 
lib to do native CRC and compression so not tied to a particular HDFS version 
would be crazy?, Or have HDFS do the checksum for us again (CPU for an extra 
seek -- ok if SSD).



> Hot contention spots; writing
> -----------------------------
>
>                 Key: HBASE-12116
>                 URL: https://issues.apache.org/jira/browse/HBASE-12116
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: 12116.checkForReplicas.txt, 
> 12116.stringify.and.cache.scanner.maxsize.txt, 12116.txt, Screen Shot 
> 2014-09-29 at 5.12.51 PM.png, Screen Shot 2014-09-30 at 10.39.34 PM.png, 
> Screen Shot 2015-04-13 at 2.03.05 PM.png, perf.write3.svg, perf.write4.svg
>
>
> Playing with flight recorder, here are some write-time contentious 
> synchronizations/locks (picture coming)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to