[
https://issues.apache.org/jira/browse/SOLR-12265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker reopened SOLR-12265:
----------------------------------
Reopening the Jira.
Tomas pointed out that when you run bin/solr -f we get this error
{code:java}
[master] ~/apache-work/lucene-solr/solr$ ./bin/solr start -f
*** [WARN] *** Your open file limit is currently 256.
It should be set to 65000 to avoid operational disruption.
If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
your profile or solr.in.sh
*** [WARN] *** Your Max Processes Limit is currently 1418.
It should be set to 65000 to avoid operational disruption.
If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
your profile or solr.in.sh
ERROR : org/eclipse/jetty/util/JavaVersion
java.lang.NoClassDefFoundError: org/eclipse/jetty/util/JavaVersion
at org.eclipse.jetty.start.StartArgs.setProperty(StartArgs.java:1273)
at org.eclipse.jetty.start.Modules.<init>(Modules.java:65)
at org.eclipse.jetty.start.Main.processCommandLine(Main.java:312)
at org.eclipse.jetty.start.Main.main(Main.java:75)
Caused by: java.lang.ClassNotFoundException: org.eclipse.jetty.util.JavaVersion
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 4 more
Usage: java -jar $JETTY_HOME/start.jar [options] [properties] [configs]
java -jar $JETTY_HOME/start.jar --help # for more information{code}
Also the CHANGES entry mentions the wrong Jira
> Upgrade Jetty to 9.4.10
> -----------------------
>
> Key: SOLR-12265
> URL: https://issues.apache.org/jira/browse/SOLR-12265
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12265.patch
>
>
> Solr 7.3 upgraded to Jetty 9.4.8
> We're seeing this WARN very sporadically ( maybe one in every 100k requests )
> on the replica when indexing.
> {code:java}
> date time WARN [qtp768306356-580185] ? (:) -
> java.nio.channels.ReadPendingException: null
> at org.eclipse.jetty.io.FillInterest.register(FillInterest.java:58)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.io.AbstractEndPoint.fillInterested(AbstractEndPoint.java:353)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.io.AbstractConnection.fillInterested(AbstractConnection.java:134)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> ~[jetty-server-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:289)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at org.eclipse.jetty.io.ssl.SslConnection$3.succeeded(SslConnection.java:149)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)
> ~[jetty-io-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:247)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:140)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:382)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:708)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:626)
> ~[jetty-util-9.4.8.v20171121.jar:9.4.8.v20171121]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0-zing_17.11.0.0]
> date time WARN [qtp768306356-580185] ? (:) - Read pending for
> org.eclipse.jetty.server.HttpConnection$BlockingReadCallback@2e98df28
> prevented AC.ReadCB@424271f8{HttpConnection@424271f8[p=HttpParser{s=START,0
> of
> -1},g=HttpGenerator@424273ae{s=START}]=>HttpChannelOverHttp@4242713d{r=141,c=false,a=IDLE,uri=null}<-DecryptedEndPoint@4242708d{/host:52824<->/host:port,OPEN,fill=FI,flush=-,to=1/86400}->HttpConnection@424271f8[p=HttpParser{s=START,0
> of -1},g=HttpGenerator@424273ae{s=START}]=>{code}
> When this happens the leader basically waits till it get's a
> SocketTimeoutException and then puts the replica into recovery.
> My motivation for upgrading to Jetty 9.4.9 is that the EatWhatYouKill was
> introduced in Jetty 9.4.x . I don't believe we saw this error in Jetty 9.3.x
> and then in Jetty 9.4.9 this class has undergone quite a few changes
> [https://github.com/eclipse/jetty.project/commit/0cb4f5629dca082eec943b94ec8ef4ca0d5f1aa4#diff-ae450a12d4eca85a437bd5082f698f48]
> .
>
--
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
