Struct CalcAccountsHashConfig

pub struct CalcAccountsHashConfig<'a> {
    pub use_bg_thread_pool: bool,
    pub check_hash: bool,
    pub ancestors: Option<&'a Ancestors>,
    pub use_write_cache: bool,
    pub epoch_schedule: &'a EpochSchedule,
    pub rent_collector: &'a RentCollector,
    pub store_detailed_debug_info_on_failure: bool,
    pub full_snapshot: Option<FullSnapshotAccountsHashInfo>,
}

parameters to calculate accounts hash

Fields

use_bg_thread_pool: bool

true to use a thread pool dedicated to bg operations

check_hash: bool

verify every hash in append vec/write cache with a recalculated hash this option will be removed

ancestors: Option<&'a Ancestors>

‘ancestors’ is used to get storages and also used if ‘use_write_cache’ is true to get account data from the write cache

use_write_cache: bool

does hash calc need to consider account data that exists in the write cache? if so, ‘ancestors’ will be used for this purpose as well as storages.

epoch_schedule: &'a EpochSchedule

rent_collector: &'a RentCollector

store_detailed_debug_info_on_failure: bool

used for tracking down hash mismatches after the fact

full_snapshot: Option<FullSnapshotAccountsHashInfo>

Some if this is an incremental snapshot which only hashes slots since the base full snapshot

Implementations

impl<'a> CalcAccountsHashConfig<'a>

pub fn get_should_cache_hash_data() -> bool

return true if we should cache accounts hash intermediate data between calls

Trait Implementations

impl<'a> Debug for CalcAccountsHashConfig<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.