-
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
Node add isn't consistently working #728
Comments
Also tried doing the same flow with the C++ SDK NodeCreateTransaction followed by
|
We discovered there is currently an issue in platform/services with NodeCreateTransaction. After the node has been added and the one of the nodes goes into teach mode for the newly added node, the teacher will get JVM out of memory errors after finishing teaching and reconnecting to the network. I'm not sure the exact amount, but Nathan quoted 22GB of memory (not sure what this 22GB refers to). I think you might be able to get around this by setting the JVM memory settings really high, but we haven't configured Solo to do that by default. We have disabled our E2E tests involving |
To Reproduce
Initialisation steps from #727 and:
Describe the bug
I've seen fails with the error from #727 as well.
Describe the expected behavior
Node added and functioning. Does not happen every time but still it is not consistent for testing from our side.
Whole JUnit/CLI Logs
Additional Context
No response
The text was updated successfully, but these errors were encountered: