Replies: 3 comments 2 replies
@yhrn if can do rolling update on one vertex at a time, this problem can be solved right? |
1 reply
It is something we plan to do, we have an issue for that #1677. Could you please take a look and let me know whether it makes sense to you? |
1 reply
|
https://numaflow.numaproj.io/user-guide/reference/ordered-processing/ is available in the nightly build. Please try it out and let us know. You can find an example in https://github.com/numaproj/numaflow/blob/main/examples/41-ordered-processing.yaml. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We are interested in having sink partitioning. Our use case is to maintain per key ordering at the sink after a partitioned reducer and still be able to have more than one sink pod. We want multiple sink pods so that we can roll out updates without completely stopping the pipeline output during the update, since this causes spikes in overall resource usage when catching up.
Manual partitioning is not practical as we can't easily control a rolling update across multiple vertices.
So we're hoping that this would be a feature that you would consider for Numaflow and that we can discuss the details implications here.
Original question on Slack @vigith
All reactions