subscription problem

[fztcjjl]

When the service is disconnected from the messaging system, the subscription needs to be resubscribed after reconnection. So there should be provide a way to resubscribe topic.

[vtolstov]

This is not simple, because we need to store topic and options for subscription..
I'm need to think about this more

[fztcjjl]

topic and subscription options has already stored in server。
eg.

go-micro/server/rpc_server.go

Line 29 in 95b8147

subscribers map[*subscriber][]broker.Subscriber

[vtolstov]

Reconnect happens inside broker client in broker implementstion. So for nats you dont need anything,after client reconnect it resubscribes. But for stan you need to subscribe again inside broker implementation. сб, 8 июн. 2019 г., 18:07 fztcjjl <[email protected]>:

…

subsription options has already stored in server。 eg. https://github.com/micro/go-micro/blob/95b8147fa12f0ac6b1df644a1a864325c86a015d/server/rpc_server.go#L29 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#503?email_source=notifications&email_token=AADVQG3G3ESCSU44OOAHJVTPZPDKHA5CNFSM4HWDJG32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXHWL3I#issuecomment-500131309>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADVQG2LZ6U4KZTWON4D2Y3PZPDKHANCNFSM4HWDJG3Q> .

[vtolstov]

i think that we need to fix this in stan broker in nats-io/stan.go repo (as devs says in slack nats already resubscribe after reconnect)

[vtolstov]

i'm create issue to stan.go nats-io/stan.go#273

[asim]

Marking this as a non-fix for now. The complexity of managing reconnection and resubscription is quite tough, especially across pluggable tooling.

[vtolstov]

i think before closing this issue we need to document current behavior and add some stuff to development repo as issue?

[asim]

Closing this is fine. Add to development repo if needed. But otherwise it's fairly complex and difficult to implement across all brokers.