-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] Bluebox disseminating same block to compact to multiple machines #17773
Comments
Ya I bet it just broadcasts it out. Let us see if there is a way to make it work better when you are running a cluster. Thanks for being a blueboxer! |
2024-03-27T17:10:05.532 full_node chia.full_node.full_node: INFO Replaced compact proof at height 3562487 Found another one from a quick look through so it must be uncommon. Just to put this into context my main node is not overly powerful and my main machines are windows so i run virtual box ubuntu compute timelord from windows as and when. It saves time and space then running separate nodes and having to wait for syncing. I don't really have threadripper or other really high core count cpu but i am willing to bet it could do the same with them. pre asic timelord this might been a non issue tbh but understand if you leave this if its too much work. |
What happened?
As per title when running a bluebox-timelord in cluster mode, bluebox disseminates same blocks to compact to multiple machines, I have found one proof of this which i added in log output.
I have target_uncompact_proofs: 100 and send_uncompact_interval 300 which is more then enough work because i am averaging 30 proofs a hour with 3 machines currently due to high compute(asic timelords).
Version
2.21
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
The text was updated successfully, but these errors were encountered: