It doesn't seem you can lose data even when you might otherwise expect to ;) I setup a small replica set using mongod --fork --logpath a.log --smallfiles --oplogSize 50 --port 27001 --dbpath data/z1 --replSet z mongod --fork --logpath b.log --smallfiles --oplogSize 50 --port 27002 --dbpath data/z2 --replSet z mongod --fork --logpath c.log --smallfiles --oplogSize 50 --port 27003 --dbpath data/z3 --replSet z And initalized it: > rs.initiate( { _id:'z', members:[ { _id:1, host:'localhost:27001' }, { _id:2, host:'localhost:27002' }, { _id:3, host:'localhost:27003' } ] } ); Then I killed all three processes: kill -9 25542 25496 25483 Next I brought one of them back up mongod --fork --logpath c.log --smallfiles --oplogSize 50 --port 27003 --dbpath data/z3 and inserted a doc > db.foo.insert({a:1}) Then I killed that process kill -9 25885 and brought the replica set back online using mongod --for
   Recent articles
Console Blackjack in Crystal
Nautical War
Reverse (Othello) in ReactJS using Typescript
Web Blackjack in ReactJS
Console Blackjack in Python 3
   Tags
android (1) apache (1) apple (1) bash (2) bashrc (1) battleship (1) blackjack (8) c (2) c++ (1) callproof (1) clang (2) clang++ (1) console (1) crystal (1) data (1) debian (4) diff (1) django (2) enterprise (1) freebsd (1) g++ (1) games (1) gcc (1) git (3) github (1) gmail (1) go-lang (3) google (1) gourse (1) kernel (3) latin1 (1) linux (4) lottery (1) microsoft (1) module (1) mongodb (1) mp3s (1) mutt (1) nautical (1) patch (1) perl6 (1) postgresql (2) powerball (1) psql (1) python (2) python3 (1) raspberrypi (1) reactjs (2) reversi (1) sdl (1) sed (1) stack (1) testing (2) trace (1) typescript (2) ubuntu (2) utf8 (1) virus (1) war (1)
   Twitter

Copyright © 2019 · GregDonald.com · All Rights Reserved