[
https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007649#comment-16007649
]
ramkrishna.s.vasudevan commented on HBASE-17738:
------------------------------------------------
bq.When unsafe is not available we should have a way to do the things.
What do you mean here? Sorry not getting this. When unsafe is not available
then even the constructor in DBB will not work which acutally does this job of
memory allocation?
Even now in the patch when we see that Unsafe is not available we just try to
call BB.allocateDirect(). So we have that protection now.
If you meant something else, I can check it.
> BucketCache startup is slow
> ---------------------------
>
> Key: HBASE-17738
> URL: https://issues.apache.org/jira/browse/HBASE-17738
> Project: HBase
> Issue Type: Sub-task
> Components: BucketCache
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch,
> HBASE-17738_3.patch, HBASE-17738.patch
>
>
> If you set bucketcache size at 64G say and then start hbase, it takes a long
> time. Can we do the allocations in parallel and not inline with the server
> startup?
> Related, prefetching on a bucketcache is slow. Speed it up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
