-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add simulation that probes mempool #24
base: main
Are you sure you want to change the base?
Conversation
@emmanueldenloye I'm getting the following error when I try to run
The same for |
git checkout main flake.lock nix flake lock --update-input txg nix flake lock --update-input chainweb-peers
72f09d2
to
7135f78
Compare
Take out unnecessary sleep commands Make txg behave more robustly when creating ES indexes
I've posted two curl commands demonstrating that the elasticesarch indexes holding tx data from the simulation both exist and have data in them. The first index polled is (
(
|
I'm posting this here for posterity. The problem is in the flake.lock file. The way to reproduce the error without using nix (in other words, to make sure the flake.lock is valid), you can use the following command:
|
This PR sets out to create a simulation of chainweb-node that observes changes to the list of pending transactions in a node's mempool. Doing this requires that we add these components to the simulation.
chainweb-peers
. The first discovers nodes in the simulation and the second pings for the list of pending transactions in each of these nodes mempool and reports the relevant data to the elasticsearch backend.This is the first part of a larger effort to create a testbed for diagnosing/understanding chainweb-node at the network level.
Here are things that seem to be brittle and work temperamentally :
The chainweb-peers executable seems to not be able to reliably successfully ping the CUT endpoint of chainweb-node. As such, once this problem is addressed, we should get rid of the cut-checker.nix file.
The dependency of each process in process-compose setup for the
chainweb-peers
is not well defined. It shouldn't need to take so long for the servicestxg
andshow-es-output
to start and produce sound output.