You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Motivation
* `linera-server initialize` is redundant with `linera storage
initialize`
* CLI arguments are duplicated in many places.
* `StorageConfigNamespace` could have a simpler name
## Proposal
* Remove `linera-server initialize`
* Create `CommonStorageOptions` and used `#[Clap::flatten]` to share
code between the different binaries.
* Rename `StorageConfig` into `InnerStorageConfig`
* Rename `StorageConfigNamespace` into `StorageConfig`
`InnerStorageConfig` is still visible and used directly in a few places
for now, but we'd like `StorageConfig` to be the real public type.
NOTE: The common storage options are now prefixed with `--storage`, e.g.
`--storage-cache-size`.
## Test Plan
CI + `git grep linera-server`
## Release Plan
- Nothing to do / These changes follow the usual release cycle.
Copy file name to clipboardExpand all lines: CLI.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,6 @@ A Byzantine-fault tolerant sidechain with low-latency finality and high throughp
108
108
109
109
###### **Options:**
110
110
111
-
*`--storage <STORAGE_CONFIG>` — Storage configuration for the blockchain history
112
111
*`--wallet <WALLET_STATE_PATH>` — Sets the file storing the private state of user chains (an empty one will be created if missing)
113
112
*`--keystore <KEYSTORE_PATH>` — Sets the file storing the keystore state
114
113
*`-w`, `--with-wallet <WITH_WALLET>` — Given an ASCII alphanumeric parameter `X`, read the wallet state and the wallet storage config from the environment variables `LINERA_WALLET_{X}` and `LINERA_STORAGE_{X}` instead of `LINERA_WALLET` and `LINERA_STORAGE`
@@ -151,25 +150,26 @@ A Byzantine-fault tolerant sidechain with low-latency finality and high throughp
151
150
*`--blob-download-timeout-ms <BLOB_DOWNLOAD_TIMEOUT>` — The delay when downloading a blob, after which we try a second validator, in milliseconds
152
151
153
152
Default value: `1000`
154
-
*`--max-concurrent-queries <MAX_CONCURRENT_QUERIES>` — The maximal number of simultaneous queries to the database
155
-
*`--max-stream-queries <MAX_STREAM_QUERIES>` — The maximal number of simultaneous stream queries to the database
153
+
*`--storage <STORAGE_CONFIG>` — Storage configuration for the blockchain history
154
+
*`--storage-max-concurrent-queries <STORAGE_MAX_CONCURRENT_QUERIES>` — The maximal number of simultaneous queries to the database
155
+
*`--storage-max-stream-queries <STORAGE_MAX_STREAM_QUERIES>` — The maximal number of simultaneous stream queries to the database
156
156
157
157
Default value: `10`
158
-
*`--max-cache-size <MAX_CACHE_SIZE>` — The maximal memory used in the storage cache
158
+
*`--storage-max-cache-size <STORAGE_MAX_CACHE_SIZE>` — The maximal memory used in the storage cache
159
159
160
160
Default value: `10000000`
161
-
*`--max-entry-size <MAX_ENTRY_SIZE>` — The maximal size of an entry in the storage cache
161
+
*`--storage-max-entry-size <STORAGE_MAX_ENTRY_SIZE>` — The maximal size of an entry in the storage cache
162
162
163
163
Default value: `1000000`
164
-
*`--max-cache-entries <MAX_CACHE_ENTRIES>` — The maximal number of entries in the storage cache
164
+
*`--storage-max-cache-entries <STORAGE_MAX_CACHE_ENTRIES>` — The maximal number of entries in the storage cache
165
165
166
166
Default value: `1000`
167
-
*`--wasm-runtime <WASM_RUNTIME>` — The WebAssembly runtime to use
168
-
*`--tokio-threads <TOKIO_THREADS>` — The number of Tokio worker threads to use
169
-
*`--tokio-blocking-threads <TOKIO_BLOCKING_THREADS>` — The number of Tokio blocking threads to use
170
167
*`--storage-replication-factor <STORAGE_REPLICATION_FACTOR>` — The replication factor for the keyspace
171
168
172
169
Default value: `1`
170
+
*`--wasm-runtime <WASM_RUNTIME>` — The WebAssembly runtime to use
171
+
*`--tokio-threads <TOKIO_THREADS>` — The number of Tokio worker threads to use
172
+
*`--tokio-blocking-threads <TOKIO_BLOCKING_THREADS>` — The number of Tokio blocking threads to use
0 commit comments