[ https://issues.apache.org/jira/browse/SOLR-17585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christos Malliaridis updated SOLR-17585: ---------------------------------------- Description: We are facing again issues similar to SOLR-16103 where we run out of CodeCache space. However, this may be caused in a different context now. One assumption is that updating the CodeCache in our gradle.properties (template.gradle.properties) may fix the issue. Setting the jvm argument {{-XX:ReservedCodeCacheSize=120m}} may fix the issue, but it would be best to identify the cause, if possible. One occurence of this issue is in [https://github.com/apache/solr/actions/runs/12073580646/job/33669959917] (probably not the best job/commit to use for reproducing the issue). was: We are facing again issues similar to SOLR-16103 where CodeCache becomes full. However, this may be caused in a different context now. One assumption is that updating the CodeCache in our gradle.properties (template.gradle.properties) may fix the issue. Setting the jvm argument {{-XX:ReservedCodeCacheSize=120m}} may fix the issue, but it would be best to identify the cause, if possible. One occurence of this issue is in [https://github.com/apache/solr/actions/runs/12073580646/job/33669959917] (probably not the best job/commit to use for reproducing the issue). > CodeCache full during Gradle builds > ----------------------------------- > > Key: SOLR-17585 > URL: https://issues.apache.org/jira/browse/SOLR-17585 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Gradle > Reporter: Christos Malliaridis > Priority: Major > > We are facing again issues similar to SOLR-16103 where we run out of > CodeCache space. However, this may be caused in a different context now. > One assumption is that updating the CodeCache in our gradle.properties > (template.gradle.properties) may fix the issue. Setting the jvm argument > {{-XX:ReservedCodeCacheSize=120m}} may fix the issue, but it would be best to > identify the cause, if possible. > One occurence of this issue is in > [https://github.com/apache/solr/actions/runs/12073580646/job/33669959917] > (probably not the best job/commit to use for reproducing the issue). -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org