[SERVER-2276] Lost Data while Master in Replica set went down Created: 22/Dec/10 Updated: 29/May/12 Resolved: 02/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 1.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Krishna Maddireddy | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOs 5 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Lost Data while Master in Replica set went down Lost data when i killed master while inserting data through mongos shell. I don't see any rollback files in any of the data directories. Configuration: Replica Set dbs mongod --fork --rest --port 30001 --replSet set1/localhost:30001,localhost:30002,localhost:30003 --shardsvr --oplogSize 500 --dbpath /home/mongo/data/db/s1r1 --logpath /home/mongo/logs/s1r1.log Replica configuration: new_config = {_id: 'set1', members: [ Configuration Server mongod --fork --configsvr --port 20001 --dbpath /home/mongo/data/db/config1 --logpath /home/mongo/logs/config1.log Mongos mongos --fork --configdb localhost:20001 --chunkSize 1 --logpath /home/mongo/logs/mongos.log > rs.status() , , , , { "_id" : 4, "name" : "localhost:30005", "health" : 1, "state" : 7, "uptime" : 26, "lastHeartbeat" : "Wed Dec 22 2010 14:47:07 GMT-0500 (EST)" } ], added sharding config through mongos db.runCommand( { addshard : "set1/localhost:30001,localhost:30002,localhost:30003", name : "shard1" }); db.runCommand( {listshards:1}) ], inserted some data use demo_contacts db.contacts.count() Killed master while inserting data. ~ |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 02/Sep/11 ] |
|
Sorry for the delay. |
| Comment by Krishna Maddireddy [ 22/Dec/10 ] |
|
is the lost data stored some where in unsafe mode? |
| Comment by Krishna Maddireddy [ 22/Dec/10 ] |
|
with 1.7.5, when a existing master goes down , the mongos can not access the cluster even though there was a active primary. > db.printShardingStatus() ); ); |
| Comment by Eliot Horowitz (Inactive) [ 22/Dec/10 ] |
|
Can you try with 1.7.5? Note that unless you call getLastError after every insert (or use safe mode in the drivers), on hardware failure a write may get lost. |