Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IMA: Message processing time can be slow down in case unstable network #75

Open
EvgeniyZZ opened this issue Jan 30, 2024 · 0 comments
Open
Labels
bug Something isn't working known issue

Comments

@EvgeniyZZ
Copy link

EvgeniyZZ commented Jan 30, 2024

Description
Message processing between schains can be slow down for a while in case unstable network OR network connection
Version: 2.1.0-beta.2
Skaled: any

Steps to reproduce

  • Turn off 1-5 skaled core containers
  • Observe logs of IMA Agent

Actual result
In case of unstable network IMA Agent may stuck for some period of time after unsuccessful getIncomingMessagesCounter() call
from two minutes up to 7, depends on amount of connected chains.

Expected result
Add expected result.
Logs
For grep use: transfer loop from skale-welcome-that-diphda to skale-swift-quixotic-marfic, S2S
imaS2S_stuck.txt
imaLog.txt

@DmytroNazarenko

2024-1-30 16:13:43.243: S2S/#17 transfer loop from skale-welcome-that-diphda to skale-swift-quixotic-marfic: Using externally provided signing function
2024-1-30 16:13:43.243: S2S/#17 transfer loop from skale-welcome-that-diphda to skale-swift-quixotic-marfic: Will call src-chain.MessageProxy.getOutgoingMessagesCounter()...
2024-1-30 16:21:22.445: S2S/#17 transfer loop from skale-welcome-that-diphda to skale-swift-quixotic-marfic: Will call dst-chain.MessageProxy.getIncomingMessagesCounter()...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working known issue
Projects
Status: No status
Development

No branches or pull requests

4 participants