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.
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
Support use default block size to replace the Hdfs ufs #14324
base: master-2.x
Are you sure you want to change the base?
Support use default block size to replace the Hdfs ufs #14324
Changes from 2 commits
e1e2060
06c39f9
5584b61
5e8583d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think this only reads the server-side default, so it doesn't take your path config or configuration from your client command. This defeats the purpose of having this property.
@beinan @yuzhu Do you know how to make this respect both the client-side config and path config? I'm afraid making this respect user-side config needs this property value to be in
message FileSystemCommonPOptions
. Getting the path config is easier than modifying RPC, but I forgot how :(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.
In order to pick up the correct path-specific setting, we will need to resolve the config for the path. The path configs are returned from master
alluxio/core/server/master/src/main/java/alluxio/master/meta/DefaultMetaMaster.java
Line 430 in ef6b7ef
to the client
alluxio/core/client/fs/src/main/java/alluxio/client/file/FileSystemContext.java
Line 433 in ef6b7ef
Then the client will resolve the path config. This is how you set
sync.interval
usingalluxio pathConf add /path
then how that takes effect.The annoying thing is, in the sync process the master is actually the client that needs to do the path resolution, and currently there's no API you can directly call. @maobaolong I will take over this part and add one API for you to use. So in your PR here it should be just an easy call.
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.
@ggezer @yuzhu I have the feeling that the in-Alluxio block size should always be the Alluxio configuration block size, instead of the UFS one. If the user is not happy with the size config then he/she can use Alluxio path config to update that. WDYT?
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.
+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.
+1 if you have different block sizes for different paths, you still need to update them with path config anyways so no need to create a new property for this.