Yashash H L

I think this was fixed in - https://github.com/numaproj/numaflow/pull/1613

sharing some of the interesting blogs that I found related to managing the proto files https://www.bugsnag.com/blog/libraries-for-grpc-services https://www.crowdstrike.com/blog/improving-performance-and-reliability-of-microservices-communication-with-grpc/ https://medium.com/namely-labs/how-we-build-grpc-services-at-namely-52a3ae9e7c35

@QuentinFAIDIDE Thanks for sharing detailed info and steps to reproduce this issue. I've been able to do the same and understand what's causing the data loss. Here's what's happening: We've...

Yes, correct. Once the `maxMsgs` limit has been set and the stream passes the allowed limit (100k in our case), the older messages will be discarded irrespective of the policy....

Thank you for raising this issue. We'll prioritize this promptly.

`DiscardNew` only works with the `workQueue` policy, we cannot use the limits policy with `DiscardNew` in our use case. But when I was testing `DiscardNew` with the `workQueue` policy, I...

When the stream is configured with the `Limits` policy and `DiscardOld`, Jetstream will automatically delete old messages if either the maxMsgs limit of 100k or the maxAge limit of 72h...