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 2016/10/24 10:01:07 UTC

[jira] [Updated] (OAK-4984) Server time unavailable with authenticated connection to MongoDB

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

Marcel Reutegger updated OAK-4984:
----------------------------------
    Labels: resilience  (was: )

> Server time unavailable with authenticated connection to MongoDB
> ----------------------------------------------------------------
>
>                 Key: OAK-4984
>                 URL: https://issues.apache.org/jira/browse/OAK-4984
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.4
>            Reporter: Marcel Reutegger
>            Priority: Minor
>              Labels: resilience
>
> The MongoDocumentStore gets the current server time with the {{serverStatus}} command. When MongoDB is configured with authentication, the command may fail because it requires the [clusterMonitor|https://docs.mongodb.com/manual/reference/built-in-roles/#clusterMonitor] role.
> The method will then simply log a WARN message and assume no time difference. Maybe there is a different command we can use to get the time on the server?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)