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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/03/08 10:03:38 UTC

[jira] [Comment Edited] (OAK-5368) Not configurable/Unnecessary short Lucene Observation Queue length

    [ https://issues.apache.org/jira/browse/OAK-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901002#comment-15901002 ] 

Chetan Mehrotra edited comment on OAK-5368 at 3/8/17 10:03 AM:
---------------------------------------------------------------

ChangeProcessor is used for JCR Listerners so it would not be involved with Observer registered by Lucene. Hence the confusion! May be some other queue was also full and that lead to confusion that warning originated due to this observer


was (Author: chetanm):
ChangeProcessor is used for JCR Listerners so it would not be involved with Observer registered by Lucene

> Not configurable/Unnecessary short Lucene Observation Queue length
> ------------------------------------------------------------------
>
>                 Key: OAK-5368
>                 URL: https://issues.apache.org/jira/browse/OAK-5368
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>    Affects Versions: 1.4.10
>            Reporter: Stefan Eissing
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.8
>
>         Attachments: LuceneIndexConfigObserver-under-load.png
>
>
> The maximum queue length in the {{LuceneIndexConfigObserver}} is hard coded to 5. This is unreasonable short for production systems experiencing heavy load.
> Tests with a patched version resulted in observed queue length of >100 entries. This floods warnings into the error log, produces additional load.
> The fix would be to increase the queue max, make it configurable or rely on the system default (which can be configured).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)