[WRN] 127.0.0.1:56287 - cid:1 - Readloop processing time: 6.41977641s

[chaitanyav]

I am seeing this message in the nats streaming server log file. Can anyone explain what this means from the NATS streaming side.

[kozlovic]

You probably run NATS Streaming with an embedded NATS Server (the default). This message indicates that a go routine that reads data from a socket and then does some processing has spent a lot of time between 2 socket reads (processing content of the buffer).
Did you see any error prior to this warning?

[chaitanyav]

Thank you @kozlovic, I am running the NATS streaming with the embedded NATS server. I did not see any error prior to this warning, seeing this message sometimes.

[chaitanyav]

@kozlovic Is there a way to resolve this issue from the client-side or server using any option.

[kozlovic]

First you would have to narrow it down to what is triggering this warning. It could be that you start subscription with high MaxInflight? When a subscription starts and there are at least MaxInflight messages to be sent, the server will read all those messages and send them. If the storage access is slow, this could be an explanation for the warning you see.
You could try to run with -SD and see if there is any even prior to the warning that we can correlate to?

[chaitanyav]

@kozlovic thanks for the hint, setting the maxackinflight to 1 along with durable subscription helped. One more question for you is there a option to retry for the client to connect to the streaming server when the connection is closed

[kozlovic]

Not sure which client library you are using, but here is some background information regarding a streaming connection (https://github.com/nats-io/stan.go#connection-status). Note that the connection lost handler is not implemented in all supported libraries at this time.
Still, this does not offer an automatic "reconnect" and re-subscription. There is an issue in GH for that with some background too: nats-io/stan.go#273