On 3/2/2015 10:34 AM, Reitzel, Charles wrote: > > Hi Ram, > > > > It appears the problem is that the old solr/jetty process is actually > still running when the new solr/jetty process is started. That’s the > problem that needs fixing. > > > > This is not a rare problem in systems with worker threads dedicated to > different tasks. These threads need to wake up in response to the > shutdown signal/command, as well the normal inputs. > > > > It’s a bug I’ve created and fixed a couple times over the years … > :-) I wouldn’t know where to start with Solr. But, as I say, > re-using the port is a band-aid. I’ve yet to see a case where it is > the best solution. >
I can't say whether the lack of the reuse option on the stop port binding is a real problem. I can say that I've never had a problem with my init script for the 4.x example jetty, which *DOES* use the STOPPORT and STOPKEY options. I know that there have been times when Solr has been completely unresponsive and the init script has been forced to use the -9 signal. You can find this init script (in redhat and ubuntu varieties) here: http://wiki.apache.org/solr/ShawnHeisey Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
