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
Currently, BucketListDB is enabled and running by default in captive-core, but is still disabled by default in validators. While BucketListDB has been running without issue in captive-core, we are holding off on enabling BucketListDB until after Soroban launch on mainnet. BucketListDB has only run on Stellar Classic in production captive-core instances and we want to wait and make sure it works well on Soroban entries before enabling it by default. We will watch how captive-core handles Soroban and enable it after launch.
Currently, captive-core supports persisting indexes on disk, but validators do not. This is due to a bug found during development where loading a persistent index resulted in a corrupted index, causing the DB to load data incorrectly. Because of this issue, validators do not persist indexes. Before enabling BucketListDB for validators, we should resolve #3677 and add safety checks so that validators can persist indexes. After resolving this issue and seeing how captive-core handles Soroban, we should enable BucketListDB.
This is not a pressing issue for now since network performance is not disk bound, but is more of a future-proofing measure and a helpful startup performance increase.
The content you are editing has changed. Please copy your edits and refresh the page.
Currently, BucketListDB is enabled and running by default in
captive-core
, but is still disabled by default in validators. While BucketListDB has been running without issue incaptive-core
, we are holding off on enabling BucketListDB until after Soroban launch on mainnet. BucketListDB has only run on Stellar Classic in productioncaptive-core
instances and we want to wait and make sure it works well on Soroban entries before enabling it by default. We will watch howcaptive-core
handles Soroban and enable it after launch.Currently,
captive-core
supports persisting indexes on disk, but validators do not. This is due to a bug found during development where loading a persistent index resulted in a corrupted index, causing the DB to load data incorrectly. Because of this issue, validators do not persist indexes. Before enabling BucketListDB for validators, we should resolve #3677 and add safety checks so that validators can persist indexes. After resolving this issue and seeing howcaptive-core
handles Soroban, we should enable BucketListDB.This is not a pressing issue for now since network performance is not disk bound, but is more of a future-proofing measure and a helpful startup performance increase.
Tasks
The text was updated successfully, but these errors were encountered: