[SERVER-26627] Config server crash after shard removal Created: 14/Oct/16 Updated: 15/Oct/16 Resolved: 14/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Stability, WiredTiger |
| Affects Version/s: | 3.0.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | dabest1 | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Not sure if it is easily reproducible: |
| Participants: |
| Description |
|
Mongod crashed on 1st config server after removal of a shard from a cluster. MongoDB version: 3.0.8. Log file on config server shows: Restarting the service failed with permissions errors. It seems like the ownership of few files was changed from mongod:mongod to root:root during or before the crash. Some kind of bug in mongod? I don't think anyone changed the ownership. These are the files with wrong ownership: This type of crash happened before, where 1st config server crashed after shard removal, but I do not recall if ownership was also broken. |
| Comments |
| Comment by dabest1 [ 15/Oct/16 ] |
|
Thank you, I have identified an automated process which has shut down the config server during the downsizing process. However, I think you should still keep this bug open as the ownership of the files was incorrectly set during the shutdown. |
| Comment by Kelsey Schubert [ 14/Oct/16 ] |
|
Hi dabest1, Thanks for your report. It appears that the mongo process received a SIGTERM, and shutdown cleanly. I would suggest investigating who or what is sending the SIGTERM. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |