[SERVER-5927] During full resyncing, when a connection error happens, thread fault appears and restart full resyncing. Is this a correct process? Created: 25/May/12 Updated: 08/Mar/13 Resolved: 27/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Kihyun Kim | Assignee: | Mathias Stearn |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | replication, resyncing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Oracle linux 5.7, iSCSI(not shared with network) |
||
| Participants: |
| Description |
|
We tried the full resyncing(remove all files in dbpath, then restart mongod). After for a while, we found these messages. And mongod continues to sync fully again. Is this a correct process that can be happened? ======================================================================================= |
| Comments |
| Comment by Mathias Stearn [ 28/Aug/12 ] |
|
Mongodump and resyncing use very similar mechanisms. Are you sure that the mongodump succeeds without error between the same two machines? It could just be timing related then. Does mongod eventually complete it's resync or does it get stuck at the same point every time? |
| Comment by Kihyun Kim [ 16/Aug/12 ] |
|
Ok, it looks like a network weakness issue. |
| Comment by Mathias Stearn [ 07/Aug/12 ] |
|
It looks like there was a connectivity issue which the server was able to recover from. Have there been any negative effects? |
| Comment by auto [ 13/Jul/12 ] |
|
Author: {u'date': u'2012-07-13T06:22:39-07:00', u'email': u'ian.whalen@gmail.com', u'name': u'Ian Whalen'}Message: Merge pull request #263 from stevebriskin/master JS tests for |