-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-29279 Allow throttling alter operation via table configuration #6951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
public static final int PROGRESSIVE_BATCH_SIZE_MAX_DISABLED = -1; | ||
private static final int PROGRESSIVE_BATCH_SIZE_MAX_DEFAULT_VALUE = Integer.MAX_VALUE; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one was unused.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi @rmdmattingly, when you have a moment, could you take a look at this? It's a simple change but I believe it makes the throttling feature much more useful in production. |
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ModifyTableProcedure.java
Outdated
Show resolved
Hide resolved
public static final long PROGRESSIVE_BATCH_BACKOFF_MILLIS_DEFAULT = 0L; | ||
public static final String PROGRESSIVE_BATCH_SIZE_MAX_KEY = | ||
"hbase.reopen.table.regions.progressive.batch.size.max"; | ||
ConfigKey.INT("hbase.reopen.table.regions.progressive.batch.size.max"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Type checks are now necessary.
31c0c8d
to
5529cb4
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Add ReopenTableRegionsProcedure.throttled to create a procedure with the throttling configuration.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
*/ | ||
public static ReopenTableRegionsProcedure throttled(final Configuration conf, | ||
final TableDescriptor desc) { | ||
long backoffMillis = Optional.ofNullable(desc.getValue(PROGRESSIVE_BATCH_BACKOFF_MILLIS_KEY)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pity we do not return Optional for desc.getValue...
@Apache9 Thanks for the approval. I've opened a PR to backport this to |
Hi @junegunn welcome to hbase committers' group. I noticed you have merged a few PRs and missed to mention signed-off to those. Not a problem, even I did same when I became a new committer. But this doc helped me understand how-to's specific to Apache HBase, might be useful to you as well. I wish this (HBASE-21701) was part of our official book! |
Thank you @NihalJain for helping me out, and apologies for missing that part! Could you share your process of adding the "Signed-off-by" and "Reviewed-by" lines to the commit message? Do I have to manually collect the email addresses of the reviewers and write the lines, or is there an easier way to do it? |
I think its all manual, I usually refer hbase teams https://hbase.apache.org/team.html page, or old commits to get email id for a user; if still cant find it, I check their github homepage. If neither of these help, I skip adding it. |
I see, thanks. I guess it'll get easier once I get used to the process. I can imagine writing up a script to automate as much of it as possible. Could it be a good candidate for a |
See https://issues.apache.org/jira/browse/HBASE-29279
Examples