eventing-natss cannot send messages after natss-streaming restarts

[wyyxd2017]

eventing-natss cannot send messages after natss-streaming restarts

[zhaojizhuang]

Hi, @wyyxd2017 can you show more log about natss-ch-dispatcher, Or steps to produce the problem

[wyyxd2017]

Hi, @wyyxd2017 can you show more log about natss-ch-dispatcher, Or steps to produce the problem

When I deployed eventing-natss for the first time, the message can be sent to the url specified by subspcription through the connection of natss. If I restart natss-streaming, I can only receive messages from the broker, but not send messages. I judged that natss-stream has established a new connection, but it is still sent through the old natss-streaming connection

[zhaojizhuang]

can you show the result of kubectl get broker,trigger,subscription,natschannel and the log of nats-ch-dispatcher pod ?

[wyyxd2017]

can you show the result of kubectl get broker,trigger,subscription,natschannel and the log of nats-ch-dispatcher pod ?

[wyyxd2017]

can you show the result of kubectl get broker,trigger,subscription,natschannel and the log of nats-ch-dispatcher pod ?

The second picture is the log after restart

[zhaojizhuang]

dispatcher has received and published events to the nats-streaming, as seen in the log。

cannot send messages to eventing.

And how do you find you can't send messages to eventing? And what's the eventing-natss version?

[wyyxd2017]

dispatcher has received and published events to the nats-streaming, as seen in the log。

cannot send messages to eventing.

And how do you find you can't send messages to eventing? And what's the eventing-natss version?

These three log pictures are the date of natss-ch-dispatcher.
, The first one is a normal log, with receiving messages and sending messages;
The second picture is the log of the error report after restarting natss-streaming;
The third picture is the log after restart. You can see that there are received logs but no sent logs

[zhaojizhuang]

The third picture is the log after restart. You can see that there are received logs but no sent logs

can you show the full yaml of natsschannel and subscripton?, no sent logs means there is no subscriber when dispatch https://github.com/knative-sandbox/eventing-natss/blob/8b49c6b39b23d8526137c200322edb509015a8ca/pkg/dispatcher/dispatcher.go#L292

[wyyxd2017]

The third picture is the log after restart. You can see that there are received logs but no sent logs

can you show the full yaml of natsschannel and subscripton?, no sent logs means there is no subscriber when dispatch

https://github.com/knative-sandbox/eventing-natss/blob/8b49c6b39b23d8526137c200322edb509015a8ca/pkg/dispatcher/dispatcher.go#L292

[zhaojizhuang]

@wyyxd2017 still have the problem?

[wyyxd2017]

@zhaojizhuang Yes. Because ReconcileKind will only execute once for the NatssChannel resource, during this execution it will subscribe and generate a subscription. If natss-streaming reconnects, the previous subscribe is no longer valid.