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

Bytewax materializer materializes entire dataset on every pod #3786

Closed
james-crabtree-sp opened this issue Oct 9, 2023 · 0 comments · Fixed by #3789
Closed

Bytewax materializer materializes entire dataset on every pod #3786

james-crabtree-sp opened this issue Oct 9, 2023 · 0 comments · Fixed by #3789

Comments

@james-crabtree-sp
Copy link
Contributor

Expected Behavior

Each pod should materialize a separate batch of data

Current Behavior

Every pod redundantly materializes the entire dataset, causing a massive overspend on processing time and database writes

Steps to reproduce

Observed with snowflake offline store and dynamo db online store. Materialize a feature with enough records for the snowflake s3 integration to output multiple files. View the logs of each pod and add up the total records materialized. Observe that every pod has materialized the entire dataset

Specifications

  • Version: 0.31
  • Platform: fedora linux
  • Subsystem: bytewax batch_engine

Possible Solution

Use JOB_COMPLETION_INDEX in each pods dataflow to select a single file to process

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