Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trello Card Link
https://trello.com/c/dyViGxGG/1654-track-upload-errors
Description
We see this error occasionally, but both disk space and inode usage seems fine. Since it is causing uploads to fail, we should try to log it out as soon as an operation fails in case this is a transient error.
Edit: My gut take as to the root cause is that large uploads/many concurrent uploads cause some file system inode limit or something because of https://github.com/AudiusProject/audius-protocol/blob/master/creator-node/src/routes/tracks.js#L73-L77. We do promise.all to move all the segments around. I feel like chunking may alleviate this problem.
Services
Does it touch a critical flow like Discovery indexing, Creator Node track upload, Creator Node gateway, or Creator Node file system?
Delete an option.
How Has This Been Tested?
Uploaded tracks locally to verify it worked with this change.
Then threw a ENOSPC error manually and observed if it printed the output