[ 
https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Gray updated HBASE-3417:
---------------------------------

    Attachment: HBASE-3417-redux-v1.patch

Adds a new unit test in TestFromClientSide for testing cache on write and evict 
on close by looking inside the block cache.

This test fails on 92 and trunk without the rest of the changes in this patch 
(CacheOnWrite is currently completely broken with hfile v2).
                
> CacheOnWrite is using the temporary output path for block names, need to use 
> a more consistent block naming scheme
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3417
>                 URL: https://issues.apache.org/jira/browse/HBASE-3417
>             Project: HBase
>          Issue Type: Bug
>          Components: io, regionserver
>    Affects Versions: 0.92.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: HBASE-3417-redux-v1.patch, HBASE-3417-v1.patch, 
> HBASE-3417-v2.patch, HBASE-3417-v5.patch
>
>
> Currently the block names used in the block cache are built using the 
> filesystem path.  However, for cache on write, the path is a temporary output 
> file.
> The original COW patch actually made some modifications to block naming stuff 
> to make it more consistent but did not do enough.  Should add a separate 
> method somewhere for generating block names using some more easily mocked 
> scheme (rather than just raw path as we generate a random unique file name 
> twice, once for tmp and then again when moved into place).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to