-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-26761 TestMobStoreScanner (testGetMassive) can OOME #4204
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproductable.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Apache9
approved these changes
Mar 11, 2022
pankaj72981
approved these changes
Mar 11, 2022
Apache9
pushed a commit
that referenced
this pull request
Mar 11, 2022
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproductable. Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Pankaj Kumar <pankajkumar@apache.org>
Apache9
pushed a commit
that referenced
this pull request
Mar 11, 2022
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproductable. Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Pankaj Kumar <pankajkumar@apache.org>
Apache9
pushed a commit
that referenced
this pull request
Mar 11, 2022
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproductable. Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Pankaj Kumar <pankajkumar@apache.org>
vinayakphegde
pushed a commit
to vinayakphegde/hbase
that referenced
this pull request
Apr 4, 2024
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproductable. Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Pankaj Kumar <pankajkumar@apache.org> (cherry picked from commit 40f8738) Change-Id: I1535e754190c8d7e3dd0dee70b70ac005e615b06
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the timing of the test but not the objective by storing three large MOB values into the row with three separate puts, each randomizing the data. Increases running time of the testGetMassive case 2x but avoids OOME in the test environment where the OOME was consistently reproducible.