Is there any difference between “restart” and “stop/start” for MariaDB (MySQL)?












0














I had a table crashed in MariaDB and it stopped responding while MariaDB was trying to repair crashed table automatically, and the repairing process seemed to be consuming server resource. I tried to restart MariaDB with "restart" command, but it took longer than usual and after restarting, the repairing process seemed to be still active and MariaDB still was not responding. Then I restarted MariaDB again with "stop" and "start" command, MariaDB stopped and started without taking so long time. After the second restarting, repairing process seemed to be stopped and the main service restored (the main service works without crashed table). I wonder "restart" command does not kill repairing process but "stop" command does. Is that right? Does anyone have idea about the difference of those commands? I use MariaDB 5.5.56 on CentOS 7.










share|improve this question






















  • Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
    – Rick James
    Nov 20 at 4:01
















0














I had a table crashed in MariaDB and it stopped responding while MariaDB was trying to repair crashed table automatically, and the repairing process seemed to be consuming server resource. I tried to restart MariaDB with "restart" command, but it took longer than usual and after restarting, the repairing process seemed to be still active and MariaDB still was not responding. Then I restarted MariaDB again with "stop" and "start" command, MariaDB stopped and started without taking so long time. After the second restarting, repairing process seemed to be stopped and the main service restored (the main service works without crashed table). I wonder "restart" command does not kill repairing process but "stop" command does. Is that right? Does anyone have idea about the difference of those commands? I use MariaDB 5.5.56 on CentOS 7.










share|improve this question






















  • Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
    – Rick James
    Nov 20 at 4:01














0












0








0







I had a table crashed in MariaDB and it stopped responding while MariaDB was trying to repair crashed table automatically, and the repairing process seemed to be consuming server resource. I tried to restart MariaDB with "restart" command, but it took longer than usual and after restarting, the repairing process seemed to be still active and MariaDB still was not responding. Then I restarted MariaDB again with "stop" and "start" command, MariaDB stopped and started without taking so long time. After the second restarting, repairing process seemed to be stopped and the main service restored (the main service works without crashed table). I wonder "restart" command does not kill repairing process but "stop" command does. Is that right? Does anyone have idea about the difference of those commands? I use MariaDB 5.5.56 on CentOS 7.










share|improve this question













I had a table crashed in MariaDB and it stopped responding while MariaDB was trying to repair crashed table automatically, and the repairing process seemed to be consuming server resource. I tried to restart MariaDB with "restart" command, but it took longer than usual and after restarting, the repairing process seemed to be still active and MariaDB still was not responding. Then I restarted MariaDB again with "stop" and "start" command, MariaDB stopped and started without taking so long time. After the second restarting, repairing process seemed to be stopped and the main service restored (the main service works without crashed table). I wonder "restart" command does not kill repairing process but "stop" command does. Is that right? Does anyone have idea about the difference of those commands? I use MariaDB 5.5.56 on CentOS 7.







mysql mariadb






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 1:40









Sekine

1




1












  • Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
    – Rick James
    Nov 20 at 4:01


















  • Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
    – Rick James
    Nov 20 at 4:01
















Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
– Rick James
Nov 20 at 4:01




Both approaches may find different things to do, hence take more or less time. If you are using MyISAM, switch to InnoDB.
– Rick James
Nov 20 at 4:01












1 Answer
1






active

oldest

votes


















0














If you systemctl show mysql.service it should list the Exec{Start/Stop/Reload} settings for this service.



journalctl -u mysql.service will list the actions taken.






share|improve this answer





















  • Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
    – Sekine
    Nov 20 at 4:55













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385056%2fis-there-any-difference-between-restart-and-stop-start-for-mariadb-mysql%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














If you systemctl show mysql.service it should list the Exec{Start/Stop/Reload} settings for this service.



journalctl -u mysql.service will list the actions taken.






share|improve this answer





















  • Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
    – Sekine
    Nov 20 at 4:55


















0














If you systemctl show mysql.service it should list the Exec{Start/Stop/Reload} settings for this service.



journalctl -u mysql.service will list the actions taken.






share|improve this answer





















  • Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
    – Sekine
    Nov 20 at 4:55
















0












0








0






If you systemctl show mysql.service it should list the Exec{Start/Stop/Reload} settings for this service.



journalctl -u mysql.service will list the actions taken.






share|improve this answer












If you systemctl show mysql.service it should list the Exec{Start/Stop/Reload} settings for this service.



journalctl -u mysql.service will list the actions taken.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 20 at 2:41









danblack

1,5071214




1,5071214












  • Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
    – Sekine
    Nov 20 at 4:55




















  • Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
    – Sekine
    Nov 20 at 4:55


















Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
– Sekine
Nov 20 at 4:55






Thank you for your reply. I checked the setting by "systemctl show mariadb.service", but there were only ExecStart and there wasn't ExecStop or ExecReload. I checked log by "journalctl -u mariadb.service", after "restart" and "stop/start", the messages for those commands were a bit different. For "restart", (Stopping MariaDB..., Starting MariaDB... and Started MariaDB) instead of (Stopping MariaDB..., Stopped MariaDB..., Starting MariaDB... and Started MariaDB) for "stop/start". I am not sure the difference between those messages means the difference of the actions or not. Thanks anyway.
– Sekine
Nov 20 at 4:55




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385056%2fis-there-any-difference-between-restart-and-stop-start-for-mariadb-mysql%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

Origin of the phrase “under your belt”?