Shawn Heisey commented on SOLR-9548:

I much prefer a real timestamp to an ever-increasing measure of runtime.  
Without it, it's extremely difficult to compare an external timestamp to log 

I'm ambivalent when it comes to thread names in the log.  I have not yet seen 
any situation where the thread names in Solr are useful, but perhaps that's a 
failure of imagination on my part.  I haven't tried to connect different 
logging statements together by thread name.  If they can be useful, we should 
leave them in, but if they aren't useful to most people, we should take them 
out, and explain in the docs how to adjust the config for situations where they 
can be useful.

> solr.log should start with informative welcome message
> ------------------------------------------------------
>                 Key: SOLR-9548
>                 URL: https://issues.apache.org/jira/browse/SOLR-9548
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Server
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>              Labels: logging
>             Fix For: 6.3, master (7.0)
>         Attachments: SOLR-9548.patch
> When starting Solr, the first log line should be more informative, such as
> {code}
> Welcome to Apache Solr™ version 7.0.0, running in standalone mode on port 
> 8983 from folder /Users/janhoy/git/lucene-solr/solr
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to