-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Replace shutdownCh and wait groups to a y.Closer for shutting down Alpha #5560
Conversation
Can't we use y.Closer instead of shutdown channel? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR title needs to be fixed. I tried to manually verify this PR but we have another issue with shutdown #5627
Reviewable status: 0 of 4 files reviewed, all discussions resolved (waiting on @manishrjain, @MichaelJCompton, and @vvbalaji-dgraph)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 4 files at r1, 2 of 2 files at r2.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @MichaelJCompton and @vvbalaji-dgraph)
…pha (#5560) Earlier we had worker.ShutdownCh which was used to pass information between alpha/run.go and graphql/admin.go which was causing confusion and was being used to stop the worker itself. We now have a y.Closer in graphql/admin which manages the WaitGroup and passing of signals between goroutines using channels. Fixes DGRAPH-1169
…pha (hypermodeinc#5560) Earlier we had worker.ShutdownCh which was used to pass information between alpha/run.go and graphql/admin.go which was causing confusion and was being used to stop the worker itself. We now have a y.Closer in graphql/admin which manages the WaitGroup and passing of signals between goroutines using channels. Fixes DGRAPH-1169
Earlier we had
worker.ShutdownCh
which was used to pass information betweenalpha/run.go
andgraphql/admin.go
which was causing confusion and was being used to stop the worker itself. We now have ay.Closer
ingraphql/admin
which manages the WaitGroup and passing of signals between goroutines using channels.Fixes DGRAPH-1169
This change is