[
https://issues.apache.org/jira/browse/HBASE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-20894:
------------------------------
Release Note: For users who have configured hbase.bucketcache.ioengine with
either the file:, files:, or mmap: prefix, and configured it to be persistent
via the hbase.bucketcache.persistent.path property, the serialization format of
the bucket cache has changed between versions. The old state will not be read
during startup, and there is currently no migration path. The impact is
expected to be minimal, however, since the cache will rebuild over time as
access patterns dictate. (was: For users who have configured
hbase.bucketcache.ioengine with either the file: or files: prefix, the
serialization format of the bucket cache has changed between versions. The old
state will not be read during startup, and there is currently no migration
path. The impact is expected to be minimal, however, since the cache will
rebuild over time as access patterns dictate.)
> Move BucketCache from java serialization to protobuf
> ----------------------------------------------------
>
> Key: HBASE-20894
> URL: https://issues.apache.org/jira/browse/HBASE-20894
> Project: HBase
> Issue Type: Task
> Components: BucketCache
> Affects Versions: 2.0.0
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-Write-the-CacheableDeserializerIdManager-index-into-.patch,
> HBASE-20894.WIP-2.patch, HBASE-20894.WIP.patch, HBASE-20894.master.001.patch,
> HBASE-20894.master.002.patch, HBASE-20894.master.003.patch,
> HBASE-20894.master.004.patch, HBASE-20894.master.005.patch,
> HBASE-20894.master.006.patch
>
>
> We should use a better serialization format instead of Java Serialization for
> the BucketCache entry persistence.
> Suggested by Chris McCown, who does not appear to have a JIRA account.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
