-
Couldn't load subscription status.
- Fork 3.4k
HBASE-25603 Add switch for compaction after bulkload #2982
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
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
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.
Please add a note describing this new property in the related ref-guide section.
| this.rsServices.getCompactionRequestor().requestCompaction(this, store, | ||
| "bulkload hfiles request compaction", Store.PRIORITY_USER + 1, | ||
| CompactionLifeCycleTracker.DUMMY, null); | ||
| if (conf.getBoolean(HConstants.COMPACTION_AFTER_BULKLOAD_ENABLE, false)) { |
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.
Shouldn't it be enabled by default, to keep consistent with previous behaviour?
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.
Yes,but I think it's better to set false by default, this feature will be enable only when user explicitly set it. Otherwise difficult to find this performance effect
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.
I agree with @wchevreuil that we'd better keep the old behavior by default, at least on branch-2. We could file a new issue to change it to false on master branch. WDYT?
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.
Yes, I totally agree
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.
@wchevreuil I have added in ref-guide section.
| this.rsServices.getCompactionRequestor().requestCompaction(this, store, | ||
| "bulkload hfiles request compaction", Store.PRIORITY_USER + 1, | ||
| CompactionLifeCycleTracker.DUMMY, null); | ||
| if (conf.getBoolean(HConstants.COMPACTION_AFTER_BULKLOAD_ENABLE, false)) { |
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.
I agree with @wchevreuil that we'd better keep the old behavior by default, at least on branch-2. We could file a new issue to change it to false on master branch. WDYT?
hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
Outdated
Show resolved
Hide resolved
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
Signed-off-by: Duo Zhang <[email protected]> Signed-off-by: Wellington Chevreuil <[email protected]>
when compaction after bulkload is enable, if bulkload is continuous, considerable compaction events will be triggered, which increase load, bring about performance impact