Your app-server will start listening to the port some time before the Solr webapp is ready, so you should check directly with Solr. You could also use JMX to check Solr's status. If you want help with your reindex failing issue, please provide more context. 25Mb is very low, please try give your VM more memory and see if indexing succeeds then.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 16. okt. 2011, at 20:38, Jithin wrote: > I am doing something similar to that. checking netstat for any connection on > port. Wanted to know if there is anything solr can do built in. > > Also I notice that my reindex is failing when I have to reindex some 7k+ > docs. Solr is giving error in logs - > > > Caused by: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) > at java.net.SocketOutputStream.write(SocketOutputStream.java:153) > at org.mortbay.io.ByteArrayBuffer.writeTo(ByteArrayBuffer.java:368) > at org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:129) > at org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:161) > at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:714) > ... 25 more > > 2011-10-16 18:05:05.431:WARN::Committed before 500 > null||org.mortbay.jetty.EofException|?at > org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:791)|?at > org.mortbay.jetty.AbstractGenerator$Output.flush(AbstractGenerator.java:569)|?at > org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:1012)|?at > sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:296)|?at > sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:140)|?at > java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)|?at > org.apache.solr.common.util.FastWriter.flush(FastWriter.java:115)|?at > org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.java:344)|?at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:265)|?at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)|?at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)|?at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)|?at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)|?at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)|?at > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)|?at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)|?at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)|?at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)|?at > org.mortbay.jetty.Server.handle(Server.java:326)|?at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)|?at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)|?at > org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)|?at > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)|?at > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)|?at > org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)|?at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)|Caused > by: java.net.SocketException: Broken pipe|?at > java.net.SocketOutputStream.socketWrite0(Native Method)|?at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)|?at > java.net.SocketOutputStream.write(SocketOutputStream.java:153)|?at > org.mortbay.io.ByteArrayBuffer.writeTo(ByteArrayBuffer.java:368)|?at > org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:129)|?at > org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:161)|?at > org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:714)|?... 25 more| > 2011-10-16 18:05:05.432:WARN::/solr/core0/update/ > java.lang.IllegalStateException: Committed > > > Is it a case where solr is not able to handle load? Currently solr is > running with a max memory setting of 25MB. All the docs are very small. Each > one contains just a few words. > > On Sun, Oct 16, 2011 at 11:52 PM, Jan Høydahl / Cominvent [via Lucene] < > ml-node+s472066n3426389...@n3.nabble.com> wrote: > >> Hi, >> >> This depends on your application server and config. A very simple option is >> to let your client poll with a ping request >> http://localhost:8983/solr/admin/ping/ until it succeeds. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> Solr Training - www.solrtraining.com >> >> On 16. okt. 2011, at 19:47, Jithin wrote: >> >>> Hi, >>> Is is possible to have a callback after solr starts listening on the >>> configured port. What I have found is there is a certain delay by the >> time >>> solr starts listening on the port after restarting solr is done. >>> So if I try to reindex solr it fails during this period. What I want is a >> >>> notification mechanism after solr starts listening on the port. >>> Is is doable? >>> >>> -- >>> View this message in context: >> http://lucene.472066.n3.nabble.com/Callback-on-starting-solr-tp3426349p3426349.html >>> Sent from the Solr - User mailing list archive at Nabble.com. >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://lucene.472066.n3.nabble.com/Callback-on-starting-solr-tp3426349p3426389.html >> To unsubscribe from Callback on starting solr?, click >> here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3426349&code=aml0aGluMTk4N0BnbWFpbC5jb218MzQyNjM0OXwtMTEwMTgwMTA3Ng==>. >> >> > > > > -- > Thanks > Jithin Emmanuel > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Callback-on-starting-solr-tp3426349p3426415.html > Sent from the Solr - User mailing list archive at Nabble.com.
