ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 03:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Online deletion edits per review

Browse Source 
- Cleaned up can_delete method fields, errors
- Changed commands to delete old db files in full history tutorial
- Clarified RocksDB w/ rotational disks
- Clarified how many ledgers may be stored w/ online deletion
This commit is contained in:
mDuo13
2019-01-14 15:43:46 -08:00
parent 4669665aba
commit 9d88381c89
4 changed files with 19 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md
View File

@@ -43,16 +43,15 @@ rippled can_delete 11320417
<!-- MULTICODE_BLOCK_END -->
The request includes the following optional parameter:
The request accepts the following parameter:
| `Field` | Type | Description |
|:-------------|:------------------|:------------------------------------------|
| `can_delete` | String or Integer | The [Ledger Index][] of the maximum ledger version to allow to be deleted. The special case `never` disables online deletion. The special case `always` enables automatic online deletion as if advisory deletion was disabled. The special case `now` allows online deletion one time at the next validated ledger that meets or exceeds the configured `online_delete` value. |
| `can_delete` | String or Integer | _(Optional)_ The [Ledger Index][] of the maximum ledger version to allow to be deleted. The special case `never` disables online deletion. The special case `always` enables automatic online deletion as if advisory deletion was disabled. The special case `now` allows online deletion one time at the next validated ledger that meets or exceeds the configured `online_delete` value. If omitted, the server makes no changes (but still replies with the current `can_delete` value). |
If no parameter is specified, no change is made.
### Response Format
The response follows the [standard format][], with
a successful result containing the following fields:
The response follows the [standard format][], with a successful result containing the following fields:
| `Field` | Type | Description |
|:-------------|:--------|:----------------------------------------------------|
@@ -62,11 +61,11 @@ Use this command with no parameter to query the existing `can_delete` setting.
### Possible Errors
* Any of the [universal error types][].
* `notEnabled` - Not enabled in configuration.
* `notReady` - Not ready to handle this request.
* `lgrNotFound` - Ledger not found.
* `invalidParams` - Invalid parameters.
- Any of the [universal error types][].
- `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
- `lgrNotFound` - The ledger specified by the `can_delete` field of the request does not exist, or it does exist but the server does not have it.
- `notEnabled` - If either online deletion or advisory deletion are not enabled in the server's configuration.
- `notReady` - The server is not ready to run online deletion at the moment. This usually means the server has just started up and has not yet acquired a validated ledger.
## See Also