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
When you have a lot of receipts for older allocations that were already being closed, once it starts an allocation, it sends a SenderAccountMessage::UpdateReceiptFees to let the sender account know about the updated value.
As soon as it gets the message, it verifies that the count is bigger than the limit, and triggers a rav request for that specific allocation. While trying to send a request to the allocation, it was already closed, and no allocation actor was found, giving this message
ERROR indexer_tap_agent::agent::sender_account: There was an error while requesting a RAV., error: Error while getting allocation actor 0x....
Solution
We have a flag called "blocked_allocation" which is added when sender account closes an allocation.
If the allocation is blocked (closing), we shouldn't trigger an allocation for counter_greater_receipt_limit.
The text was updated successfully, but these errors were encountered:
Problem
When you have a lot of receipts for older allocations that were already being closed, once it starts an allocation, it sends a
SenderAccountMessage::UpdateReceiptFees
to let the sender account know about the updated value.As soon as it gets the message, it verifies that the count is bigger than the limit, and triggers a rav request for that specific allocation. While trying to send a request to the allocation, it was already closed, and no allocation actor was found, giving this message
Solution
We have a flag called "blocked_allocation" which is added when sender account closes an allocation.
If the allocation is blocked (closing), we shouldn't trigger an allocation for
counter_greater_receipt_limit
.The text was updated successfully, but these errors were encountered: