wardlican commented on issue #3855: URL: https://github.com/apache/amoro/issues/3855#issuecomment-3552199527
> [@wardlican](https://github.com/wardlican) I couldn't reproduce this scenario. I think the main issue is related to the data; the inaccurate calculation of the Writer's scroll size is causing this phenomenon. > > In your scenario, Binpack is using the size of `self-optimizing.max-task-size-bytes` instead of `self-optimizing.target-size`. > > If possible, try setting `self-optimizing.max-task-size-bytes` to match `self-optimizing.target-size` (50KB). Using self-optimizing.max-task-size-bytes does not solve this problem. We also encountered this issue in our production environment. The default values for both target and self-optimizing.max-task-size-bytes are 128MB. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
