Module solana_ledger::blockstore

The blockstore module provides functions for parallel verification of the Proof of History ledger as well as iterative read, append write, and random access read to a persistent file-based ledger…..

Re-exports

• pub use crate::blockstore_db::BlockstoreError;
• pub use crate::blockstore_meta::OptimisticSlotMetaVersioned;
• pub use crate::blockstore_meta::SlotMeta;
• pub use crate::blockstore_metrics::BlockstoreInsertionMetrics;
• pub use blockstore_purge::PurgeType;

Modules

• RocksProperties
  Properties
• blockstore_purge

Structs

• Blockstore
• BlockstoreSignals
• CompletedDataSetInfo
  A “complete data set” is a range of Shreds that combined in sequence carry a single serialized Vec<Entry>.
• IndexMetaWorkingSetEntry
• PAR_THREAD_POOL 🔒
• PAR_THREAD_POOL_ALL_CPUS 🔒
• SignatureInfosForAddress
• SlotMetaWorkingSetEntry
  The in-memory data structure for updating entries in the column family cf::SlotMeta.

Enums

• InsertDataShredError

Constants

• MAX_COMPLETED_SLOTS_IN_CHANNEL
• MAX_DATA_SHREDS_PER_SLOT
• MAX_REPLAY_WAKE_UP_SIGNALS

Functions

• __stability 🔒
• __stability 🔒
• __static_ref_initialize 🔒
• __static_ref_initialize 🔒
• adjust_ulimit_nofile 🔒
• chain_new_slot_to_prev_slot 🔒
• commit_slot_meta_working_set 🔒
  For each slot in the slot_meta_working_set which has any change, include corresponding updates to cf::SlotMeta via the specified write_batch. The write_batch will later be atomically committed to the blockstore.
• create_new_ledger
• create_new_ledger_from_name
• create_new_ledger_from_name_auto_delete
• entries_to_test_shreds
• find_slot_meta_else_create 🔒
  Returns the SlotMeta with the specified slot_index. The resulting SlotMeta could be either from the cache or from the DB. Specifically, the function:
• find_slot_meta_in_cached_state 🔒
  Returns the SlotMeta of the specified slot from the two cached states: working_set and chained_slots. If both contain the SlotMeta, then the latest one from the working_set will be returned.
• find_slot_meta_in_db_else_create 🔒
  A helper function to find_slot_meta_else_create that searches the SlotMeta based on the specified slot in db and updates insert_map.
• get_index_meta_entry 🔒
• get_last_hash 🔒
• get_ledger_path_from_name
• get_ledger_path_from_name_auto_delete
• get_slot_meta_entry 🔒
  Obtain the SlotMeta from the in-memory slot_meta_working_set or load it from the database if it does not exist in slot_meta_working_set.
• handle_chaining 🔒
  For each entry in working_set whose did_insert_occur is true, this function handles its chaining effect by updating the SlotMeta of both the slot and its parent slot to reflect the slot descends from the parent slot. In addition, when a slot is newly connected, it also checks whether any of its direct and indirect children slots are connected or not.
• handle_chaining_for_slot 🔒
  A helper function of handle_chaining which handles the chaining based on the SlotMetaWorkingSetEntry of the specified slot. Specifically, it handles the following two things:
• is_newly_completed_slot 🔒
• is_orphan 🔒
• make_chaining_slot_entries
• make_many_slot_entries
• make_many_slot_shreds
• make_slot_entries
• send_signals 🔒
• slot_has_updates 🔒
  Returns a boolean indicating whether a slot has received additional shreds that can be replayed since the previous update to the slot’s SlotMeta.
• test_all_empty_or_min
• traverse_children_mut 🔒
  Traverse all the children (direct and indirect) of slot_meta, and apply slot_function to each of the children (but not slot_meta).
• update_completed_data_indexes 🔒
• update_slot_meta 🔒
• verify_shred_slots 🔒

Type Definitions

• CompletedRanges 🔒
• CompletedSlotsReceiver
• CompletedSlotsSender