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 revisions

Browse Source 
- Split ledger history section into a parent concept page w/ online
deletion and history sharding as child pages
- Clarified how much data is stored in general
- Covered the special case for backfilling with advisory_delete enabled
(including updating the diagram)
- Changed full history recommendation to NuDB only
This commit is contained in:
mDuo13
2018-12-18 14:21:51 -08:00
parent ab6b4d4435
commit a3400378c4
11 changed files with 317 additions and 166 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,7 +1,7 @@
# can_delete
[[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source")
With `online_delete` and `advisory_delete` configuration options enabled, the `can_delete` method informs the rippled server of the latest ledger which may be deleted.
The `can_delete` method informs the `rippled` server of the latest ledger version which may be deleted when using [online deletion with advisory deletion enabled](online-deletion.html#advisory-deletion). If advisory deletion is not enabled, this method does nothing.
_The `can_delete` method is an [admin method](admin-rippled-methods.html) that cannot be run by unprivileged users._
@@ -47,7 +47,7 @@ The request includes the following optional parameter:
| `Field` | Type | Description |
|:-------------|:------------------|:------------------------------------------|
| `can_delete` | String or Integer | The maximum ledger to allow to be deleted. For `ledger_index` or `ledger_hash`, see [Specifying Ledgers][]. `never` sets the value to 0, and effectively disables online deletion until another `can_delete` is appropriately called. `always` sets the value to the maximum possible ledger (4294967295), and online deletion occurs as of each configured `online_delete` interval. `now` triggers online deletion at the next validated ledger that meets or exceeds the configured `online_delete` interval, but no further. |
| `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. |
If no parameter is specified, no change is made.
@@ -68,6 +68,11 @@ Use this command with no parameter to query the existing `can_delete` setting.
* `lgrNotFound` - Ledger not found.
* `invalidParams` - Invalid parameters.
## See Also
- [Online Deletion](online-deletion.html)
- [Configure Advisory Deletion](configure-advisory-deletion.html)
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}