You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/02 23:41:58 UTC
[jira] [Commented] (TRAFODION-2384) Trafodion node needs to be
gracefully shutdown when the node is brought down
[ https://issues.apache.org/jira/browse/TRAFODION-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716875#comment-15716875 ]
ASF GitHub Bot commented on TRAFODION-2384:
-------------------------------------------
GitHub user selvaganesang opened a pull request:
https://github.com/apache/incubator-trafodion/pull/862
[TRAFODION-2384] Trafodion node needs to be gracefully shutdown when …
…the node is brought down
Added a service script for Trafodion at $MY_SQROOT/sysinstall/etc/init.d/trafodion.
As part of cluster install, this file will be copied to /etc/init.d and
configured for service startup.
The service script has the support for stop and status only.
You can do the following:
bin]$ sudo service trafodion status
trafodion on node kenai01.cluster.local is started as logical node 000
bin]$ sudo service trafodion stop
Stopping trafodion node 000 on kenai01.cluster.local
bin]$ sudo service trafodion status
trafodion on node kenai01.cluster.local is not yet started
bin]$ sudo service trafodion start
start: missing job name
Try `start --help' for more information.
This allows init 6, shutdown and reboot to execute the trafodion services to be stopped in
correct sequence. Hence, it should fix the core dumps seen at the time of node shutdown.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/selvaganesang/incubator-trafodion trafodion-2384
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/862.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #862
----
commit af9524e686b1e0fcfc8a192b0b6b7c971a8ec77c
Author: selvaganesang <se...@esgyn.com>
Date: 2016-12-02T23:16:18Z
[TRAFODION-2384] Trafodion node needs to be gracefully shutdown when the node is brought down
Added a service script for Trafodion at $MY_SQROOT/sysinstall/etc/init.d/trafodion.
As part of cluster install, this file will be copied to /etc/init.d and
configured for service startup.
The service script has the support for stop and status only.
You can do the following:
bin]$ sudo service trafodion status
trafodion on node kenai01.cluster.local is started as logical node 000
bin]$ sudo service trafodion stop
Stopping trafodion node 000 on kenai01.cluster.local
bin]$ sudo service trafodion status
trafodion on node kenai01.cluster.local is not yet started
bin]$ sudo service trafodion start
start: missing job name
Try `start --help' for more information.
This allows init 6, shutdown and reboot to execute the trafodion services to be stopped in
correct sequence. Hence, it should fix the core dumps seen at the time of node shutdown.
----
> Trafodion node needs to be gracefully shutdown when the node is brought down
> ----------------------------------------------------------------------------
>
> Key: TRAFODION-2384
> URL: https://issues.apache.org/jira/browse/TRAFODION-2384
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: installer
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
> Fix For: 2.1-incubating
>
>
> When a node in a Trafodion cluster is brought down using linux commands like shutdown, init 6 and reboot, the trafodion processes need to be stopped before the underlying the stack is stopped. Otherwise, some of the processes can dump core which are being restarted as part of the persistence concept of Trafodion. RMS processes, TM are examples of such persistence processes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)