jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2705) Reduce log level in MultiIndex for deleting obsolete index
Date Fri, 24 Sep 2010 16:53:33 GMT

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

Jukka Zitting resolved JCR-2705.
--------------------------------

         Assignee: Jukka Zitting
    Fix Version/s: 2.2.0
       Resolution: Fixed

Done in revision 1000956.

> Reduce log level in MultiIndex for deleting obsolete index
> ----------------------------------------------------------
>
>                 Key: JCR-2705
>                 URL: https://issues.apache.org/jira/browse/JCR-2705
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 2.0.0
>            Reporter: Sergiy Shyrkov
>            Assignee: Jukka Zitting
>            Priority: Trivial
>             Fix For: 2.2.0
>
>
> The MultiIndex class issues a logging message (with info level) that the obsolete index
cannot be deleted (quite often).
> As the segments are deleted later (with a retry) and this "warning" can be ignored (http://dev.day.com/kb/content/wiki/kb/Crx/Troubleshooting/UnableToDeleteObsoleteIndex.html
), it would be nice to reduce the logging level to debug. People, who are maintaining projects,
are not aware of Jackarabbit details and are sometimes scared about this "warning" :-)
> Thank you in advance!
> Kind regards
> Sergiy

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message