Why a Numaflow watermark wouldn’t move
I started looking into issue #3645 in Numaflow, a Kubernetes-native stream processing platform, because of a workaround that seemed odd. The pipeline was still processing messages. The vertices were healthy, and there were no errors in the logs. But pipeline_processing_lag kept growing, first for hours and then for days. The accumulator vertex’s watermark wasn’t The reporter, th0ger, was using Numaflow 1.8.3 with Python SDK 0.14.0.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in