[
https://issues.apache.org/jira/browse/SOLR-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421436#comment-16421436
]
Shawn Heisey commented on SOLR-12173:
-------------------------------------
A side effect of logging at WARN would be that there would usually be something
in the logging tab of the admin UI. We did recently fix a bug so it explicitly
says there's nothing to display, but a real log entry would be a good thing.
Random thought: A log event indicating when all required SolrCloud recovery
operations are finished would be useful. I think it should be logged
separately, with elapsed time for all recovery and including the JVM uptime
again.
> Create or improve "Solr startup complete" log message
> -----------------------------------------------------
>
> Key: SOLR-12173
> URL: https://issues.apache.org/jira/browse/SOLR-12173
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Affects Versions: 7.3
> Reporter: Shawn Heisey
> Priority: Trivial
>
> Solr should log an event indicating when startup is complete, with a logger
> name or a text string that is unique so we can search a log for this event.
> The time to log this is when all cores are loaded/started (or inventoried for
> lotsOfCores functionality), cloud information is examined and cached as
> required, background threads started, etc.
> The log message should included JVM uptime and elapsed time since webapp
> startup.
> If somebody were to hot-deploy Solr into a running container, the JVM uptime
> would not be useful information. That should not be common, though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
