[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049129#comment-17049129
]
Hudson commented on HBASE-22695:
Results for branch master
[build #1649 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1649/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1649//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1649//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1649//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926567#comment-16926567
]
Hudson commented on HBASE-22695:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926389#comment-16926389
]
Hudson commented on HBASE-22695:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[ https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905660#comment-16905660 ] Xu Cang commented on HBASE-22695: - I am late for the discussion, but still would love to know, what's the rationale doing this? Thanks! > Store the rsgroup of a table in table configuration > --- > > Key: HBASE-22695 > URL: https://issues.apache.org/jira/browse/HBASE-22695 > Project: HBase > Issue Type: Sub-task > Components: rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: HBASE-22514 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[ https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893330#comment-16893330 ] Duo Zhang commented on HBASE-22695: --- I mean do it asynchronously. Just need to trigger the balancer I think. > Store the rsgroup of a table in table configuration > --- > > Key: HBASE-22695 > URL: https://issues.apache.org/jira/browse/HBASE-22695 > Project: HBase > Issue Type: Sub-task > Components: rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892617#comment-16892617
]
Xiaolin Ha commented on HBASE-22695:
{quote}I prefer we do not trigger a move when doing this first, including
changing the server set of a rsgroup. Let's do this asynchronously.
{quote}
If we add rsgroup info to table config, then we don't need to move regions
after creating table.
But how can we not move regions when change the server set of a rsgroup?
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[ https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888706#comment-16888706 ] Duo Zhang commented on HBASE-22695: --- This will be huge change. I think we need to define the behavior first. In the old implementation, changing the rsgroup of a table will lead to a move, but changing the rsgroup config of a namespace will not. In general, I prefer we do not trigger a move when doing this first, including changing the server set of a rsgroup. Let's do this asynchronously. The only exception is changing the rsgroup config of a table, where we need to reopen the regions of a table. Later we could see if we can provide a synchronous way, maybe we can return a proc id to client to let them query the status, just like what we have done for create table, etc. > Store the rsgroup of a table in table configuration > --- > > Key: HBASE-22695 > URL: https://issues.apache.org/jira/browse/HBASE-22695 > Project: HBase > Issue Type: Sub-task > Components: rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
