-
Notifications
You must be signed in to change notification settings - Fork 74.2k
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
Using tf.data.Dataset.list_files prints "unshardable source dataset" warning #55474
Comments
Hello @dmho418 , Example mentioned in https://www.tensorflow.org/tutorials/distribute/input#sharding demonstrates how to set the sharding policy:
This will work as long as the dataset starts with list of files. If the dataset doesn't start with list of files, you will face an error along the lines of |
Hi @tilakrayal From https://www.tensorflow.org/tutorials/distribute/input#sharding doesn't that mean that the default policy AUTO would shard by FILE automatically if a file-based dataset is detected? In #45157 (comment) I think it's a different issue. There the user manually iterating the dataset and passing tensors to |
When the |
Thanks @sachinprasadhs, I think I misunderstood the documentation. On the distributed input tutorial it says:
Which seems to imply that a tensorflow/tensorflow/core/grappler/optimizers/data/auto_shard.cc Lines 132 to 138 in e6ba479
|
@dmho418 , If your issue is resolved, could you please close this issue. Thanks! |
This issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Thank you. |
Closing as stale. Please reopen if you'd like to work on this further. |
System information
Describe the current behavior
Using distributed strategy and
tf.data.Dataset.list_files
prints aunshardable source dataset
warning.Describe the expected behavior
API should detect that the source dataset is files and can be sharded.
Reference: https://www.tensorflow.org/tutorials/distribute/input
Standalone code to reproduce the issue
The text was updated successfully, but these errors were encountered: