-
Notifications
You must be signed in to change notification settings - Fork 440
TEZ-4667: Correct the test case testInMemAllocationWithJvmMaxMemory #445
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
|
🎊 +1 overall
This message was automatically generated. |
|
@maheshrajus: thanks for taking care of this, a few questions:
|
|
@abstractdog INFO [Time-limited test] impl.TestSimpleFetchedInputAllocator (TestSimpleFetchedInputAllocator.java:testInMemAllocationWithJvmMaxMemory(99)) - jvmMax: 1073741824 here RequestSize should be greater than InMemThreshold. Then only it will allocate from the DISK. So it is failing in some env only. In any case we should put more RequestSize . So currently Test sample: |
|
I still feel the test case is shady in its current form, and I'm afraid this fix won't make it any clearer requestSize should be greater than inMemThreshold, which is a lower bound, also I guess it has an upper bound constraint (jvm memory, or whatever), am I right to assume that? could this line be clearer to comply with those constraints and work in every scenario (regardless of the jvmMax) |
|
@abstractdog I will make requestSize simple instead of jvm memory and "(long) (0.4f * inMemThreshold) + 100L" checks. Lower bound value already tested in existed test cases. i will put requestSize size more than inMemThreshold and test the scenario Planning to modify like this: |
|
🎊 +1 overall
This message was automatically generated. |
|
@abstractdog Can you review and approve the changes ? thanks ! |
This test case is failing in some env when requested memory is less compared to available memory.
We need to increase the requested memory so that it will not fail.