-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After changes thats fixes 25151 issue facing problems with java.lang.IllegalStateException: task ... already marked as finished #25217
Comments
@losipiuk ptal |
After I removed the retry-policy, the errors stopped, but everything worked stably on previous versions. |
Having the same issue with 471, trino in k8s, iceberg with s3 and glue. Occurs 100% when running alter table execute optimize on a large table. Is there anything I could help with? E.g. logs / test other versions? |
We are also experiencing this issue, hard to pin down, but happens when we have large queries that call slow functions, and retry-policy task. |
@grumbler do you have log lines starting with
In your logs? I expect you have. Can you quote those? I have high confidence I know which new code path you are hitting. But not sure yet what is the root cause. |
Also can you build version from #25333 and see how it looks like there. I would expect that it would still fail - but probably with more reasonable error message. Probably we will need to tweak one timeout too. |
@wufh43 How long do the functions run? Also can you look into logs and see if you have anything with |
@Albel-Analyst yeah - issue is FTE specific. Would you be able to build from #25333 and see how it behaves? |
@losipiuk sure, let me spin up a test instance on 472 and grab the logs. Yep, I have quite a lot of those
From the client side:
build from MR - I won't have time for that until next week, unfortunately. |
Thanks. Would you be fine with sharing query text and plan (Output of EXPLAIN ...)? Can be stripped from any parts you see sensitive of course. |
Sure! I've replaced catalogName.schemaName.tableName with
explain:
|
I am facing a problem after building from current master branch. There was no such problem on 471, but I had to build from master because of this issue. #25151
Now, periodically I encounter this problem.:
If it's important, then I use
connector.name=iceberg
iceberg.catalog.type=rest
retry-policy=TASK
The text was updated successfully, but these errors were encountered: