You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User A uploads any other file to any shuttle or API node
content gets pinned on selected node, but gets added to the staging zone located on shuttle 1
consolidation of staging zone on shuttle 1 will fail until shuttle 1 is back online
Expected behavior
in (4), if the file is big enough for dealmaking on its own, it should not be added to a staging zone at all. if it is not big enough for dealmaking, a new staging zone on an alive node should be created. if the upload is done directly to a shuttle, the staging zone should be made on that shuttle. if it's through the api node, an alive shuttle with the largest existing staging zone for that user should be selected
The text was updated successfully, but these errors were encountered:
Describe the bug
Expected behavior
in (4), if the file is big enough for dealmaking on its own, it should not be added to a staging zone at all. if it is not big enough for dealmaking, a new staging zone on an alive node should be created. if the upload is done directly to a shuttle, the staging zone should be made on that shuttle. if it's through the api node, an alive shuttle with the largest existing staging zone for that user should be selected
The text was updated successfully, but these errors were encountered: