Details
-
Improvement
-
Resolution: Fixed
-
Major
-
2.5.0, 3.0, 4.5.0, 4.6.0, 4.6.4, 4.6.3, 4.6.5, 5.0.0, 5.0.1, 5.5.0, 5.5.1
-
Security Level: Public
Description
This long-known architectural issue is that currently every operation is sent back in the order in which it had been received. Thus for a set of requests A, B, C, D, any background fetch latency on item B will also affect service times with C and D.
Existing memcached protocol does not state that operations must be handled in order, but owing to the one implementation doing so and all clients having been built/tested against that implementation, it's possible that there are erroneous dependencies on current behavior.
Attachments
Issue Links
- blocks
-
MB-23243 Support for High DGM use case for large datasets
- Closed
- causes
-
MB-37512 30% drop in transaction throughput in 7.0.0-1165 build for durability enabled cases
- Closed
- is duplicated by
-
MB-27090 Enable operations to complete out of order on a single application conneciton
- Closed
- relates to
-
MB-14423 Greenstack
- Resolved