I wrote shell tasks that start, stop, and heartbeat the server and run them from cron (unix). Heartbeat means: 1) is the tomcat even running, 2) does tomcat return the Solr admin page, 3) does Solr return a search. For an indexer, 4) does solr return from a commit. Stopping the server via the tomcat shutdown often fails or hangs, so the sequence is: shutdown, two minutes, kill (like a ^C), 30 seconds, kill -9 (not ignoreable). If any of these fail, we get email.
What I also want is a program that quickly verifies that the index file is not corrupted. That would make me feel better about automatically deleting old snapshots. For Multicore, I'd like something that watches a directory for new cores and automatically loads and unloads them to Solr. The same way Tomcat et. al watch for newly deployed apps and removed ones.. Lance p.s. I started writing shell scripts in 1982. The young whippersnappers in the office are in awe of my MAD SHELL SKILLZ -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jon Drukman Sent: Tuesday, August 12, 2008 5:50 PM To: solr-user@lucene.apache.org Subject: Administrative questions 1. How do people deal with having solr start when system reboots, manage the log output, etc. Right now I run it manually under a unix 'screen' command with a wrapper script that takes care of restarts when it crashes. That means that only my user can connect to it, and it can't happen when the system starts up... But I don't see any other way to control the process easily. 2. Is there any way to modify a schema without stopping the process, destroying the existing index, then restarting and reloading all the data? It doesn't take that long and we're not in production yet, but once we're live I can't see that being feasible. -jsd-
