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

Hudson commented on HBASE-23588:
--------------------------------

Results for branch master
        [build #1590 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1590/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1590//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1590//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1590//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Cache index blocks and bloom blocks on write if CacheCompactedBlocksOnWrite 
> is enabled
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-23588
>                 URL: https://issues.apache.org/jira/browse/HBASE-23588
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: HBASE-23588.master.addendum000.patch
>
>
> The existing behaviour even even cacheOnWrite is enabled is that we don cache 
> the index or bloom blocks. Now with HBASE-23066 in place we also write blocks 
> on compaction. So it may be better to cache the index/bloom blocks also if 
> cacheOnWrite is enabled?
> FYI [~javaman_chen]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to