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

Add support for simulated mining #1

Open
larskuhtz opened this issue Nov 4, 2021 · 0 comments
Open

Add support for simulated mining #1

larskuhtz opened this issue Nov 4, 2021 · 0 comments

Comments

@larskuhtz
Copy link
Collaborator

The current devnet setup uses in-node mining. In node mining has the advantage that it is easy to scale the number of mining nodes by increasing the replica count.

Simulated mining requires the use of chainweb-mining-client. Chainweb-web-mining clients must be mapped to a single chainweb-node. The internal service routing of the docker compose network probably doesn't guarantee sticky application level sessions. If a service container "knows" its replica number, it could be used to assign it to a unique mining node. Alternatively, we could use the the replica count of the mining nodes to randomly assign mining-client to a unique node by hashing some unique identifier (e.g. the internal IP address) of the client.

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

1 participant