[
https://issues.apache.org/jira/browse/HBASE-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519000#comment-14519000
]
Andrey Stepachev commented on HBASE-13147:
------------------------------------------
Thank you [~ram_krish] for looking at this thing.
{quote}
remove(META_VERSION_KEY);
{quote}
Yeah. That is to remove version from meta. But for now I'm thinking to make
field tableVersion visible to users. So user can use this version for its own
versioning if needed.
And we can use versions for other tables if needed.
{quote}
Just on master coming up we will do the migration
{quote}
yes, when master is starting and didn't found descriptor
it will upgrade meta. Next meta should be reassigned
to recent region server, and that is next jira i think, because
there are serveral ways to do so.
> 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)
