up the example default delete to 30,000 as lower values have shown issues in production

content/infrastructure/configuration/data-retention/configure-advisory-deletion.md

@@ -42,7 +42,7 @@ To configure advisory deletion with a daily schedule, perform the following step
 
         [node_db]
         # Other settings unchanged ...
-      	online_delete=2000
+      	online_delete=300000
       	advisory_delete=1
 
     - Set `advisory_delete` to `1` to run online deletion only when prompted. (Set it to `0` to run online deletion automatically as new ledger versions become available.)

content/infrastructure/configuration/data-retention/configure-full-history.md

@@ -35,7 +35,7 @@ To configure your server to acquire and store full history, complete the followi
         [node_db]
       	type=NuDB
       	path=/var/lib/rippled/db/nudb
-      	#online_delete=2000
+      	#online_delete=300000
       	#advisory_delete=0
 
     On a full-history server, you should use NuDB for the ledger store, because RocksDB requires too much RAM when the database is that large. For more information, see [Capacity Planning](capacity-planning.html). You can remove the following performance-related configuration options from the default `[node_db]` stanza, because they only apply to RocksDB: `open_files`, `filter_bits`, `cache_mb`, `file_size_mb`, and `file_size_mult.`

content/infrastructure/configuration/data-retention/configure-online-deletion.md

@@ -37,7 +37,7 @@ To change the amount of history your server stores, perform the following steps:
 
         [node_db]
         # Other settings unchanged ...
-      	online_delete=2000
+      	online_delete=300000
       	advisory_delete=0
 
     Set `online_delete` to the minimum number of ledger versions to keep after running online deletion. With automatic deletion (the default), the server typically runs deletion when it has accumulated about twice this many ledger versions.