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

Investigate why we sometimes have multiple pods per gameserver #490

Closed
jkowalski opened this issue Jan 17, 2019 · 0 comments · Fixed by #565
Closed

Investigate why we sometimes have multiple pods per gameserver #490

jkowalski opened this issue Jan 17, 2019 · 0 comments · Fixed by #565
Labels
kind/bug These are bugs.
Milestone

Comments

@jkowalski
Copy link
Contributor

During large cluster turnup I ran into this:

$ kubectl get gs
NAME                     STATE          ADDRESS   PORT   NODE   AGE
simple-udp-sv722-gj985   RequestReady                           27m
simple-udp-sv722-m7rk2   RequestReady                           27m

$ kubectl get pod
NAME                           READY   STATUS    RESTARTS   AGE
simple-udp-sv722-gj985-csgr7   2/2     Running   0          27m
simple-udp-sv722-gj985-rw6p7   2/2     Running   0          27m
simple-udp-sv722-m7rk2-g8rn8   2/2     Running   0          27m
simple-udp-sv722-m7rk2-q44mm   2/2     Running   0          27m

In a large turnup (10K GS) this reproes quite often - typically one or two of the GS get stuck in this state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug These are bugs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants