docker-library / docker-library/mysql
temp server maybe become a zombie process
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.6k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
In my environment, I found the temp mysql server become a zombie process，like this:
UID PID PPID C STIME TTY TIME CMD
mysql 1 0 0 Jul03 ? 00:05:47 mysqld --defaults-file=/etc/my.cnf
mysql 15 1 0 Jul03 ? 00:00:00 [mysqld]
I suspect when mysqldump shutdown mysql with socket ends，but the mysqld not exits completed。
when the second mysqld started，the first mysqld process becomes zombie process；
Is this possible?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported temporary MySQL server lifecycle around mysqldump, socket shutdown, and starting a second mysqld process. Inspect the reported process states and determine whether shutdown leaves a zombie; completion requires identifying the cause and defining the needed lifecycle fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100