[SERVER-10293] process mongods are usually auto-disconnected, and sometimes we are fail to start it in hand Created: 23/Jul/13 Updated: 10/Dec/14 Resolved: 23/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | zhangjianchao | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | replicaset, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
operation system:red hat linux-server-6.4-x86_64 three Mongo config server |
||
| Attachments: |
|
| Participants: |
| Description |
|
we started three mongod(correspond to three shard) in every server.afte we insert data about 1000,0000,we check the process mongods whether they are still started yet.then we find someone is stoped, the log is uploaded in the first attachement. Mon Jul 22 10:00:30.337 [repl writer worker 1] ERROR: writer worker caught exception: BSONObj size: 1936028718 (0x2E746573) is i } how to deal with them |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 23/Jul/13 ] |
|
duplicate of |