ChenSammi commented on PR #8360: URL: https://github.com/apache/ozone/pull/8360#issuecomment-2857213750
> > Good point to use the actual container size instead, but we don't know what the actual size is (when committing space) before actually downloading the container, right? > > Right, so I think that info should be brought in proto message. Agree. We can do this in a new JIRA. Generally, the tar zip file of container will have smaller size than it's real size, so reserve a 2* max container size is conservative enough in most cases. But there are container over-allocated case, where container size can be double or triple the max container size as @siddhantsangwan saw in user's environment, have a accurate container size can handle this case welly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org For additional commands, e-mail: issues-h...@ozone.apache.org
