go-ipfs-config: Remove badger2 profile

This is needed for the upcoming release since there is not yet an official badger2 release with the items needed for use by IPFS.
This commit is contained in:
gammazero 2020-11-23 17:09:21 -08:00
parent 1ec9262cda
commit 74dcf427fc
2 changed files with 1 additions and 35 deletions

View File

@ -142,19 +142,6 @@ func badgerSpec() map[string]interface{} {
}
}
func badger2Spec() map[string]interface{} {
return map[string]interface{}{
"type": "measure",
"prefix": "badger2.datastore",
"child": map[string]interface{}{
"type": "badger2ds",
"path": "badger2ds",
"syncWrites": false,
"truncate": true,
},
}
}
func flatfsSpec() map[string]interface{} {
return map[string]interface{}{
"type": "mount",

View File

@ -152,27 +152,6 @@ This profile may only be applied when first initializing the node.
"badgerds": {
Description: `Configures the node to use the badger datastore.
This is a fast datastore. Use this datastore if performance, especially
when adding many gigabytes of files, is critical. However:
* This datastore will not properly reclaim space when your datastore is
smaller than several gigabytes. If you run IPFS with '--enable-gc' (you have
enabled block-level garbage collection), you plan on storing very little data in
your IPFS node, and disk usage is more critical than performance, consider using
flatfs.
* This datastore uses up to several gigabytes of memory.
This profile may only be applied when first initializing the node.`,
InitOnly: true,
Transform: func(c *Config) error {
c.Datastore.Spec = badgerSpec()
return nil
},
},
"badger2ds": {
Description: `Configures the node to use the badger2 datastore.
This is the fastest datastore. Use this datastore if performance, especially
when adding many gigabytes of files, is critical. However:
@ -187,7 +166,7 @@ This profile may only be applied when first initializing the node.`,
InitOnly: true,
Transform: func(c *Config) error {
c.Datastore.Spec = badger2Spec()
c.Datastore.Spec = badgerSpec()
return nil
},
},