-
Notifications
You must be signed in to change notification settings - Fork 226
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
increase tendermint_p2p::secret_connection::DATA_MAX_SIZE #1356
Comments
Perhaps we could raise I'm not sure how it was originally chosen, but it's not like the systems we're running it on are hurting for memory. |
Following up on iqlusioninc/tmkms#729 (comment) Simply bumping the But TCP connection gets interrupted at tendermint-rs/p2p/src/secret_connection.rs Line 486 in bcc0b37
with
On the node's side
To overwrite the tmkms deps, I used [patch.crates-io]
tendermint = { git = "https://github.com/qezz/tendermint-rs", tag = "v0.34.0-tcp-conn-patch.4", package = "tendermint", features = ["secp256k1"] }
tendermint-config = { git = "https://github.com/qezz/tendermint-rs", tag = "v0.34.0-tcp-conn-patch.4", package = "tendermint-config" }
tendermint-p2p = { git = "https://github.com/qezz/tendermint-rs", tag = "v0.34.0-tcp-conn-patch.4", package = "tendermint-p2p" }
tendermint-proto = { git = "https://github.com/qezz/tendermint-rs", tag = "v0.34.0-tcp-conn-patch.4", package = "tendermint-proto" } tried these values pub const DATA_MAX_SIZE: usize = 10240;
pub const DATA_MAX_SIZE: usize = 1024000;
pub const DATA_MAX_SIZE: usize = 65536; I didn't have a chance to look deeper, unfortunately |
This seems to be some sort of bug in the It's certainly not helped by the API: where Secret Connection is a message-oriented protocol, |
Let's try with #1393 and re-consider if that does not help. This proposal looks like suppressing the symptom to me. |
shall we try the new version on a testnet? |
What went wrong?
Link to the issue: iqlusioninc/tmkms#729 (comment)
TMKMS (signer) use:
to define the buffer size for incoming (signing / privval) requests. It happened that SEI network pushes the block proposals that are up to 6 times bigger than 1024 bytes (current value of
DATA_MAX_SIZE
) and that makes the tmkms to fail@tony-iqlusion suggested this might be the issue of tendermint-p2p. I would like to understand if the value should be bumped, or maybe tmkms uses it incorrectly?
Steps to reproduce
tendermint_p2p::secret_connection::DATA_MAX_SIZE
)Definition of "done"
either the DATA_MAX_SIZE is bumped or there is a clear explanation of how and where things should be defined
The text was updated successfully, but these errors were encountered: