fix(GraphQL): Update GraphQL schema only on Group-1 leader (#5739) #5829
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #GRAPHQL-364.
This PR changes the way how GraphQL schema is updated. From now on, every request to update the GraphQL schema will be executed on Group-1 leader, instead of on the alpha which received the request. This helps solve some concurrency issues during GraphQL schema update.
(cherry picked from commit f4cd0b3)
# Conflicts:
# graphql/admin/schema.go
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)
Docs Preview:![Dgraph Preview](https://camo.githubusercontent.com/9ee6c980b1dc809eae7968795cd3b3a0f6417b3a82de6d87eb08695b223273d7/68747470733a2f2f626c2e6f636b732e6f72672f7072617368616e742d73686168692f7261772f33613966393962656338343233316366653363306538326366383833663135392f306535383864393038616438633862313039353862383765626464326261363837373963636634662f6467726170682e737667)