-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Failed to process FETCH_INV_DATA message #5439
Comments
@wubin01 Do you have identified the cause of the problem? If so, could you please explain it in detail? |
@chengtx01 A broadcast list timeout threshold can be set. If the peer broadcast list exceeds a certain threshold, no more transactions will be obtained from it. |
Do you have a detailed solution? If so, can you add it in the body of the text? |
@lvs007 If the list broadcast by the peer exceeds 15s, no longer get it.
The logic after repair is as follows:
|
System information
Java-tron version: v4.7.2
OS & Version: Linux & macOS
Expected behavior
The FETCH_INV_DATA message from the peer should be successfully processed.
Actual behavior
When processing the FETCH_INV_DATA message, it was found that the transaction hash requested by the Peer was not in the broadcast list cache of the Peer, so a not spread inv exception was reported.
The log is as follows:
Is Peer a normal node?
The node interaction process was normal. It took 449s from establishment to disconnection. The log is as follows.
Is the transaction normal?
The transaction
1ec914af1d51a99ddb628a7e154dd0bf603ce8c6c9d81b68c1773b67130f85be
requested by Peer was a normal transaction, the transaction had been packaged in the block at 10:20:12, and the time requested by Peer was 10:22:29, which was delayed by 2 minutes and 15 seconds.The text was updated successfully, but these errors were encountered: