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 "Marcel Reutegger (Jira)" <ji...@apache.org> on 2020/06/30 06:55:00 UTC

[jira] [Resolved] (OAK-9125) Oak-run indexing with MongoDB logs errors in a background thread

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

Marcel Reutegger resolved OAK-9125.
-----------------------------------
    Fix Version/s: 1.8.23
       Resolution: Fixed

Applied proposed patch to 1.8 branch: http://svn.apache.org/r1879355

> Oak-run indexing with MongoDB logs errors in a background thread
> ----------------------------------------------------------------
>
>                 Key: OAK-9125
>                 URL: https://issues.apache.org/jira/browse/OAK-9125
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: indexing, oak-run
>    Affects Versions: 1.8.22
>            Reporter: Thomas Mueller
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.8.23
>
>         Attachments: OAK-9125.patch
>
>
> The following error message can be logged in a background thread:
> {noformat}
> Caused by: com.mongodb.MongoQueryException: 
> Query failed with error code 13 and error message 
> 'not authorized on ... to execute command 
> { find: "nodes", filter: { _id: "0:/" }, limit: 1, singleBatch: true }' 
> on server ... at com.mongodb.operation.FindOperation$1.call(FindOperation.java:722)
> {noformat}
> Those error messages don't have a negative impact on the index command. However, they are annoying.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)