[
https://issues.apache.org/jira/browse/OAK-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380125#comment-14380125
]
Chetan Mehrotra commented on OAK-2680:
--------------------------------------
bq. I experienced a view new log statements coming from LuceneIndexProvider
during startup:
Thats by design. An {{observer}} which is just interested in changes and does
not care about external or internal would prefer to keep the size small and let
events be collapsed/merged. Warning makes more sense if the underlying
{{ObservationListener}} is only interested in internal events.
> 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)
