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

Yacy Crashed 3 times for no real reason. found 3 hs_err_pid log files #646

Open
smokingwheels opened this issue May 26, 2024 · 2 comments
Open
Labels
bug Indicates an unexpected problem or unintended behavior question Indicates that an issue, pull request, or discussion needs more information

Comments

@smokingwheels
Copy link

Yacy Crashed 3 times for no real reason a few weeks ago now.
There is 3 hs_err_pid log files in the yacy folder.
No it is not running out of memory.
3 log files
http://cloudparty.evils.in/index.php/s/yDw49ajTPnzzgJp

See issue for my flavor of java.
corretto/corretto-21#63

Is this setting too big in the java args?
-XX:ReservedCodeCacheSize=32m

Testing the setting.
Before: the JAVA load was going up to 2000 %. The system load was 54 in 24 core system when searching a 5 Hz. Power consumption = 317 watts.
With 2 yacys running from memory the CPU load was always 7-8 on the status pages.

After: the code cache size with 2 yacys running the load 4.57, 4.58, 4.38 power consumption 180.00 Watts
System load 6.45, 5.74, 5.12 when load testing at ~5 Hz

@okybaca okybaca added bug Indicates an unexpected problem or unintended behavior question Indicates that an issue, pull request, or discussion needs more information labels May 28, 2024
@okybaca
Copy link
Contributor

okybaca commented May 28, 2024

It's a little unclear for me.
Did YaCy crash with the setting, you described later, or without that?

@smokingwheels
Copy link
Author

I've added this setting to /etc/sysctl.conf
vm.max_map_count = 262144
See how it goes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior question Indicates that an issue, pull request, or discussion needs more information
Projects
None yet
Development

No branches or pull requests

2 participants