Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Daemonize etcd #66

Closed
atinmu opened this issue Jan 12, 2016 · 0 comments
Closed

Daemonize etcd #66

atinmu opened this issue Jan 12, 2016 · 0 comments
Assignees

Comments

@atinmu
Copy link
Contributor

atinmu commented Jan 12, 2016

etcd instance can't be brought down when glusterd goes down since the other consumers like NSR would still be able to access it. This task is to have etcd daemonized such that on glusterd shutdown etcd instance doesn't go down.

gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 21, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 25, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing previous commit comments.

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 29, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 29, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing previous commit comments.

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 29, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing previous commit comments.

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 29, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing some minor typo issue

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 29, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing some minor issue in unit text case

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 30, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing some minor issue in unit text case and etcd restart case

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Jan 30, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Fixing some minor issue in unit text case

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
gaurav36 added a commit to gaurav36/glusterd2 that referenced this issue Feb 1, 2016
Currently when etcd daemon start upon starting of glusterd2 then upon
performing ^C (SIGINT) its killing etcd daemon.

With this patch it will set child process id to different from main
process id group and, etcd daemon will not be kill upon performing
SIGINT (^C) of main process.

Addressing previous commit comment

Issue gluster#66

Signed-off-by: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Signed-off-by : Atin Mukherjee <amukherj@redhat.com>
atinmu pushed a commit to atinmu/glusterd2 that referenced this issue Feb 8, 2016
Closes gluster#66

Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
@atinmu atinmu self-assigned this Feb 8, 2016
@atinmu atinmu closed this as completed in #78 Feb 9, 2016
@atinmu atinmu removed the in progress label Feb 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant