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

bench client submit tx occur error "EOF" #550

Open
609127400 opened this issue Feb 14, 2025 · 3 comments
Open

bench client submit tx occur error "EOF" #550

609127400 opened this issue Feb 14, 2025 · 3 comments

Comments

@609127400
Copy link

I am run benchmark with deployment/*.yaml,i have deployed 3 nodes with id 0/1/2.
then i wanna use bench client to send tx to mir nodes(compile src code in cmd/bench)

i play cmd:
../bin/bench client -i 0 -m ./membership.json -T 1m -v

then logs shows:
Connecting to node: 10.0.5.214:10000
Node connected. id=2 addr=10.0.5.214:10000
Submitting transaction #0
Submitting transaction #1
Could not close gRPC client 2
Error: failed sending transaction to nodes: [2] first error: EOF

I tried many times, all come out to that.

it seems like the bench client can only submit one tx then close the connection with mir node, next submit will failed becase the connection is already closed, is it right?

@matejpavlovic
Copy link
Contributor

Unfortunately, the bench client might be outdated and transactions can currently only be generated by the TxGen module from within the nodes. The code would probably need to be adapted to support external clients again.

@609127400
Copy link
Author

What I got from your response is:

When I runned benchmark with *.yaml and *.sh in deployment dir, especially deployment/scripts/run-new.sh, there is already used TxGen to send transactions to the Mir consensus network, and no need to additionally run cmd/bench/client to send transactions.

Is that right?

by the way, the reason I previously used cmd/bench/client was because I saw a throughput value of 0.4 in the benchmark results, and I suspected that I might not have actually sent any transactions to the consensus network.

@matejpavlovic
Copy link
Contributor

Yes, that is right.
To adjust the load, the TxGen.NumClients option needs to be used, which configures to number of transaction-producing threads at each node's local transaction generator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants