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

nats streaming pod status as "Completed" #46

Open
nvcnvn opened this issue Jul 4, 2019 · 0 comments
Open

nats streaming pod status as "Completed" #46

nvcnvn opened this issue Jul 4, 2019 · 0 comments

Comments

@nvcnvn
Copy link

nvcnvn commented Jul 4, 2019

I'm running on my local minikube, it seem some how the pod gracefully shutdown:

kubectl get pods -n nats
NAME                                             READY   STATUS             RESTARTS   AGE
nats-operator-5b9df7cbb7-vmxt7                   1/1     Running            1          25h
nats-streaming-operator-66479b8d84-qwb2s         1/1     Running            1          25h
wistful-sponge-nast-streaming-nast-1             1/1     Running            0          8h
wistful-sponge-nast-streaming-nast-2             1/1     Running            0          8h
wistful-sponge-nast-streaming-nast-3             1/1     Running            0          8h
wistful-sponge-nast-streaming-nats-streaming-1   0/1     Completed          2          25h
wistful-sponge-nast-streaming-nats-streaming-2   0/1     Completed          1          25h
wistful-sponge-nast-streaming-nats-streaming-3   0/1     Completed          2          25h

Logs:

kubectl logs wistful-sponge-nast-streaming-nats-streaming-2 -n nats
[1] 2019/07/03 09:37:04.768787 [INF] STREAM: Starting nats-streaming-server[wistful-sponge-nast-streaming-nats-streaming] version 0.12.2
[1] 2019/07/03 09:37:04.768858 [INF] STREAM: ServerID: sdR75tHu4vdSxVG7yOHCci
[1] 2019/07/03 09:37:04.768861 [INF] STREAM: Go version: go1.11.6
[1] 2019/07/03 09:37:04.768863 [INF] STREAM: Git commit: [4489c46]
[1] 2019/07/03 09:37:04.786394 [INF] STREAM: Recovering the state...
[1] 2019/07/03 09:37:04.788582 [INF] STREAM: No recovered state
[1] 2019/07/03 09:37:04.788686 [INF] STREAM: Cluster Node ID : "wistful-sponge-nast-streaming-nats-streaming-2"
[1] 2019/07/03 09:37:04.788690 [INF] STREAM: Cluster Log Path: wistful-sponge-nast-streaming-nats-streaming/"wistful-sponge-nast-streaming-nats-streaming-2"
[1] 2019/07/03 09:37:06.837362 [INF] STREAM: Message store is RAFT_FILE
[1] 2019/07/03 09:37:06.837449 [INF] STREAM: Store location: store
[1] 2019/07/03 09:37:06.837537 [INF] STREAM: ---------- Store Limits ----------
[1] 2019/07/03 09:37:06.837571 [INF] STREAM: Channels:                  100 *
[1] 2019/07/03 09:37:06.837588 [INF] STREAM: --------- Channels Limits --------
[1] 2019/07/03 09:37:06.837668 [INF] STREAM:   Subscriptions:          1000 *
[1] 2019/07/03 09:37:06.837707 [INF] STREAM:   Messages     :       1000000 *
[1] 2019/07/03 09:37:06.837741 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2019/07/03 09:37:06.837757 [INF] STREAM:   Age          :     unlimited *
[1] 2019/07/03 09:37:06.837848 [INF] STREAM:   Inactivity   :     unlimited *
[1] 2019/07/03 09:37:06.837887 [INF] STREAM: ----------------------------------
[1] 2019/07/03 12:36:23.901524 [INF] STREAM: connection "_NSS-wistful-sponge-nast-streaming-nats-streaming-acks" reconnected to NATS Server at "nats://172.17.0.22:4222"
[1] 2019/07/03 12:36:23.906155 [INF] STREAM: connection "_NSS-wistful-sponge-nast-streaming-nats-streaming-general" reconnected to NATS Server at "nats://172.17.0.23:4222"
[1] 2019/07/03 12:36:23.913372 [INF] STREAM: Shutting down.

Is this issue of nats streaming operator?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant