Skip to content
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

Missing index columns after upgrade to dask-expr #1144

Open
aimran-adroll opened this issue Oct 10, 2024 · 0 comments
Open

Missing index columns after upgrade to dask-expr #1144

aimran-adroll opened this issue Oct 10, 2024 · 0 comments

Comments

@aimran-adroll
Copy link

Not sure if this qualifies as bug report or not. But we recently bumped dask (2023.12.0 -> 2024.9.1). We are now running into quite a bit of crashes involving missing index keys (usually preceded by read parquet + a bunch of groupby agg/apply).

Here is an example error msg:
KeyError: "None of [Index(['advertisable_eid', 'user', 'subset_id'], dtype='object')] are in the [columns]"

If I step through the code, I can see where its failing. But if I dump out the columns, the dataframe spits out the right columns. Debugging is complicated by the fact that the job only crashes on distributed workload (for now).

Curiously, adding a few strategic df = df.optimize() right after the groupby operation mysteriously resolves the issue. I only accidentally came across the solution and have no idea why it helps.

I am filing it here because the crash logs are filled with calls to this module (esp the fuse step). If there are any tips or tricks to get more debugging traces out of the system, kindly share 🙏🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant