I wouldn't really be happy with such a solution. The admin gui is a
diagnostic/inspection tool, not a graphical configuration mechanism.
Also, it would seem odd to have a config parameter in Solr that
overrode explicitly-configured container/jvm settings unnecessarily.
-Mike
On 15-Feb-08, at 6:34 PM, Fuad Efendi wrote:
Thanks...
I am thinking about making *persistent* runtime configuration options
(available via SOLR admin screen)... It would be best option... Of
course we
can write (global) config file and put it somewhere, even for people
"who
would expect the JVM
default configuration to work" - many people expect HTTP Client to
work
without deadlocks ;) in Java 6 (even 1.5.14; SUN)(what about backward
compatibility? Write once run everywhere?!!)
: Currently, default settings output "UPDATE" messages
(thousands per second
: in my case). Is it WARNING/SEVERE setting in SOLR source?
They are INFO level messages, which is the jvm defualt.
One INFO level message per request doesn't seem that excessive to me,
almost any HTTP server i can think of is going to have an
access log that
records even more info per request.
Solr doens't have any logging configuration options in the
solrconfig.xml
for a variety of reasons, a few off hte top of my head...
* most servlet containers already have a way to cofigure
logging. If
solr had it's own way (that trumped the servlet container)
that would piss
a lot of people off would expect their container configs to
work, and make
configuring solr really confusing.
* even if people use a servlet container that doesn't have a
convinient way to configure logging, the JVM has a default logging
configuration mechanism which allows for truely globals logging
configuration (used by every JVM instance on the machine)
with overrides
possible per JVM. If solr had it's own way (that trumped the servlet
container) that would piss a lot of people who would expect the JVM
default configuration to work, and make configuring solr
really confusing.
