You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marc Pfaff (JIRA)" <ji...@apache.org> on 2015/03/25 16:59:53 UTC
[jira] [Comment Edited] (OAK-2680) Report a full observation queue
situation to the logfile
[ https://issues.apache.org/jira/browse/OAK-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380112#comment-14380112 ]
Marc Pfaff edited comment on OAK-2680 at 3/25/15 3:59 PM:
----------------------------------------------------------
The patch is logging at WARN level. I'm uncertain if that is too verbose or not. AFAIU a full queue should ideally not happen. But during the testing of this patch I experienced a view new log statements coming from LuceneIndexProvider during startup:
{code}
Revision queue for observer org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexProvider is full (max = 5). Further revisions will be compacted.
{code}
Looks like this specific observer's queue is explicitly set to 5 only.
was (Author: pfaffm@adobe.com):
The patch is logging at WARN level. I'm uncertain if that is too verbose or not. AFAIU a full queue should ideally not happen. But during the testing of this patch I experienced queue a view new such log statements coming from LuceneIndexProvider during startup:
{code}
Revision queue for observer org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexProvider is full (max = 5). Further revisions will be compacted.
{code}
Looks like this specific observer's queue is explicitly set to 5 only.
> Report a full observation queue situation to the logfile
> --------------------------------------------------------
>
> Key: OAK-2680
> URL: https://issues.apache.org/jira/browse/OAK-2680
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-core
> Affects Versions: 1.1.7
> Reporter: Marc Pfaff
> Assignee: Michael Dürig
> Priority: Minor
> Fix For: 1.1.8
>
> Attachments: OAK-2680.patch
>
>
> This is a improvement request for having an explicit warning in the log file, when the BackgroundObserver's queue maximum is reached.
> Currently, in that case, a warning is logged from the ChangeProcessor observer only. But as each observer has it's own queue, a warning from a more central place covering all observers would be helpful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)