[jira] [Commented] (SOLR-16634) "gradlew check" fails with OOM on fresh clone

["Kevin Risden (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680012#comment-17680012 ] 

Kevin Risden commented on SOLR-16634:
-------------------------------------

[~ichattopadhyaya] go ahead and take my comment out of context. Since you are apparently in capable of reading the logs that you have posted twice now.

My comment is specifically about you REMOVING gradle.properties and ignoring the advice in the output that you said you couldn't find.

{quote}There is no such message. I am not sure if you're even reading the same things as I am. I regret the time you wasted.{quote}

I guess you haven't read what you have posted multiple times. I mean it starts with "IMPORTANT" but why read that?

{code:java}
> Task :localSettings

IMPORTANT. This is the first time you ran the build. I wrote some sane defaults (for this machine) to 'gradle.properties', they will be picked up on consecutive gradle invocations (not this one).

Run gradlew :helpLocalSettings for more information.
{code}

Now if you actually read that it explains why and what happens. 

I'll save you the trouble for actually running that command to see since it just prints out this: https://github.com/apache/solr/blob/main/help/localSettings.txt

So yes what you are running into in the description is user error - deleting or not having gradle.properties generated is 100% user error as what you are running into is EXPECTED if you don't follow the build guidelines laid out.

After a bunch of other comments and finally following the build you did end up with:

{code:java}
* What went wrong:
Execution failed for task ':solr:core:forbiddenApisMain'.
> GC overhead limit exceeded
{code}

This is unexpected (and not something I've seen before). Again the localSettings help explains that you MIGHT have to tweak gradle.properties based on your hardware. If you followed that recommendation you might have looked at gradle.properties and seen if maybe the 1G is too low on your hardware. It might be worth looking at raising the 1G in gradle.properties but without knowing why your machine is doing what it is doing. It wouldn't make sense to globally make that change.

Again this is all laid out in the localSettings output that you haven't read, but instead of actually following the advice of others - you resorted in personal attacks and comments that aren't helpful on SOLR-15616. Please stop the personal attacks and actually read what others are sharing when they write it.

> "gradlew check" fails with OOM on fresh clone
> ---------------------------------------------
>
>                 Key: SOLR-16634
>                 URL: https://issues.apache.org/jira/browse/SOLR-16634
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Ishan Chattopadhyaya
>            Priority: Major
>
> I have a 64GB machine, where a fresh Solr clone was done. "gradlew check" failed with this following:
> https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679832&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679832
> {code}
> [ishan@7980xe solr] $ ./gradlew check -x test -Pvalidation.errorprone=true
> Downloading gradle-wrapper.jar from https://raw.githubusercontent.com/gradle/gradle/v7.6.0/gradle/wrapper/gradle-wrapper.jar
> To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.6/userguide/gradle_daemon.html#sec:disabling_the_daemon.
> Daemon will be stopped at the end of the build 
> > Task :localSettings
> IMPORTANT. This is the first time you ran the build. I wrote some sane defaults (for this machine) to 'gradle.properties', they will be picked up on consecutive gradle invocations (not this one).
> Run gradlew :helpLocalSettings for more information.
> > Task :rat
> Trying to override old definition of task javadoc
> > Task :solr:solrj:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> > Task :solr:solrj-streaming:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> > Task :solr:solrj-zookeeper:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> FAILURE: Build failed with an exception.
> * What went wrong:
> Gradle build daemon has been stopped: JVM garbage collector thrashing and after running out of JVM memory
> * Try:
> > Run with --stacktrace option to get the stack trace.
> > Run with --info or --debug option to get more log output.
> > Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> {code}
> For context, [~krisden] has attributed this to user error: https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679837&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679837
> Please also note that "gradlew localSettings" also resulted in a subsequent OOM failure (details here: https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679841&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679841)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org