[
https://issues.apache.org/jira/browse/HBASE-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039718#comment-16039718
]
stack commented on HBASE-18109:
-------------------------------
Agree on the scheduling, that it is inexact. I think the original author would
probably argue that given assignment is multi-step, the above favoring of
high-priority tasks will in the end make it so hbase:meta and system tables get
assigned first. He'd have a point I think; I've not much experience watching
this stuff in real deploys. Would be cool if could get more insurance that
high-priority tasks are scheduled first.
#1 makes most sense I think. Default would be user priority. I'd think we'd
keep priority an internal setting, not generally available, otherwise, all will
set their tables as high-priority. We can take care of known-system-tables by
setting their priority internally, explicitly. We can in a follow-on work on
how we'd expose this feature so only @phil yang could use it (smile) and maybe
one or two others if they make a deposit in a particular bank account. What you
think [~easyliangjob]?
> Assign system tables first (priority)
> -------------------------------------
>
> Key: HBASE-18109
> URL: https://issues.apache.org/jira/browse/HBASE-18109
> Project: HBase
> Issue Type: Sub-task
> Components: Region Assignment
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: Yi Liang
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-18109-V1.patch
>
>
> Need this for stuff like the RSGroup table, etc. Assign these ahead of
> user-space regions.
> From 'Handle sys table assignment first (e.g. acl, namespace, rsgroup);
> currently only hbase:meta is first.' of
> https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.oefcyphs0v0x
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
