Concurrency (thread) does not work as expected
seems there is reentrence issues with http-based objstorage backends (http, seaweedfs) and azure backend preventing from taking advantage of the multithreading implementation of the content replayer.
Staging instance, all changes can be removed at any time
seems there is reentrence issues with http-based objstorage backends (http, seaweedfs) and azure backend preventing from taking advantage of the multithreading implementation of the content replayer.