hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18002) Investigate why bucket cache filling up in file mode in an exisitng file is slower
Date Mon, 08 May 2017 08:07:04 GMT

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

ramkrishna.s.vasudevan commented on HBASE-18002:
------------------------------------------------

Good point.
But with latest SSDs this will still happen but may be at lesser error rate and we may have
no way to improve this.
bq.(Clear file data from code I mean)
YEs then this seems the best soln. Like if there is a valid path configured and if the file
len is not equal to 0 then better delete it from code and recreate it. Any failure here handlie
it as failure in bucket cache init only.


> 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
>             Fix For: 2.0.0
>
>
> 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.3.15#6346)

Mime
View raw message