[
https://issues.apache.org/jira/browse/HBASE-18002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074231#comment-16074231
]
ramkrishna.s.vasudevan commented on HBASE-18002:
------------------------------------------------
I agree the patch as such is not right because I am not checking for the
persistencepath.
bq.I think for actual persistance to happen we need to configure
'BUCKET_CACHE_PERSISTENT_PATH_KEY' this also right? If we don't do that then
the meta data of the persistance is not available so nothing will be retrieved
back?
If you do not have this config then you can delete the file on restart with no
issues.
> Investigate why bucket cache filling up in file mode in an exisitng file is
> slower
> -----------------------------------------------------------------------------------
>
> Key: HBASE-18002
> URL: https://issues.apache.org/jira/browse/HBASE-18002
> Project: HBase
> Issue Type: Sub-task
> Components: BucketCache
> Affects Versions: 2.0.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-18002.patch
>
>
> This issue was observed when we recently did some tests with SSD based bucket
> cache. Similar thing was also reported by @stack and [~danielpol] while doing
> some of these bucket cache related testing.
> When we try to preload a bucket cache (in file mode) with a new file the
> bucket cache fills up quite faster and there not much 'failedBlockAdditions'.
> But when the same bucket cache is filled up with a preexisitng file ( that
> had already some entries filled up) this time it has more
> 'failedBlockAdditions' and the cache does not fill up faster. Investigate why
> this happens.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
