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
against an indexer $AF_IDX_ADDRESS for TestNet.
(You may want to change the round to the current round.)
Note that this code does not make any parallel queries to the indexer, it waits for the previous query to end before making a new query. So this should almost create no load on the indexer and on the DB.
TestNet indexer does not seem to crash. MainNet indexer does.
Setup
algorand-indexer version:
$ algorand-indexer -v
2.5.0 compiled at 2021-06-22T18:26:33+0000 from git hash 1f3fb466681dc0f025be504576e4632b83130e27 (modified)
OS: macOS BigSur 11.4
Version 2.3.4 of indexer did not have this issue.
Urgency/Relative Priority
Relatively urgent: Allows crashes of the indexer with very low load
The text was updated successfully, but these errors were encountered:
fabrice102
changed the title
Indexer triggers DB error "" when doing too many sequential queries (no parallel queries)
Indexer triggers DB error "FATAL: sorry, too many clients already" when doing too many sequential queries (no parallel queries)
Jun 28, 2021
Summary
Querying accounts with a previous round even sequentially make the DB display the following error:
and then a long list of
The indexer returns the message:
(error 500)
and sometimes completely crashes.
To try, run:
against an indexer
$AF_IDX_ADDRESS
for TestNet.(You may want to change the round to the current round.)
Note that this code does not make any parallel queries to the indexer, it waits for the previous query to end before making a new query. So this should almost create no load on the indexer and on the DB.
TestNet indexer does not seem to crash. MainNet indexer does.
Setup
$ algorand-indexer -v 2.5.0 compiled at 2021-06-22T18:26:33+0000 from git hash 1f3fb466681dc0f025be504576e4632b83130e27 (modified)
Version 2.3.4 of indexer did not have this issue.
Urgency/Relative Priority
Relatively urgent: Allows crashes of the indexer with very low load
The text was updated successfully, but these errors were encountered: