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
After #16929, MonitoredSteramingUploader will only be used by OpenDAL object store. However, the reporting metrics are not exactly what we want because I/O may or may not happen on opendal writer write calls and the I/O scheduling is done inside the implementation of opendal writer.
However, after apache/opendal#4638, whenever a I/O happens in the opendal writer, it will invoke the execute method provided by the Executor implemented by us. We should monitor I/O metrics in the Executor and deprecate the outer MonitoredStreamingUploader completely.
The text was updated successfully, but these errors were encountered:
After #17198, the metrics related to streaming uploader has already been moved into opendal object store. I will try to see whether we can completely deprecate MonitoredSteramingUploader.
After #16929,
MonitoredSteramingUploader
will only be used by OpenDAL object store. However, the reporting metrics are not exactly what we want because I/O may or may not happen on opendal writer write calls and the I/O scheduling is done inside the implementation of opendal writer.However, after apache/opendal#4638, whenever a I/O happens in the opendal writer, it will invoke the
execute
method provided by theExecutor
implemented by us. We should monitor I/O metrics in theExecutor
and deprecate the outer MonitoredStreamingUploader completely.The text was updated successfully, but these errors were encountered: