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 "Alex Deparvu (JIRA)" <ji...@apache.org> on 2018/10/09 08:32:00 UTC
[jira] [Commented] (OAK-7783) Default write concern and read
concern level not applied
[ https://issues.apache.org/jira/browse/OAK-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642967#comment-16642967 ]
Alex Deparvu commented on OAK-7783:
-----------------------------------
{{ReplicaSetDefaultWriteConcernIT.majorityWriteConcern}} is currently failing on my machine due to lack of running mongo instance:
{noformat}
[INFO] Running org.apache.jackrabbit.oak.plugins.document.mongo.ReplicaSetDefaultWriteConcernIT
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1,140.316 s <<< FAILURE! - in org.apache.jackrabbit.oak.plugins.document.mongo.ReplicaSetDefaultWriteConcernIT
[ERROR] majorityWriteConcern(org.apache.jackrabbit.oak.plugins.document.mongo.ReplicaSetDefaultWriteConcernIT) Time elapsed: 1,140.293 s <<< ERROR!
com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=REPLICA_SET, servers=[{address=127.0.0.1:50900, type=REPLICA_SET_SECONDARY, roundTripTime=0.7 ms, state=CONNECTED}, {address=50902:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: No route to host (connect failed)}}, {address=50901:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: No route to host (connect failed)}}, {address=127.0.0.1:50902, type=REPLICA_SET_GHOST, roundTripTime=0.6 ms, state=CONNECTED}, {address=127.0.0.1:50901, type=REPLICA_SET_GHOST, roundTripTime=0.6 ms, state=CONNECTED}]
at org.apache.jackrabbit.oak.plugins.document.mongo.ReplicaSetDefaultWriteConcernIT.majorityWriteConcern(ReplicaSetDefaultWriteConcernIT.java:60)
{noformat}
> Default write concern and read concern level not applied
> --------------------------------------------------------
>
> Key: OAK-7783
> URL: https://issues.apache.org/jira/browse/OAK-7783
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 1.9.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.10, 1.9.9
>
>
> The automatic default write concern and read concern level are not applied when a DocumentNodeStore on MongoDB is constructed with a builder. The MongoDocumentStore will use the server default values instead.
> This is a regression introduced with OAK-7360.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)