Bug #86854 MySQL Cluster entrypoint.sh does not start apps with exec
| Submitted: | 28 Jun 2017 19:09 | Modified: | 17 Aug 2017 14:35 |
|---|---|---|---|
| Reporter: | Sean McDowell | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Package Repos | Severity: | S3 (Non-critical) |
| Version: | 7.5 | OS: | Linux |
| Assigned to: | Lars Tangvald | CPU Architecture: | Any |
[28 Jun 2017 19:09]
Sean McDowell
[29 Jun 2017 5:57]
MySQL Verification Team
Hi Sean, Thanks for the report. Looking at the https://github.com/mysql/mysql-docker/blob/mysql-cluster/7.5/docker-entrypoint.sh I see we are running custom user commands with exec but ndb* stuff without it. It might be a bug or intentional, I'm not 100% sure but I'll verify the bug and let our devs recheck the reasoning behind not using exec. I do agree that following docker policy we should be starting ndb(mt)d and rest of them with exec all best Bogdan Kecman
[29 Jun 2017 8:21]
Lars Tangvald
Posted by developer: The images should use exec for all the commands, yes. The cluster images are at an early experimental stage. We will rewrite them to be more in line with the server images (i.e. have the same features, with the cluster-specific commands added on top).
[17 Aug 2017 14:35]
Lars Tangvald
Posted by developer: The MySQL Cluster Docker images are now in line with the server images, functionality-wise.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.