-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
unixfs autosharding with config #8527
Conversation
|
da36d77
to
e51a8dd
Compare
c2925e2
to
9a0c4a5
Compare
9a0c4a5
to
fd55804
Compare
@@ -216,7 +216,7 @@ jobs: | |||
command: | | |||
npm init -y | |||
npm install ipfs@^0.59.1 | |||
npm install ipfs-interop@^7.0.3 |
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.
TODO: use a version of interop that's on master
- applies fix from go-ipfs-config which removes null when default - escapes JSON string when passed in sharness script
* test: add tests for automatic sharding and unsharding * refactor: changed some naming in the sharding sharness tests to make more sense Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>
893e6a9
to
e0b6bb4
Compare
We switch to autosharding setup in ipfs/kubo#8527
This ensures existing users of global sharding experiment get notified that the flag no longer works + that autosharding happens automatically. For people who NEED to keep the old behavior (eg. have no time to migrate today) there is a note about restoring it with `UnixFSShardingSizeThreshold`.
// Migrate users of deprecated Experimental.ShardingEnabled flag | ||
if cfg.Experimental.ShardingEnabled { | ||
logger.Fatal("The `Experimental.ShardingEnabled` field is no longer used, please remove it from the config.\n" + | ||
"go-ipfs now automatically shards when directory block is bigger than `" + shardSizeString + "`.\n" + | ||
"If you need to restore the old behavior (sharding everything) set `Internal.UnixFSShardingSizeThreshold` to `1B`.\n") | ||
} |
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.
ℹ️ This provides a migration path for existing users that have experiment enabled.
I also updated docs/experimental-features.md
and made flag optional in JSON in ipfs/go-ipfs-config#158
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. This seems like the best we can get.
There's no way to warn anybody who explicitly wanted sharding to stay off since that flag didn't have no way to denote "unset" which is what we're moving towards now.
We switch to autosharding setup in ipfs/kubo#8527
Continued in #8563 |
We switch to autosharding setup in ipfs#8527
We switch to autosharding setup in ipfs#8527
We switch to autosharding setup in ipfs#8527
We switch to autosharding setup in ipfs#8527
Related to #8114 and may end up merging onto it.
ipfs/go-ipfs-config#149 adds
Internal.UnixFSShardingSizeThreshold
config flagTesting:
Experimental.ShardingEnabled
?