[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15000543#comment-15000543 ] Marcel Reutegger commented on OAK-3554: --- For now I didn't change the write concern when connected to a

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991306#comment-14991306 ] Marcel Reutegger commented on OAK-3554: --- I implemented the proposed changes to the default

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991355#comment-14991355 ] Marcel Reutegger commented on OAK-3554: --- For reference, this is the result for a local 3-node replica

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982198#comment-14982198 ] Ian Boston commented on OAK-3554: - [~chetanm] as discussed offline. While putting w=2 onto the query that

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982325#comment-14982325 ] Chetan Mehrotra commented on OAK-3554: -- bq. You may find that the difference between a global w=2 and a

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982349#comment-14982349 ] Ian Boston commented on OAK-3554: - +1, looks good and safe to me. > Use write concern of w:majority when

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975881#comment-14975881 ] Marcel Reutegger commented on OAK-3554: --- +1 > Use write concern of w:majority when connected to a

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975820#comment-14975820 ] Chetan Mehrotra commented on OAK-3554: -- Due to OAK-2592 even setting the write concern would not be

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976109#comment-14976109 ] Chetan Mehrotra commented on OAK-3554: -- Some more thoughts - It might happen that setting w:majority

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976125#comment-14976125 ] Marcel Reutegger commented on OAK-3554: --- I was thinking about this as well in context of OAK-2592, but

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976312#comment-14976312 ] Chetan Mehrotra commented on OAK-3554: -- Had a discussion with Marcel and Vikas on this and below is the

[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

[ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976408#comment-14976408 ] Norberto Leite commented on OAK-3554: - Hi gentelman, Actually you should wait for version 3.2 to