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

[Data] Add Datasource.on_write_start #38298

Merged
merged 18 commits into from
Aug 14, 2023
Merged

Conversation

bveeramani
Copy link
Member

Why are these changes needed?

Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Related issue number

Fixes #36690

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
@ericl
Copy link
Contributor

ericl commented Aug 10, 2023 via email

@bveeramani
Copy link
Member Author

@c21 Here's the currently failing test:

  | # Ensure that directory was created for only the non-empty dataset.
  | if fs is None:
  | assert not os.path.isdir(all_empty_path)
  | assert os.path.isdir(some_empty_path)
  | # Only files for the non-empty blocks should be created.
  | file_list = os.listdir(some_empty_path)
  | file_list.sort()
  | assert file_list == [
  | f"{some_empty_key}_00000{i}_000000.parquet" for i in range(2)
  | ]
  | else:
  | >           assert (
  | fs.get_file_info(_unwrap_protocol(all_empty_path)).type
  | == pa.fs.FileType.NotFound
  | )
  | E           assert <FileType.Directory: 3> == <FileType.NotFound: 0>
  | E             +<FileType.Directory: 3>
  | E             -<FileType.NotFound: 0>
  |  
  | python/ray/data/tests/test_parquet.py:861: AssertionError

…te-start

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Copy link
Contributor

@c21 c21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change with on_write_start LGTM. As discussed offline, let's delete the staging directory if no file is written.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
…oject/ray into bveeramani/on-write-start

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Appease lint

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Add unit tests

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Appease lint

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Remove extra files

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Remove unnecessary file

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Update BUILD

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Rename `created_dir` to `has_created_dir`

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
@bveeramani bveeramani merged commit 993c131 into master Aug 14, 2023
50 of 53 checks passed
@bveeramani bveeramani deleted the bveeramani/on-write-start branch August 14, 2023 23:52
NripeshN pushed a commit to NripeshN/ray that referenced this pull request Aug 15, 2023
Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: NripeshN <nn2012@hw.ac.uk>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: harborn <gangsheng.wu@intel.com>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
Currently, we attempt to create a directory in every write task. This can cause rate limiting issues with S3. To address this problem, this PR adds a on_write_start method that is executed once per write job.

Signed-off-by: Balaji Veeramani <balaji@anyscale.com>
Signed-off-by: Victor <vctr.y.m@example.com>
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

Successfully merging this pull request may close these issues.

[Data] SLOW_DOWN AWS error when writing to S3
3 participants