[
https://issues.apache.org/jira/browse/HBASE-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518735#comment-14518735
]
ramkrishna.s.vasudevan commented on HBASE-13147:
------------------------------------------------
I may be wrong here but just asking
{code}
remove(META_VERSION_KEY);
{code}
When we will be needing this removal to happen for a non-meta case?
bq. MetaMigration.migrateMeta(fsd);
Just on master coming up we will do the migration?
bq. bootstrap(rd, c);
There is some code called bootStrap in the MasterFileSystem. so if META is not
found it will load only the new TableDescriptor for META with the new version
in it right?
> Load actual META table descriptor, don't use statically defined one.
> --------------------------------------------------------------------
>
> Key: HBASE-13147
> URL: https://issues.apache.org/jira/browse/HBASE-13147
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 2.0.0
> Reporter: Andrey Stepachev
> Assignee: Andrey Stepachev
> Attachments: HBASE-13147-branch-1.patch,
> HBASE-13147-branch-1.v2.patch, HBASE-13147.patch, HBASE-13147.v2.patch,
> HBASE-13147.v3.patch, HBASE-13147.v4.patch, HBASE-13147.v4.patch,
> HBASE-13147.v5.patch, HBASE-13147.v6.patch, HBASE-13147.v7.patch
>
>
> In HBASE-13087 stumbled on the fact, that region servers don't see actual
> meta descriptor, they use their own, statically compiled.
> Need to fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
