yoshiyuki.kanno
yoshiyuki.kanno
noticed when I checked notes today. It's a bit cumbersome to check whether the performance degradation occurred or not at a first glance.
With #671, we can include the compaction related info in https://github.com/leo-project/leofs_doctor when the target node is leo_storage.
In order to avoid overlooking this kind of issues like https://github.com/leo-project/leofs/issues/702.
especially for operation mistakes. ### how to implement As we already have a diagnose which is able to retrieve offsets to a metadata, body of every object, we can retrieve...
### Background We have a bit complicated conf file for http://leo-project.net/leofs/docs-old/admin_guide/admin_guide_11.html. So it would be good to have a feature to do conf test like `nginx -t` and also show...
(IIRC, this kind of benchmarks is not conducted regularly.) With the fix for https://github.com/leo-project/leofs/issues/642, As leo_gateway(s) have to ping both managers every time in case handling object operations via s3...
In order to detect concurrency errors systematically. Reference: https://github.com/parapluu/Concuerror
Not to overlook kinda #586 . Also maybe adding the feature that enumerating the all keys in conf and check whether their key name really exist or not would be...
Details are described here https://github.com/leo-project/leo_object_storage/pull/22#issuecomment-358161292. It would be good to set m_EleveldbThreads to the number of AVS files rather than the default(71) to avoid IO tasks being enqueued on eleveldb...
Details are described here https://github.com/leo-project/leofs/issues/725#issuecomment-305393080. In order to make such stuck happen as less times as possible, we can make a request to a gen_server more scalable/responsive in specific cases...