-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-16650.Optimize the cost of obtaining timestamps in Centralized cache management. #4528
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. |
|
Here are some unit tests that are failing. E.g: It looks like these failed unit tests have little to do with the code I submitted. |
ZanderXu
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.
Thanks @jianghuazhu for your work. LGTM.
And the failed UT org.apache.hadoop.hdfs.server.mover.TestMover.testScheduleBlockLocality work well locally.
|
Thanks @ZanderXu . |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |



Description of PR
Getting timestamps in Centralized cache management is done in the following ways:
long now = new Date().getTime();
This way doesn't seem optimal.
The purpose of pr here is to simplify them.
Details: HDFS-16650
How was this patch tested?
Here is just a change of method, for the test, the pressure is not too big.