-
Notifications
You must be signed in to change notification settings - Fork 0
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
Transaction stuck on IsBroadcast
using fork-aware pool
#174
Comments
This will help with debugging #175 |
I reviewed a log. The situation there actually looks like one where transaction events are stuck. Actually the Here is the excerpt from the log, and also explanation why it happend
The transaction is included in the view (for block number 46053):
At this point the parachain starts a heavy re-org, which takes ~1 minute. During this period no
Once this re-org is done, transaction is included, but the listener is already disconnected:
After some more blocks tx is finalized:
I had an implemetnation where txpool is processing all the blocks (not only best or finalized) - see this commit. If the requirement is to have immediate If occasional delays in Please let me know if above analysis makes sense for the case you observed. Especially I'd like to confirm the period of time after which you concluded the event as stuck. |
This sounds like the problem to me? Did the listener disconnect on its own? If yes, this is the problem. |
From the discussion on element, I understood the listener was terminated by the client. Quoting element:
|
Confirming the period of time after the events were concluded as stuck is important. Was it ~1 minute or more? |
By client you mean the rpc client? |
Yes |
@valentinfernandez1 @gautamdhameja this would be really good to know. Otherwise we can just guess. |
paritytech/polkadot-sdk#1202 (comment) as said here. I would just send We need at least something to report that the block is not part of the best chain anymore. The new json-rpc-spec handles it this way. However, even there I would like to switch it to just report |
Mythical team has been testing the fork-aware transaction pool on Rococo Muse and have encountered an error while using the
submitAndWatch
rpc method.Issue is the following:
Ready
->Broadcast
->InBlock
-> Finalized (Occationally it can get a retracted but that is expected if there is a fork).Ready
->Broadcast
. And no new updates are received after theBroadcast
status, even though the transaction did get included in a finalized block.The text was updated successfully, but these errors were encountered: