[SERVER-28603] new 3.2 replica nodes "could not find member to sync from" Created: 04/Apr/17 Updated: 04/Apr/17 Resolved: 04/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Enrique Abott | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It seems after completing the rolling upgrade from 3.0.12 to 3.2, the new nodes cannot sync with the primary instance for some reason. Do you know what could be causing this issue? |
| Comments |
| Comment by Kelsey Schubert [ 04/Apr/17 ] |
|
Thanks for your report. As mentioned previously, the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. See also our Technical Support page for additional support resources. Kind regards, |