Kenn Knowles
Kenn Knowles
Gya I missed one ;_;
Just for posterity and everyone else getting notifications. As release manager I learned just now that we need a tickets such as this whenever we add a new version: https://issues.apache.org/jira/browse/INFRA-25880...
Permared now
Thanks for reporting this. Those four error messages are from the service's point of view (after 4 it fails a batch job). I wonder if we see a crash loop...
So to summarize, we could check these configurations: - Old reshuffle, v1: known good - Old reshuffle, v2: test this with 2.53.0 and `--experiments=use_runner_v2` - New reshuffle, v1: test this...
Alright, thank you so much for isolating this! We would love to be able to minimally reproduce it and fix it. From the lack of error, it may be a...
One thing occurred to me: the entire stage after the shuffle failed. From the error message, this stage includes a fusion of many steps that are not part of the...
Easy to test: you can comment out the BQ write and see if you still reproduce the error.
Through Google's Cloud Support channels you can get someone who can really dig in to the details of the logs and the metrics. But from an outside perspective, doing some...
And just to check - it succeeded on runner v2? So then it could be the BigQuery write or it could be an interaction of the fused steps.