Skip to content

fix(iisa): report IISA refusing a request apart from an outage - #761

Draft
MoonBoi9001 wants to merge 2 commits into
mb9/refuse-unusable-per-chain-price-capsfrom
mb9/report-iisa-rejections-distinctly
Draft

MoonBoi9001 wants to merge 2 commits into
mb9/refuse-unusable-per-chain-price-capsfrom
mb9/report-iisa-rejections-distinctly

Conversation

@MoonBoi9001

Copy link
Copy Markdown
Member

When IISA answers with a 4xx, dipper now logs the status and IISA's reply and calls the request refused, where it used to report IISA as unavailable with no reason given. The job still retries every 60 seconds, since a refusal is usually fixed by a deploy, and the outage breaker's log now names the chain whose pool lookup failed.

When IISA refused a request with a 4xx, dipper logged only the status and blamed an IISA outage.
It now logs the status and IISA's reply and says the request was refused, still retrying the job
every 60 seconds, since a deploy (new config, token or version) usually fixes a refusal.
The outage breaker asks IISA for each chain's pool of indexers, and when that lookup failed its
log did not say which chain, so a refusal tied to one chain's settings was hard to trace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant