From your email I gather your main concern is starting zookeeper on server startups.
You may want to look at these non-native service oriented options too: Create a script( cmd or bat) to start ZK on server bootup. This method may not restart Zk if Zk crashes(not the server). Create C# commad line program that starts on server bootup(see above) that uses the .Net System.Diagnostics.Process.Start method to start Zk on sever start and monitor the Zk process via a loop. Restart when Zk process crash or "hang". I prefer this method. There might be a Java equivalent of this. There are many exmaples avaialble on the web. Cheers, @nazik_huq On Thursday, January 9, 2014 10:07 AM, Charlie Hull <char...@flax.co.uk> wrote: On 09/01/2014 09:44, Karthikeyan.Kannappan wrote: > I am hosting in windows OS > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Zookeeper-as-Service-tp4110396p4110413.html > Sent from the Solr - User mailing list archive at Nabble.com. > There are various ways to 'servicify' (yes that may not be an actual word) executable applications on Windows. The venerable SrvAny is one such option as is the newer nssm.exe (Non-Sucking Service Manager). Bear in mind that a Windows Service doesn't operate quite the same way with regard to stdout and stderr which may mean any error messages end up in a black hole, with you simply getting something unhelpful 'service failed to start' error messages from Windows itself if something goes wrong. The 'working directory' is another thing that needs careful setting up. Cheers Charlie -- Charlie Hull Flax - Open Source Enterprise Search tel/fax: +44 (0)8700 118334 mobile: +44 (0)7767 825828 web: www.flax.co.uk
