[SERVER-3831] journal by default is unreasonable for an arbiter Created: 13/Sep/11  Updated: 06/Dec/22  Resolved: 08/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: 2.0.0
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: James Pharaoh Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 2
Labels: majority
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-9144 Non-data nodes (arbiter) should not c... Closed
Assigned Teams:
Replication
Participants:

 Description   

The new default for 2.0.0 on 64bit systems is to enable journalling. This seems pretty silly if the box is only being used as an arbiter.

I don't really see why they would need a journal at all. If they do, then it surely doesn't have to be three gigs.



 Comments   
Comment by Mathias Stearn [ 13/Sep/11 ]

The problem is that the journal is created before we know that we are an arbiter. I'll see what we can do to work around this. As a work around, you can set --nojournal.

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