[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846744#comment-16846744 ] Cassandra Targett commented on SOLR-13349: -- Yes, 7.7.2 is coming very soon - within the next couple of weeks. > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > Fix For: 7.7.2, 8.1, master (9.0) > > Attachments: SOLR-13349.patch > > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846700#comment-16846700 ] Simon Tunnat commented on SOLR-13349: - Will there be a Solr patch version 7.7.2 for this bug? > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > Fix For: 7.7.2, 8.1, master (9.0) > > Attachments: SOLR-13349.patch > > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804426#comment-16804426 ] Erick Erickson commented on SOLR-13349: --- [~ichattopadhyaya] I take it back, I put the entries in CHANGES.txt for both 7x and 7.7.2, so you should be good to go. > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804424#comment-16804424 ] ASF subversion and git services commented on SOLR-13349: Commit 9e1ada0ab72f3a41104b422ebd03665528b7d2ab in lucene-solr's branch refs/heads/branch_7_7 from erick [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=9e1ada0 ] SOLR-13349: High CPU usage in Solr due to Java 8 bug > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804409#comment-16804409 ] ASF subversion and git services commented on SOLR-13349: Commit 8773e6b160029b43764c4b9459efe9624c52cb31 in lucene-solr's branch refs/heads/branch_7x from erick [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=8773e6b ] SOLR-13349:High CPU usage in Solr due to Java 8 bug (cherry picked from commit b2941ff) > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804410#comment-16804410 ] ASF subversion and git services commented on SOLR-13349: Commit 7dfe1c093b65f77407c2df4c2a1120a213aef166 in lucene-solr's branch refs/heads/branch_7x from erick [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=7dfe1c0 ] SOLR-13349: High CPU usage in Solr due to Java 8 bug > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804395#comment-16804395 ] ASF subversion and git services commented on SOLR-13349: Commit 03a3562f782a795afb3e5dbb474aca216273cc4d in lucene-solr's branch refs/heads/branch_8x from erick [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=03a3562 ] SOLR-13349:High CPU usage in Solr due to Java 8 bug (cherry picked from commit b2941ff) > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804390#comment-16804390 ] ASF subversion and git services commented on SOLR-13349: Commit b2941ff0da4987dec4774aa6b4bb7c597b362243 in lucene-solr's branch refs/heads/master from erick [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b2941ff ] SOLR-13349:High CPU usage in Solr due to Java 8 bug > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802994#comment-16802994 ] Erick Erickson commented on SOLR-13349: --- I don't know what I was seeing yesterday then, 'cause I can't see it now. So you and Cassandra are right and I'm hallucinating. > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802515#comment-16802515 ] Ishan Chattopadhyaya commented on SOLR-13349: - Thanks for bringing it to my notice, [~erickerickson]. Seems like latest code on branch_6_6 has it at 1. So, I'm planning to go ahead with the release there. +1 to fixing this asap in branch_7_7, since a 7.7.2 release might be on the cards. > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801897#comment-16801897 ] Erick Erickson commented on SOLR-13349: --- I pulled the branch_6_6 code fresh and the change from 1 to 0 is there. Hmmm, the download for 6.6.5 is dated July 2018, and this change was made to the 6.6 code line in late November. So I'd guess it doesn't affect the _released_ 6.6.5, but would affect 6.6.6? > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13349) High CPU usage in Solr due to Java 8 bug
[ https://issues.apache.org/jira/browse/SOLR-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801885#comment-16801885 ] Cassandra Targett commented on SOLR-13349: -- Does it really impact 6.6? If the theory is correct that the change from 1 to 0 is causing the problem, then the code change occurred with 7.7: branch_6_6: https://github.com/apache/lucene-solr/blob/branch_6_6/solr/core/src/java/org/apache/solr/update/CommitTracker.java#L58 branch_7_7: https://github.com/apache/lucene-solr/blob/branch_7_7/solr/core/src/java/org/apache/solr/update/CommitTracker.java#L62 > High CPU usage in Solr due to Java 8 bug > > > Key: SOLR-13349 > URL: https://issues.apache.org/jira/browse/SOLR-13349 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.7, 8.0, master (9.0) >Reporter: Erick Erickson >Priority: Major > > We've had sporadic reports of high CPU usage in Solr 7. Lukas Weiss reported > a Java 8 bug that appears to be the root cause (I have not personally > verified), see: [https://bugs.openjdk.java.net/browse/JDK-8129861] e-mail > reproduced below: > CommitTracker makes this call: > Executors.newScheduledThreadPool(0, new > DefaultSolrThreadFactory("commitScheduler")); > The supposition is that calling this with 1 will fix this (untested) > [~ichattopadhyaya] This affects 6.6 and IIUC you're spinning a new version. > We'll need to verify and include this fix. > [~jpountz] You're right. I first thought "naaah, it wouldn't be that far > back" but your question made me check, thanks! > AFAICT, this is the only place in Solr/Lucene that uses zero. > Using Java 9+ is another work-around. > Anyone picking this up should port to 7.7 as well. > e-mail from the user's list (many thanks to Lukas and Adam). > Apologies, I can’t figure out how to reply to the Solr mailing list. > I just ran across the same high CPU usage issue. I believe it’’s caused by > this commit which was introduced in Solr 7.7.0 > > [https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5] > There is a bug in JDK versions <=8 where using 0 threads in the > ScheduledThreadPool causes high CPU usage: > [https://bugs.openjdk.java.net/browse/JDK-8129861] > Oddly, the latest version > of solr/core/src/java/org/apache/solr/update/CommitTracker.java on > master still uses 0 executors as the default. Presumably most everyone is > using JDK 9 or greater which has the bug fixed, so they don’t experience > the bug. > Feel free to relay this back to the mailing list. > Thanks, > Adam Guthrie > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org