[
https://issues.apache.org/jira/browse/OAK-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381300#comment-14381300
]
Chetan Mehrotra commented on OAK-2680:
--------------------------------------
[~mduerig] I would prefer if we log warning only if the underying
listener/observer would not like the events to be compacted. If the observer is
fine for events to be compacted (like in case of LuceneIndexProvider) then
warning should not be logged. Otherwise you would frequently see this warning
with {{LuceneIndexProvider}} and that would create noise.
Probably the BackgroundObserver takes a flag indicating that wether wrapped
observer is fine with events to be compacted then we can pass that flag within
{{LuceneIndexProvider}}
> 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)
