[jira] [Created] (HBASE-26218) Better logging in CanaryTool
Caroline Zhou created HBASE-26218: - Summary: Better logging in CanaryTool Key: HBASE-26218 URL: https://issues.apache.org/jira/browse/HBASE-26218 Project: HBase Issue Type: Improvement Reporter: Caroline Zhou CanaryTool logs currently don't indicate which mode they pertain to – they should at least make note of that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25849) Backport HBASE-22738, HBASE-24760, & HBASE-25298 (Fallback feature for RS groups when there are no RS in current group) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-25849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25849: -- Summary: Backport HBASE-22738, HBASE-24760, & HBASE-25298 (Fallback feature for RS groups when there are no RS in current group) to branch-1 (was: Backport HBASE-22738 & HBASE-24760 (Fallback feature for RS groups when there are no RS in current group) to branch-1) > Backport HBASE-22738, HBASE-24760, & HBASE-25298 (Fallback feature for RS > groups when there are no RS in current group) to branch-1 > --- > > Key: HBASE-25849 > URL: https://issues.apache.org/jira/browse/HBASE-25849 > Project: HBase > Issue Type: Improvement >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25815) RSGroupBasedLoadBalancer online status never updates after being set to true for the first time
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25815: -- Description: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. was: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. Seems to be addressed by HBASE-22662 > RSGroupBasedLoadBalancer online status never updates after being set to true > for the first time > --- > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25815) RSGroupBasedLoadBalancer online status never updates after being set to true for the first time
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25815: -- Description: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. Seems to be addressed by HBASE-22662 was: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. Seems to be addressed by HBASE-21700 > RSGroupBasedLoadBalancer online status never updates after being set to true > for the first time > --- > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. > Seems to be addressed by HBASE-22662 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25815) RSGroupBasedLoadBalancer online status never updates after being set to true for the first time
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25815: -- Summary: RSGroupBasedLoadBalancer online status never updates after being set to true for the first time (was: Backport "HBASE-21700 Simplify the implementation of RSGroupInfoManagerImpl" to branch-1) > RSGroupBasedLoadBalancer online status never updates after being set to true > for the first time > --- > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. > Seems to be addressed by HBASE-21700 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25849) Backport HBASE-22738 & HBASE-24760 (Fallback feature for RS groups when there are no RS in current group) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-25849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25849: -- Summary: Backport HBASE-22738 & HBASE-24760 (Fallback feature for RS groups when there are no RS in current group) to branch-1 (was: Backport "HBASE-22738 Fallback to default group to choose RS when there are no RS in current group" and "HBASE-24760 Add a config hbase.rsgroup.fallback.enable for RSGroup fallback feature" to branch-1) > Backport HBASE-22738 & HBASE-24760 (Fallback feature for RS groups when there > are no RS in current group) to branch-1 > - > > Key: HBASE-25849 > URL: https://issues.apache.org/jira/browse/HBASE-25849 > Project: HBase > Issue Type: Improvement >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25815) Backport "HBASE-21700 Simplify the implementation of RSGroupInfoManagerImpl" to branch-1
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25815: -- Summary: Backport "HBASE-21700 Simplify the implementation of RSGroupInfoManagerImpl" to branch-1 (was: RSGroupBasedLoadBalancer online status never updates after being set to true for the first time) > Backport "HBASE-21700 Simplify the implementation of RSGroupInfoManagerImpl" > to branch-1 > > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. > Seems to be addressed by HBASE-21700 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25815) RSGroupBasedLoadBalancer online status never updates after being set to true for the first time
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25815: -- Description: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. Seems to be addressed by HBASE-21700 was: Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta and hbase:rsgroup tables), it will never update the status again. That means if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update its status to “offline,” so some of the code paths will go through the “online” code path even though the catalog tables aren’t available to be read from or written to (in particular, anything that calls RSGroupInfoManagerImpl#flushConfig). Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which are stored in memory (see order of [these lines of code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is already marked as “online,” exceptions thrown while trying to write to an offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap from being updated. In terms of the order just mentioned, in-memory state should be updated first. > RSGroupBasedLoadBalancer online status never updates after being set to true > for the first time > --- > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. > Seems to be addressed by HBASE-21700 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Add detailed RIT info in JSON format for consumption as metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Summary: Add detailed RIT info in JSON format for consumption as metrics
(was: Create RIT servlet in HMaster to track more detailed RIT info not
captured in metrics)
> Add detailed RIT info in JSON format for consumption as metrics
> ---
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
> Components: master
>Affects Versions: 3.0.0-alpha-1, 2.4.6, 2.3.7
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Labels: observability
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT jsp page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state, table, or server name, and/or adding counts of RIT by state or server
> name.
> !Screen Shot 2021-07-27 at 10.34.45.png!
> !Screen Shot 2021-07-27 at 10.34.53.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-26163) Better logging in RSGroupInfoManagerImpl
Caroline Zhou created HBASE-26163: - Summary: Better logging in RSGroupInfoManagerImpl Key: HBASE-26163 URL: https://issues.apache.org/jira/browse/HBASE-26163 Project: HBase Issue Type: Improvement Reporter: Caroline Zhou Assignee: Caroline Zhou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-25815) RSGroupBasedLoadBalancer online status never updates after being set to true for the first time
[ https://issues.apache.org/jira/browse/HBASE-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou reassigned HBASE-25815: - Assignee: Caroline Zhou > RSGroupBasedLoadBalancer online status never updates after being set to true > for the first time > --- > > Key: HBASE-25815 > URL: https://issues.apache.org/jira/browse/HBASE-25815 > Project: HBase > Issue Type: Bug >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > Once the RSGroupBasedLoadBalancer is “online” (it has found the hbase:meta > and hbase:rsgroup tables), it will never update the status again. That means > if hbase:meta or hbase:rsgroup ever go offline, the balancer doesn’t update > its status to “offline,” so some of the code paths will go through the > “online” code path even though the catalog tables aren’t available to be read > from or written to (in particular, anything that calls > RSGroupInfoManagerImpl#flushConfig). > Also, in the RSGroupInfoManagerImpl#flushConfig code path, the call to write > to hbase:rsgroup comes before the update to the rsGroupMap and tableMap which > are stored in memory (see order of [these lines of > code|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L664-L670]), > so if hbase:rsgroup goes offline after the RSGroupBasedLoadBalancer is > already marked as “online,” exceptions thrown while trying to write to an > offline hbase:rsgroup table prevent the in-memory rsGroupMap and tableMap > from being updated. In terms of the order just mentioned, in-memory state > should be updated first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT jsp page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc. This JSON dump can be served as a servlet.
We may also consider different ways of grouping the JSON results, such as by
state, table, or server name, and/or adding counts of RIT by state or server
name.
!Screen Shot 2021-07-27 at 10.34.45.png!
!Screen Shot 2021-07-27 at 10.34.53.png!
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc. This JSON dump can be served as a servlet.
We may also consider different ways of grouping the JSON results, such as by
state or server name.
!Screen Shot 2021-07-27 at 10.34.45.png!
!Screen Shot 2021-07-27 at 10.34.53.png!
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT jsp page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state, table, or server name, and/or adding counts of RIT by state or server
> name.
> !Screen Shot 2021-07-27 at 10.34.45.png!
> !Screen Shot 2021-07-27 at 10.34.53.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388214#comment-17388214
]
Caroline Zhou edited comment on HBASE-25469 at 7/27/21, 5:44 PM:
-
[~apurtell] [~stack] [~tianjingyun] [~bharathv] [~vjasani] Please take a look.
Added a few fields to the rit.jsp page as well as created a new servlet to
serve individual RIT information as json (RIT info in one place, can be parsed
for metrics). A couple of things to consider/I would like your feedback on:
* Any other fields we should add to the json output? (Aggregates like
ritCount, ritCountOverThreshold, etc. can be found in AssignmentManager metrics
so I didn't include those here, but we could also provide counts by RIT
state/by server.)
* Should we include the ability for the json to display only RIT over
threshold/RITs grouped by state or server name?
I would also like to backport this to branch-1, after master PR is approved.
Thanks.
was (Author: caroliney14):
[~apurtell] [~stack] [~tianjingyun] [~bharathv] [~vjasani] Please take a look.
Added a few fields to the rit.jsp page as well as created a new servlet to
serve individual RIT information as json (RIT info in one place, can be parsed
for metrics). A couple of things to consider/I would like your feedback on:
* Any other fields we should add to the json output? (Aggregates like
ritCount, ritCountOverThreshold, etc. can be found in AssignmentManager metrics
so I didn't include those here.)
* Should we include the ability for the json to display only RIT over
threshold/RITs grouped by state or server name?
I would also like to backport this to branch-1, after master PR is approved.
Thanks.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
> !Screen Shot 2021-07-27 at 10.34.45.png!
> !Screen Shot 2021-07-27 at 10.34.53.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388214#comment-17388214
]
Caroline Zhou commented on HBASE-25469:
---
[~apurtell] [~stack] [~tianjingyun] [~bharathv] [~vjasani] Please take a look.
Added a few fields to the rit.jsp page as well as created a new servlet to
serve individual RIT information as json (RIT info in one place, can be parsed
for metrics). A couple of things to consider/I would like your feedback on:
* Any other fields we should add to the json output? (Aggregates like
ritCount, ritCountOverThreshold, etc. can be found in AssignmentManager metrics
so I didn't include those here.)
* Should we include the ability for the json to display only RIT over
threshold/RITs grouped by state or server name?
I would also like to backport this to branch-1, after master PR is approved.
Thanks.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
> !Screen Shot 2021-07-27 at 10.34.45.png!
> !Screen Shot 2021-07-27 at 10.34.53.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Attachment: Screen Shot 2021-07-27 at 10.34.53.png
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc. This JSON dump can be served as a servlet.
We may also consider different ways of grouping the JSON results, such as by
state or server name.
!Screen Shot 2021-07-27 at 10.34.45.png!
!Screen Shot 2021-07-27 at 10.34.53.png!
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc. This JSON dump can be served as a servlet.
We may also consider different ways of grouping the JSON results, such as by
state or server name.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
> !Screen Shot 2021-07-27 at 10.34.45.png!
> !Screen Shot 2021-07-27 at 10.34.53.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Attachment: Screen Shot 2021-07-27 at 10.34.45.png
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
> Attachments: Screen Shot 2021-07-27 at 10.34.45.png, Screen Shot
> 2021-07-27 at 10.34.53.png
>
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc. This JSON dump can be served as a servlet.
We may also consider different ways of grouping the JSON results, such as by
state or server name.
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
The query to see all RITs is
{{/rits.jsp?format=json=region=null=null}}. We can add a
parameter {{=}} to not include RITs not over threshold in the
JSON. We may also consider different ways of grouping the JSON results, such as
by state or server name (the latter would require a new parameter {{=}}).
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc. This JSON dump can be served as a servlet.
> We may also consider different ways of grouping the JSON results, such as by
> state or server name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
The query to see all RITs is
{{/rits.jsp?format=json=region=null=null}}. We can add a
parameter {{=}} to not include RITs not over threshold in the
JSON. We may also consider different ways of grouping the JSON results, such as
by state or server name (the latter would require a new parameter {{=}}).
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc.
> The query to see all RITs is
> {{/rits.jsp?format=json=region=null=null}}. We can add a
> parameter {{=}} to not include RITs not over threshold in
> the JSON. We may also consider different ways of grouping the JSON results,
> such as by state or server name (the latter would require a new parameter
> {{=}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
Additionally, this info can be added to the table under the {{/rit.jsp}} page,
and we can also add a button on that page to view info as JSON, for easy
parsing into metrics, etc.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place (some already found on the page):
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
Additionally, this info can be added to the table under the {{/rit.jsp}} page,
and we can also add a button on that page to view info as JSON, for easy
parsing into metrics, etc.
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* Region Hash
* Table
* Region State
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Id
* Procedure Type
* Procedure State
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place (some already found on the page):
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> Additionally, this info can be added to the table under the {{/rit.jsp}}
> page, and we can also add a button on that page to view info as JSON, for
> easy parsing into metrics, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
Additionally, this info can be added to the table under the {{/rit.jsp}} page,
and we can also add a button on that page to view info as JSON, for easy
parsing into metrics, etc.
was:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place (some already found on the page):
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Type
Additionally, this info can be added to the table under the {{/rit.jsp}} page,
and we can also add a button on that page to view info as JSON, for easy
parsing into metrics, etc.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Type
> Additionally, this info can be added to the table under the {{/rit.jsp}}
> page, and we can also add a button on that page to view info as JSON, for
> easy parsing into metrics, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[
https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caroline Zhou updated HBASE-25469:
--
Description:
In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
There are some additional RIT details that would be helpful to have in one
place:
* Region Hash
* Table
* Region State
* RIT Start Time
* RIT Duration (ms)
* Server
* Procedure Id
* Procedure Type
* Procedure State
This info can be added to the table under the {{/rit.jsp}} page, and we can
also add a button on that page to view info as JSON, for easy parsing into
metrics, etc.
> Create RIT servlet in HMaster to track more detailed RIT info not captured in
> metrics
> -
>
> Key: HBASE-25469
> URL: https://issues.apache.org/jira/browse/HBASE-25469
> Project: HBase
> Issue Type: Improvement
>Reporter: Caroline Zhou
>Assignee: Caroline Zhou
>Priority: Minor
>
> In HBase 2.1+, there is a RIT JSP page that was added as part of HBASE-21410.
> There are some additional RIT details that would be helpful to have in one
> place:
> * Region Hash
> * Table
> * Region State
> * RIT Start Time
> * RIT Duration (ms)
> * Server
> * Procedure Id
> * Procedure Type
> * Procedure State
> This info can be added to the table under the {{/rit.jsp}} page, and we can
> also add a button on that page to view info as JSON, for easy parsing into
> metrics, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HBASE-25469) Create RIT servlet in HMaster to track more detailed RIT info not captured in metrics
[ https://issues.apache.org/jira/browse/HBASE-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou reassigned HBASE-25469: - Assignee: Caroline Zhou > Create RIT servlet in HMaster to track more detailed RIT info not captured in > metrics > - > > Key: HBASE-25469 > URL: https://issues.apache.org/jira/browse/HBASE-25469 > Project: HBase > Issue Type: Improvement >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-23080) Add table-level fallback feature for RS groups
[ https://issues.apache.org/jira/browse/HBASE-23080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339435#comment-17339435 ] Caroline Zhou edited comment on HBASE-23080 at 5/5/21, 6:19 AM: Thanks [~apurtell] and [~Xiaolin Ha]. It looks like some fallback logic is already implemented in master/branch-2 as part of HBASE-22738 and HBASE-24760, but not on a per-table basis. I've repurposed this Jira for table-level fallback and created HBASE-25849 for the backporting of the previous 2 issues. was (Author: caroliney14): Thanks [~apurtell] and [~Xiaolin Ha]. It looks like some fallback logic is already implemented in master/branch-2 as part of HBASE-22738 and HBASE-24760, but not on a per-table basis. I've repurposed this Jira for table-level fallback. > Add table-level fallback feature for RS groups > -- > > Key: HBASE-23080 > URL: https://issues.apache.org/jira/browse/HBASE-23080 > Project: HBase > Issue Type: Improvement > Components: rsgroup >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25849) Backport "HBASE-22738 Fallback to default group to choose RS when there are no RS in current group" and "HBASE-24760 Add a config hbase.rsgroup.fallback.enable for RSGro
Caroline Zhou created HBASE-25849: - Summary: Backport "HBASE-22738 Fallback to default group to choose RS when there are no RS in current group" and "HBASE-24760 Add a config hbase.rsgroup.fallback.enable for RSGroup fallback feature" to branch-1 Key: HBASE-25849 URL: https://issues.apache.org/jira/browse/HBASE-25849 Project: HBase Issue Type: Improvement Reporter: Caroline Zhou Assignee: Caroline Zhou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23080) Add table-level fallback feature for RS groups
[ https://issues.apache.org/jira/browse/HBASE-23080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339435#comment-17339435 ] Caroline Zhou commented on HBASE-23080: --- Thanks [~apurtell] and [~Xiaolin Ha]. It looks like some fallback logic is already implemented in master/branch-2 as part of HBASE-22738 and HBASE-24760, but not on a per-table basis. I've repurposed this Jira for table-level fallback. > Add table-level fallback feature for RS groups > -- > > Key: HBASE-23080 > URL: https://issues.apache.org/jira/browse/HBASE-23080 > Project: HBase > Issue Type: Improvement > Components: rsgroup >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23080) Add table-level fallback feature for RS groups
[ https://issues.apache.org/jira/browse/HBASE-23080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-23080: -- Summary: Add table-level fallback feature for RS groups (was: Purge LoadBalancer.BOGUS_SERVER_NAME in rsgroup) > Add table-level fallback feature for RS groups > -- > > Key: HBASE-23080 > URL: https://issues.apache.org/jira/browse/HBASE-23080 > Project: HBase > Issue Type: Improvement > Components: rsgroup >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25846) RSGroupBasedLoadBalancer does not allow dynamic config setting
[ https://issues.apache.org/jira/browse/HBASE-25846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339379#comment-17339379 ] Caroline Zhou commented on HBASE-25846: --- Thanks [~zhangduo], I wasn't aware of HBASE-25825 before reporting this one. Can I backport HBASE-25825 to branch-1 and have you review? > RSGroupBasedLoadBalancer does not allow dynamic config setting > -- > > Key: HBASE-25846 > URL: https://issues.apache.org/jira/browse/HBASE-25846 > Project: HBase > Issue Type: Improvement >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > In branch-1, > [RSGroupBasedLoadBalancer#onConfigurationChange|https://github.com/apache/hbase/blob/branch-1/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L452] > doesn't do anything – it should call the internal balancer's > onConfigurationChange(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-25846) RSGroupBasedLoadBalancer does not allow dynamic config setting
[ https://issues.apache.org/jira/browse/HBASE-25846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline Zhou updated HBASE-25846: -- Description: In branch-1, [RSGroupBasedLoadBalancer#onConfigurationChange|https://github.com/apache/hbase/blob/branch-1/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L452] doesn't do anything – it should call the internal balancer's onConfigurationChange(). (was: In master/branch-2, [RSGroupBasedLoadBalancer#onConfigurationChange|[https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L411]] only accounts for changes in the fallback setting, and in branch-1, [RSGroupBasedLoadBalancer#onConfigurationChange|https://github.com/apache/hbase/blob/branch-1/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L452] doesn't do anything at all. In both cases, we should also call the internal balancer's onConfigurationChange().) > RSGroupBasedLoadBalancer does not allow dynamic config setting > -- > > Key: HBASE-25846 > URL: https://issues.apache.org/jira/browse/HBASE-25846 > Project: HBase > Issue Type: Improvement >Reporter: Caroline Zhou >Assignee: Caroline Zhou >Priority: Minor > > In branch-1, > [RSGroupBasedLoadBalancer#onConfigurationChange|https://github.com/apache/hbase/blob/branch-1/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L452] > doesn't do anything – it should call the internal balancer's > onConfigurationChange(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25846) RSGroupBasedLoadBalancer does not allow dynamic config setting
Caroline Zhou created HBASE-25846: - Summary: RSGroupBasedLoadBalancer does not allow dynamic config setting Key: HBASE-25846 URL: https://issues.apache.org/jira/browse/HBASE-25846 Project: HBase Issue Type: Improvement Reporter: Caroline Zhou Assignee: Caroline Zhou In master/branch-2, [RSGroupBasedLoadBalancer#onConfigurationChange|[https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L411]] only accounts for changes in the fallback setting, and in branch-1, [RSGroupBasedLoadBalancer#onConfigurationChange|https://github.com/apache/hbase/blob/branch-1/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupBasedLoadBalancer.java#L452] doesn't do anything at all. In both cases, we should also call the internal balancer's onConfigurationChange(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
