Lathanderjk

Zero progress was actually because of dynamic sync-rate controller, after switching off congestion control resync start but never finished either. After setting fixed rate "c-plan-ahead 0 and "resync-rate 50M" everything...

Same issue.

Of course i expected performance drop an I/O increase but not thousand times... or 3-4000x

I only asking if this is intended and there no room for some grouping and reducing fsync calls. One block write to file with dd is causing 6 writes by...

Grouping fsync mean less security thats true but for single operation before sending OK to client? In this scenario losing one fsync would by just forcing client to retry operation?...

In my test setup i use DRBD to replicate medata (B protocol an RDMA transport) and manage moosefs master via pacemaker cluster manager to create HA setup. CHANGELOG SAVE MODE=2...

Would be amazing if this finally was added. Using just HA(single master+replicas) setup, managed by sentinel or pacemaker is not very scalable.

I have similar problem on RHEL 9, it's probably caused by unexpected eof. I tried to block access to OpenSSL 3 library forcing libmsodbcsql use OpenSSL 1.1 (for compat-openssl11 package)...

It will be very nice also build it with http3 experimental support, maybe even OpenSSL(or QuicTLS) 3.1 with KTLS enabled. Openssl 1.1 is EOL since 11th September 2023.

Any news?, HTTP 3 is on 1/3 website and openresty has no support for it. Also nginx 1.27.0 is out for few weeks now, HTTP/3 support should be mature enough...