[jira] [Commented] (HBASE-26588) Implement a migration tool to help users migrate SFT implementation for a large set of tables
[ https://issues.apache.org/jira/browse/HBASE-26588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495144#comment-17495144 ] Duo Zhang commented on HBASE-26588: --- HBASE-26673 has been resolved. Maybe it is enough for most of our users? > Implement a migration tool to help users migrate SFT implementation for a > large set of tables > - > > Key: HBASE-26588 > URL: https://issues.apache.org/jira/browse/HBASE-26588 > Project: HBase > Issue Type: Sub-task > Components: tooling >Reporter: Duo Zhang >Priority: Major > > It will be very useful for our users who deploy HBase on S3 like systems. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (HBASE-26588) Implement a migration tool to help users migrate SFT implementation for a large set of tables
[
https://issues.apache.org/jira/browse/HBASE-26588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476228#comment-17476228
]
Duo Zhang commented on HBASE-26588:
---
{quote}
Was thinking about a new hbase shell command that would allow on the new API
method, yeah. Maybe the command should allow to either migrate all at once, or
a subset of tables passed as parameters.
{quote}
Agree we should have a shell command. Filed HBASE-26673 for this. On migrating
at once, checked the code base, we have disable_all and drop_all, so maybe it
is OK to implement a 'change_sft_all'?
> Implement a migration tool to help users migrate SFT implementation for a
> large set of tables
> -
>
> Key: HBASE-26588
> URL: https://issues.apache.org/jira/browse/HBASE-26588
> Project: HBase
> Issue Type: Sub-task
> Components: tooling
>Reporter: Duo Zhang
>Priority: Major
>
> It will be very useful for our users who deploy HBase on S3 like systems.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (HBASE-26588) Implement a migration tool to help users migrate SFT implementation for a large set of tables
[ https://issues.apache.org/jira/browse/HBASE-26588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469966#comment-17469966 ] Wellington Chevreuil commented on HBASE-26588: -- Was thinking about a new hbase shell command that would allow on the new API method, yeah. Maybe the command should allow to either migrate all at once, or a subset of tables passed as parameters. Maybe also come with a convenient command to list all tables whose tracker config diverges from the global config specified one? > Implement a migration tool to help users migrate SFT implementation for a > large set of tables > - > > Key: HBASE-26588 > URL: https://issues.apache.org/jira/browse/HBASE-26588 > Project: HBase > Issue Type: Sub-task > Components: tooling >Reporter: Duo Zhang >Priority: Major > > It will be very useful for our users who deploy HBase on S3 like systems. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (HBASE-26588) Implement a migration tool to help users migrate SFT implementation for a large set of tables
[ https://issues.apache.org/jira/browse/HBASE-26588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460845#comment-17460845 ] Duo Zhang commented on HBASE-26588: --- I think the tool will be straight forward, just call the API in HBASE-26587 to change the SFT implementation for all tables on the cluster. A possible configurable value is the max concurrency, i.e, how many tables can be altered concurrently. > Implement a migration tool to help users migrate SFT implementation for a > large set of tables > - > > Key: HBASE-26588 > URL: https://issues.apache.org/jira/browse/HBASE-26588 > Project: HBase > Issue Type: Sub-task > Components: tooling >Reporter: Duo Zhang >Priority: Major > > It will be very useful for our users who deploy HBase on S3 like systems. -- This message was sent by Atlassian Jira (v8.20.1#820001)
