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
seems to be so heavy that I get a RPC-CORE: queryStorageAt(keys: Vec<StorageKey>, at?: BlockHash): Vec<StorageChangeSet>:: -32999: RPC rate limit exceeded error message when I'm connected to a public endpoint. Kusama node (v1.13.0).
If I set withClaimedRewardsEras: false it works on a Kusama public endpoint (i.e. wss://kusama-rpc.polkadot.io/), but of course I'm missing info
I can get past to this issue when I'm connected to my internal node, withClaimedRewardsEras: true, but still it takes roughly 13 seconds for 1 address
Polkadot doesn't seem to have the same issue: I can make the query with withClaimedRewardsEras: true set on internal and public endpoints with no problems
Not sure that's expected, so I'm opening this issue...
The text was updated successfully, but these errors were encountered:
ironoa
added a commit
to w3f/polkadot-k8s-payouts
that referenced
this issue
Jun 28, 2024
seems to be so heavy that I get a RPC-CORE: queryStorageAt(keys: Vec, at?: BlockHash): Vec:: -32999: RPC rate limit exceeded error message when I'm connected to a public endpoint. Kusama node (v1.13.0).
As you mentioned I would imagine this is directly related to the public node you are connected to. For all the heavy calls we are using entries to get everything at once so there is no limit hit. Have you tried with other Kusama public nodes?
related to #5859
seems to be so heavy that I get a
RPC-CORE: queryStorageAt(keys: Vec<StorageKey>, at?: BlockHash): Vec<StorageChangeSet>:: -32999: RPC rate limit exceeded
error message when I'm connected to a public endpoint. Kusama node (v1.13.0).withClaimedRewardsEras: false
it works on a Kusama public endpoint (i.e. wss://kusama-rpc.polkadot.io/), but of course I'm missing infowithClaimedRewardsEras: true
, but still it takes roughly 13 seconds for 1 addresswithClaimedRewardsEras: true
set on internal and public endpoints with no problemsNot sure that's expected, so I'm opening this issue...
The text was updated successfully, but these errors were encountered: