Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dgraph Alpha does not shutdown when signaled to when it has not yet joined a cluster #4035

Closed
danielmai opened this issue Sep 20, 2019 · 1 comment
Labels
area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. kind/bug Something is broken. priority/P3 Low priority, something to be done once everything else seems fixed. status/accepted We accept to investigate/work on it.

Comments

@danielmai
Copy link
Contributor

danielmai commented Sep 20, 2019

What version of Dgraph are you using?

v1.1.0

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, OS)?

N/A

Steps to reproduce the issue (command/config used to run Dgraph).

  1. Run Dgraph Alpha with no Zero running.

    dgraph alpha
    
  2. Press Ctrl-C (SIGINT) or send a SIGTERM to the Alpha process. The Alpha will show these logs, closing the gRPC and HTTP ports:

    ^CI0920 15:47:54.818842   10214 run.go:547] Caught Ctrl-C. Terminating now (this may take a few seconds)...
    E0920 15:47:54.818949   10214 run.go:331] GRPC listener canceled: accept tcp [::]:9080: use of closed network connection
    E0920 15:47:54.819126   10214 run.go:350] Stopped taking more http(s) requests. Err: accept tcp [::]:8080: use of closed network connection
    I0920 15:47:54.819443   10214 run.go:566] GRPC and HTTP stopped.
    
  3. The Alpha process stays idle indefinitely.

Expected behaviour and actual result.

Dgraph Alpha should shut down properly even if it hasn't yet been assigned to a group.

The actual result is that the Alpha process continues running unless it is forcibly shutdown with three Ctrl-C's or forcibly killed by SIGKILL.

This is a low priority issue. Fixing this would be a small operational enhancement.

@danielmai danielmai added kind/bug Something is broken. priority/P3 Low priority, something to be done once everything else seems fixed. status/accepted We accept to investigate/work on it. area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. labels Sep 20, 2019
@minhaj-shakeel
Copy link
Contributor

Github issues have been deprecated.
This issue has been moved to discuss. You can follow the conversation there and also subscribe to updates by changing your notification preferences.

drawing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. kind/bug Something is broken. priority/P3 Low priority, something to be done once everything else seems fixed. status/accepted We accept to investigate/work on it.
Development

No branches or pull requests

2 participants