db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-5086) Disable istat logging by default
Date Wed, 02 Mar 2011 19:09:37 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-5086:
--------------------------------------

    Attachment: disable-logging.diff

Attaching a patch that makes logging disabled by default. According to the comments in the
code, the logging was intended to be disabled before the release.

Running regression tests.

> Disable istat logging by default
> --------------------------------
>
>                 Key: DERBY-5086
>                 URL: https://issues.apache.org/jira/browse/DERBY-5086
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions: 10.8.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: disable-logging.diff
>
>
> The automatic index statistics daemon will by default log what it's doing. That means
messages like these ones will be written to derby.log during normal operation:
> Wed Mar 02 13:36:22 CET 2011 Thread[main,5,main] {istat} "APP"."T": update scheduled
- 23ce809c-012e-7691-6c29-000003480128 reason=[no stats, row-estimate=36167] (queueSize=1)
> Wed Mar 02 13:36:22 CET 2011 Thread[index-stat-thread,5,main] {istat} "APP"."T": generating
index statistics
> Wed Mar 02 13:36:23 CET 2011 Thread[index-stat-thread,5,main] {istat} "APP"."T": generation
complete (509 ms)
> Wed Mar 02 13:36:23 CET 2011 Thread[main,5,main] {istat} stopping daemon, active=false,
work/age=510/14736 [q/p/s=0/1/1,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]
> Although these messages may be helpful in diagnosing bugs, they may also be a source
of confusion since users probably only expect errors/problems to be logged by default. Also,
for some workloads, large quantities of log may be produced and take up disk space. Therefore,
I think we should disable the logging before the 10.8 release, and instead instruct users
who experience problems to enable logging manually with the derby.storage.indexStats.log property.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message