[SERVER-17274] Does not set arbiterOnly:true if journal enabled Created: 13/Feb/15  Updated: 14/Apr/16  Resolved: 20/Mar/15

Status: Closed
Project: Core Server
Component/s: Replication, Usability
Affects Version/s: 2.6.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Grachov Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Made mistake in arbiter configuration, did
'storage.journal.enabled' instad of 'journal.enabled', and then
rs.addArb(myhost);
arbiter became PRIMARY, as its beign hosted on most powerful server.

cleared /data/arb directory and disabled journaling, and all worked as expected

mongo 2.6.7



 Comments   
Comment by Ramon Fernandez Marina [ 02/Mar/15 ]

drontxl@yandex.ru, we haven't heard back from you for a while. If this is still an issue for you, can you please send the logs requested in my previous message?

Thanks,
Ramón.

Comment by Ramon Fernandez Marina [ 13/Feb/15 ]

drontxl@yandex.ru, can you please upload the logs for the new arbiter node since startup, and the logs from the other nodes since before you run the rs.addArb() command?

Generated at Thu Feb 08 03:43:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.