Mike created SOLR-6071:
--------------------------

             Summary: Make solr install like other databases
                 Key: SOLR-6071
                 URL: https://issues.apache.org/jira/browse/SOLR-6071
             Project: Solr
          Issue Type: New Feature
          Components: scripts and tools
    Affects Versions: 5.0
         Environment: Ubuntu
            Reporter: Mike


It's long past time that Solr should have proper startup and log scripts. 

There are a number of reasons and much evidence why we should start including 
them:

1. In Solr-4792 we removed the war file from the distribution making it easier 
than ever before to set solr up with these scripts.
2. The StackOverflow question on this topic has been viewed more than 34k times 
and has several differing answers.
3. For non-java developers, figuring out the right way to start and daemonize 
Solr isn't obvious. Right now, my installation has a number of java flags that 
I've accumulated over the years (-jar means what? -server is only needed on 32 
bit machines? -xMX huh?) This leads to varied deployments and inconsistencies 
that common scripts could help alleviate.
4. Anecdotally I've heard endless bashing of Solr because it's such a pain to 
get set up. 
5. Solr is unlike any other database I know in the grittiness of starting it up.
6. Not having these scripts makes Solr look less polished than it would 
otherwise.

We discussed this on IRC a bit yesterday and there didn't seem to be any 
opposition to doing this. Consensus seemed to be simply that it hadn't been 
done...yet.

I am not an expert on these things, but I think we should get something put 
together for Solr 5, if there's time. Hopefully this thread can get the ball 
rolling -- I didn't see any previous discussion anywhere. Apologies if I missed 
it. 

This would be a great improvement to Solr.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to