-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HDFS-15882. Fix incorrectly initializing RandomAccessFile based on configuration options #2751
Conversation
hi @aajisaka, please take a review when you're free, thanks. |
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. +1 from my side. Will commit if no other comments shortly.
LGTM |
Thanks @Hexiaoqiao @leosunli |
Sorry for late response, just check yetus report, I found there are many failed unit tests. Do you mind to trigger Yetus again? |
Yeah, we use
|
976fa03
to
d380f26
Compare
…configuration options
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
The failed unit tests seems not related to this PR, committed to trunk. Thanks @lamberken for your report and contributions. |
…nfiguration options (apache#2751). Contributed by Xie Lei. Reviewed-by: He Xiaoqiao <[email protected]>
ISSUE
https://issues.apache.org/jira/browse/HDFS-15882
NOTICE
rw
Open for reading and writing. If the file does not already exist then an attempt will be made to create it.rws
Require that every update to the file's content or metadata be written synchronously to the underlying storage device.From the literal meaning of this variable
shouldSyncWritesAndSkipFsync
, we should userw
when shouldSyncWritesAndSkipFsync is true.We use SATA disk to store the journal node's data. It's not effective for improving RPC performance whether the
shouldSyncWritesAndSkipFsync
variable is true or false. it's caused by initializing RandomAccessFile incorrectly.