Occasionally we see users run into issues when changes are made to more files than the standard limit of 10,000. This can apply to all versions of Domino.
Here's an example of one such error we pulled from workspace logs:
2022-06-16T23:25:56.774Z: Received request to finish run 62abb58e1253f129da704b2c with exit code 143
2022-06-16T23:26:04.307Z: Domino tried to save 29447 files from your run but failed because this was above the save limit of 10000 files.
You can generate fewer files or use .dominoignore to tell Domino to ignore certain files and directories.
If you are trying to store a large dataset, you can improve performance by using the Datasets functionality.
See the Dataset documentation here: https://support.dominodatalab.com/hc/en-us/articles/360020125052
2022-06-16T23:26:15.366Z: Caught termination signal!
2022-06-16T23:26:15.366Z: -- killed by pod termination --
Note: If you have not made these files changes in the current session, they may be changes left over from previous session (which was not sync'ed) or a script running within your run/workspace. Before doing a full sync you may want to check your files to verify that you want to save their current state.
To override this error, please contact your local admin. They'll need to adjust this setting under the central config within the admin console:
com.cerebro.domino.executor.syncFileCountLimit |
Please note they'll need to restart frontend services before the change can take effect. This change can be made temporarily to allow a single user or admins can choose to keep this setting in place.
Comments
0 comments
Please sign in to leave a comment.