-
Notifications
You must be signed in to change notification settings - Fork 7
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
Make W3S JAVA OPTs configurable via advanced editor #76
Conversation
bump workflow checkout to v3 and add workflow dispatch
the last commit here 787014d was not intended to merge into this PR, it was merged on my package to generate a release on my CI but i forgot that it would edit this PR as well since its a PR from my master branch not a new branch as I did with every other PR. IDK if i should revert it or just close this PR and open a new PR without from a new branch, so any other edits i make trying to tweak this build dont accidentally get pulled into this PR as well. Converting to a Draft now since ive been having so much trouble getting a non officially signed DNP installed so far and this PR got jumbled by pulling changes from my master branch in another repo. but this remains high priority. |
UPDATE: build resolved itself, same hash was installed without incident but still had same issues even doubling the Max heap size to 8g from 4g. was going to give up but just tested no minimum heap size and a 10g max. all working as soon as I finished. Definitely need to make this a confgurable field as some power users running lots of keys may run into similar issues, but it appears unless this upstream was supposed to need more than double the max heap size as the previous version for the same amount of validators, there's something else wrong, perhaps a memory leak somwhere but regardless I was able to resolve this issue for me with this PR and JAVA_OPTS set to |
bumping max heap size to 10g testing with lower values, 6g, 8g no improvement but when i made the max 10 and removed the low end everything started working for me again.
/ipfs/QmUK42NVuP4tVT6UbpNK1WnyYJeiNZ3eL1wM67QvdvMSmd |
Ever since the release of v1.0.8 The W3S no longer works for many users (likely those running higher numbers of validators) and the error appears to be related to OOM issues due to the JAVA OPTs being hardcoded in this package. In every other Java based package, Besu, Teku and all their forks for networks all have a separate field in the Advanced Config for Java OPTS.
Best solution for this appears to be making the JAVA opts configurable from the UI, and not have the values hardcoded in the docker file.
Due to the many reports of others with this issue on other networks than gnosis, i moved the upper limit of the max heap size to 10g from 4g and removed the lower limit to make it work. Before that i tested with 6g max. then 8g max then 8g max and a 1g min, same issues failing at same spots. felt like it was something else but then as a hail mary i tried to just throw 10g at it and remove the lower limit and now Ive got no issues running 93 keys Open to suggestions on what the upper limit should be but clearly 4g is not high enough given the current feedback and error reports and it appears theres a deeper issue as this upstream version shouldnt require more than double the max heap size to run the same amount of keys as the previous version did. Anyways this fix works and this param should be made editable in all signers. (PRs are already open)
Errors detailed below: