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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/11/14 11:36:03 UTC
[jira] [Closed] (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 ]
Davide Giannella closed OAK-4984.
---------------------------------
Bulk close for 1.5.13
> 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
> Assignee: Marcel Reutegger
> Priority: Minor
> Labels: resilience
> Fix For: 1.6, 1.5.13
>
>
> 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)