[
https://issues.apache.org/jira/browse/HBASE-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297906#comment-16297906
]
stack commented on HBASE-19116:
-------------------------------
Just tried a branch-2 starting over data written by an 0.98. This is the
exception to fix:
{code}
382603 2017-12-19 21:25:08,333 DEBUG
[StoreOpener-8e6e2b71d8a413561d9103b0cb6e4686-1] regionserver.HStore: loaded
hdfs://ve0524.halxg.cloudera.com:8020/hbase/data/default/ycsb/8e6e2b71d8a413561d9103b0cb6e4686/family/3633fe2e03ad4cceb0d2018f1f0d76da,
isReference=false, isBulkLoadResult=false, seqid=341101 6,
majorCompaction=false
382604 2017-12-19 21:25:08,339 DEBUG [StoreFileOpenerThread-family-1]
hfile.HFile: Opening HFile v2 with v3 reader
382605 2017-12-19 21:25:08,342 ERROR [StoreFileOpenerThread-family-1]
regionserver.StoreFileReader: Error reading bloom filter meta for
GENERAL_BLOOM_META -- proceeding without
382606 java.io.IOException: java.lang.ClassNotFoundException:
org.apache.hadoop.hbase.KeyValue$RawBytesComparator
382607 at
org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.getComparatorClass(FixedFileTrailer.java:583)
382608 at
org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComparator(FixedFileTrailer.java:592)
382609 at
org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.<init>(CompoundBloomFilter.java:79)
382610 at
org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMeta(BloomFilterFactory.java:104)
382611 at
org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBloomfilter(StoreFileReader.java:480)
382612 at
org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreFile.java:426)
382613 at
org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(HStoreFile.java:461)
382614 at
org.apache.hadoop.hbase.regionserver.HStore.createStoreFileAndReader(HStore.java:665)
382615 at
org.apache.hadoop.hbase.regionserver.HStore.lambda$openStoreFiles$0(HStore.java:533)
382616 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
382617 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
382618 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
382619 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
382620 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
382621 at java.lang.Thread.run(Thread.java:745)
382622 Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.hbase.KeyValue$RawBytesComparator
382623 at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
382624 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
382625 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
382626 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
382627 at java.lang.Class.forName0(Native Method)
382628 at java.lang.Class.forName(Class.java:264)
382629 at
org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.getComparatorClass(FixedFileTrailer.java:581)
382630 ... 14 more
{code}
> Currently the tail of hfiles with CellComparator* classname makes it so
> hbase1 can't open hbase2 written hfiles; fix
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-19116
> URL: https://issues.apache.org/jira/browse/HBASE-19116
> Project: HBase
> Issue Type: Sub-task
> Components: HFile, migration
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0-beta-2
>
>
> See tail of HBASE-19052 for discussion which concludes we should try and make
> it so operators do not have to go to latest hbase version before they
> upgrade, at least if we can avoid it.
> The necessary change of our default comparator from KV to Cell naming has
> hfiles with tails that have the classname CellComparator in them in place of
> KeyValueComparator. If an hbase1 tries to open them, it will fail not having
> a CellComparator in its classpath (We have name of comparator in tail because
> different files require different comparators... perhaps we write an alias
> instead of a class one day... TODO). HBASE-16189 and HBASE-19052 are about
> trying to carry knowledge of hbase2 back to hbase1, a brittle approach making
> it so operators will have to upgrade to the latest branch-1 before they can
> go to hbase2.
> This issue is about undoing our writing of an incompatible (to hbase1) tail,
> not unless we really have to (and it sounds like we could do without writing
> an incompatible tail) to see if we can avoid requiring operators go to
> lastest branch-1 (we may end up needing this but lets a have a really good
> reason for it if we do).
> Oh, let this filing be an answer to our [~anoop.hbase]'s old high-level
> question over in HBASE-16189:
> bq. ...means when rolling upgrade done to 2.0, first users have to upgrade to
> some 1.x versions which is having this fix and then to 2.0.. What do you guys
> think Whether we should avoid this kind of indirection? cc Enis Soztutar,
> Stack, Ted Yu, Matteo Bertozzi
> Yeah, lets try to avoid this if we can...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
