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
As part of the work on captive stellar-cores for faster horizon ingestion (eg. stellar/go#2322), stellar-core run command might need to be modified to operate in-memory only.
If so, it will also need a new flag indicating which ledger to "start from" -- passed from horizon indicating horizon's last-ingested ledger -- meaning "do an offline catchup to N, not emitting metadata, and then an online catchup from N, emitting metadata during replay".
If however we're not storing ledger state in memory for online captive cores, we can have horizon just run two commands when initiating a captive core: once to offline-catchup, and once to run.
The text was updated successfully, but these errors were encountered:
As part of the work on captive stellar-cores for faster horizon ingestion (eg. stellar/go#2322),
stellar-core run
command might need to be modified to operate in-memory only.If so, it will also need a new flag indicating which ledger to "start from" -- passed from horizon indicating horizon's last-ingested ledger -- meaning "do an offline catchup to N, not emitting metadata, and then an online catchup from N, emitting metadata during replay".
If however we're not storing ledger state in memory for online captive cores, we can have horizon just run two commands when initiating a captive core: once to offline-catchup, and once to run.
The text was updated successfully, but these errors were encountered: