[SERVER-36678] member in replset becomes down with unknow reason Created: 14/Aug/18 Updated: 15/Aug/18 Resolved: 15/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.7, 3.6.6 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Bruce Zu | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
We have a secondary member, IP 172-31-66-130, became RS_DOWN the time primary, IP 172-31-54-204, found it became RS_DOWN is 2018-08-04T03:13:54.704+0000 before the EC2 is stopped and start on Aug 6 the last mongod.log message is recorded on Aug 4
mongod.log mongodlog.zip This is the second time our replset experience this issue. This is not any hints can be found from /var/log Any help will be appreciated, Please let me know any other log or information need to provide. Thank you! Bruce
|
| Comments |
| Comment by Bruce Zu [ 15/Aug/18 ] |
|
Hi Nick, I am not sure I run into a bug or not, so I post there with diagnostic. This is not expected behavior that this secondary became unreachable and frozen suddenly while the other secondary worked well with the same configuration. Anyway, I post it to user-group https://groups.google.com/forum/#!topic/mongodb-user/HH5yY4QwNmc Best regards, Bruce
|
| Comment by Nick Brewer [ 15/Aug/18 ] |
|
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-user group. -Nick |