[
https://issues.apache.org/jira/browse/HBASE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562573#comment-16562573
]
Mike Drob commented on HBASE-20894:
-----------------------------------
Thanks for the additional insight, [~stack]. Doing a further review of how we
use instances of {{CachableDeserializer}}, I'm even more baffled about what's
going on.
There is only one non-test usage of CachableDeserializer to be registered in
the IdManager, and it is a static instance that comes up in HFileBlock. So the
old code works because there's only one id ever registered? Serializing class
name isn't going to help us because it will be some garbage anonymous name.
I'll try pulling that out into a separate class and see if it helps.
> 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
>
>
> 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)
