[
https://issues.apache.org/jira/browse/HBASE-12116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494454#comment-14494454
]
Andrew Purtell commented on HBASE-12116:
----------------------------------------
bq. Chatting w/ Esteban, its an audit CP that is run in CDH
Ah, well 2% for audit is still not bad.
bq. On write path ditto (more awkward here even given no BB interface at write
time).
Yep, but if raising the floor of supported Hadoop version on trunk, maybe we
could work up something together with HDFS for a 2.0 release timeframe.
bq. A hbase native lib to do native CRC and compression so not tied to a
particular HDFS version would be crazy?
Sure, if taking on checksumming at our layer instead of pushing off to HDFS is
something we still want to do. I think it still makes sense, we trade
complexity in our code for a big cut in IOPS needed for reading. Native bits in
HBase should be optional and have a Java only fallback, native code is a PITA
for deployment, even if compiled for the correct architecture we may fail to
dlopen if native symbol versioning gets in the way.
> 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)
