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
The first case includes a duration field which measures the total time to ingest the ledger through all the processors.
The second case also includes a duration field, however, that field only measures the time to run the transaction processors.
We should only be logging the first case during resume state ingestion. This bug was introduced in #5117
In 2.27.0 we never logged the "Processed Ledger" message in processor runner:
The "Processed Ledger" message was logged only in fsm during the resume state and the other states which only reingested history. We should fix this bug and ensure that "Processed Ledger" is only logged once per ledger in every state of the fsm (resume, reingest history, etc)
The text was updated successfully, but these errors were encountered:
In the release-horizon-v2.28.0 branch, the "Processed Ledger" message is logged twice whenever a ledger is ingested in the resume state:
The first case includes a duration field which measures the total time to ingest the ledger through all the processors.
The second case also includes a duration field, however, that field only measures the time to run the transaction processors.
We should only be logging the first case during resume state ingestion. This bug was introduced in #5117
In 2.27.0 we never logged the "Processed Ledger" message in processor runner:
https://github.com/stellar/go/blob/release-horizon-v2.27.0/services/horizon/internal/ingest/processor_runner.go
The "Processed Ledger" message was logged only in fsm during the resume state and the other states which only reingested history. We should fix this bug and ensure that "Processed Ledger" is only logged once per ledger in every state of the fsm (resume, reingest history, etc)
The text was updated successfully, but these errors were encountered: