Open TheCheshireFox opened 3 months ago
@TheCheshireFox could you share an example of how you are purging the stream?
Sure. We use this method:
public ulong PurgeStream(string streamName, string subject, CancellationToken cancellationToken)
{
var optionsBuilder = new PurgeOptions.PurgeOptionsBuilder();
optionsBuilder.WithSubject(subject);
var response = JetStreamManagement.PurgeStream(streamName, optionsBuilder.Build()); // JetStreamManagement has a type IJetStreamManagement
return response.Purged;
}
@wallyqs, any news? Maybe I can provide more information?
Observed behavior
So far, for unknown reasons, the stream and ack floor sequence goes further away than the message sequence. This leads to some messages not being delivered.
In the same time we have this lines in logs:
Expected behavior
All messages in a stream must be delivered.
Server and client version
nats-server: v2.10.17 dotnet nats-client: 1.0.4
Host environment
os: Windows Server 2019 Standard arch: x64 ram: 6 Gb
Steps to reproduce
I'm not sure what the steps to reproduce are, but we got such a problem for the message we NAK on the stream we actively purging.