-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-28601 Enable setting memstore on-heap sizes in bytes #7726
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
base: master
Are you sure you want to change the base?
Conversation
liuxiaocs7
commented
Feb 10, 2026
- see: HBASE-28601
ndimiduk
left a comment
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.
LGTM!
| */ | ||
| public static long getMemstoreSizeInBytes(Configuration conf) { | ||
| try { | ||
| return Long.parseLong(conf.get(MEMSTORE_MEMORY_SIZE_KEY, "-1")); |
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.
Can we support human-friendly values here?
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.
Hi, @ndimiduk, sure, we support human-friendly values, just like in blockcache, and I add some more test cases in jira, please help take a look when free, thanks!!!
|
Hi, @ndimiduk, in the runner summary(https://github.com/apache/hbase/actions/runs/21860359593?pr=7726), how can we see which ut failed, thanks! |
|
The failed units test should be mentioned in a table in the Summary of the run. It's kinda hard to find on the GitHub UI, and it appears to not render at all on mobile. I'll get you a direct link when I'm back at my desk. |
|
I thought I had added this feature along with the unit test job, but I don't see the failed tests in the summary. For now, you'll have to download the artifact from that medium test run and look for the surefire reports there. Let me see what happened to that feature in our build. |
|
I see. I'm parsing Failures but not Errors -- i.e., unit test assertions that failed, but not uncaught thrown exceptions and the like. That's an omission. |
Hi, @ndimiduk, thank you very much for your quick response. I'm relieved we've identified the underlying issue, which explains why I could sometimes see failed UTs in the Summary and sometimes not. In any case, thank you for your efforts!!! |
|
For example, in this runner job summary(https://github.com/apache/hbase/actions/runs/21894809023), we can see |
|
@ndimiduk Got it, thanks Nick! |
8f1a2a2 to
f0e48fb
Compare
|
Hi, @ndimiduk, thanks for help to retrigger the ut, medium test fails seems the first three uts below fails on my local env, maybe they need to upgrade to junit5 because they extends |
|
Let's see #7744 |
With #7744, medium test could pass(https://github.com/apache/hbase/actions/runs/21958775498?pr=7744)! |
