[DISCUSS] Solr separate deprecation log

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Solr separate deprecation log

Jan Høydahl / Cominvent
Hi,

When instructing people in what to do before upgrading to a new version, we often tell them to check for deprecation log messages and fix those before upgrading. Normally you'll see the most important logs as WARN level in the Admin UI log tab just after startup and first use. But I'm wondering if it also makes sense to introduce a separate DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a separate logs/deprecation.log to make it easier to check this from the command line. If the file is non-empty you have work to do :)

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com


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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Solr separate deprecation log

Tomas Fernandez Lobbe-2
+1 Sounds like a good a idea to me.

> On Nov 8, 2018, at 5:06 AM, Jan Høydahl <[hidden email]> wrote:
>
> Hi,
>
> When instructing people in what to do before upgrading to a new version, we often tell them to check for deprecation log messages and fix those before upgrading. Normally you'll see the most important logs as WARN level in the Admin UI log tab just after startup and first use. But I'm wondering if it also makes sense to introduce a separate DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a separate logs/deprecation.log to make it easier to check this from the command line. If the file is non-empty you have work to do :)
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Solr separate deprecation log

Shawn Heisey-2
In reply to this post by Jan Høydahl / Cominvent
On 11/8/2018 6:06 AM, Jan Høydahl wrote:
> But I'm wondering if it also makes sense to introduce a separate DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a separate logs/deprecation.log to make it easier to check this from the command line. If the file is non-empty you have work to do :)

+1

I think we need to leave additivity set to true on this one so that the
logs are duplicated in solr.log.  Perhaps explicitly set additivity to
true in the config so that it's easy for somebody to disable it if it's
important to them to not have log duplication.

I have an implementation question, but that can wait until there's an
issue in Jira.

Thanks,
Shawn


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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Solr separate deprecation log

Varun Thacker-4
In reply to this post by Jan Høydahl / Cominvent
+1 . That's a good idea!

On Thu, Nov 8, 2018 at 10:26 AM Jan Høydahl <[hidden email]> wrote:
Hi,

When instructing people in what to do before upgrading to a new version, we often tell them to check for deprecation log messages and fix those before upgrading. Normally you'll see the most important logs as WARN level in the Admin UI log tab just after startup and first use. But I'm wondering if it also makes sense to introduce a separate DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a separate logs/deprecation.log to make it easier to check this from the command line. If the file is non-empty you have work to do :)

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com


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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Solr separate deprecation log

Jan Høydahl / Cominvent
Created https://issues.apache.org/jira/browse/SOLR-12987

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

12. nov. 2018 kl. 21:28 skrev Varun Thacker <[hidden email]>:

+1 . That's a good idea!

On Thu, Nov 8, 2018 at 10:26 AM Jan Høydahl <[hidden email]> wrote:
Hi,

When instructing people in what to do before upgrading to a new version, we often tell them to check for deprecation log messages and fix those before upgrading. Normally you'll see the most important logs as WARN level in the Admin UI log tab just after startup and first use. But I'm wondering if it also makes sense to introduce a separate DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a separate logs/deprecation.log to make it easier to check this from the command line. If the file is non-empty you have work to do :)

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com


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