Avi Kivity d5050e4c6a storage_proxy: make MUTATION and MUTATION_DONE verbs sychronous at the server side ...

While MUTATION and MUTATION_DONE are asynchronous by nature (when a MUTATION
completes, it sends a MUTATION_DONE message instead of responding
synchronously), we still want them to be synchronous at the server side
wrt. the RPC server itself.  This is because RPC accounts for resources
consumed by the handler only while the handler is executing; if we return
immediately, and let the code execute asynchronously, RPC believes no
resources are consumed and can instantiate more handlers than the shard
has resources for.

Fix by changing the return type of the handlers to future<no_wait_type>
(from a plain no_wait_type), and making that future complete when local
processing is over.

Ref #596.
Message-Id: <1453048967-5286-1-git-send-email-avi@scylladb.com>

2016-01-18 09:59:34 +02:00

..

messaging_service.cc

storage_proxy: make MUTATION and MUTATION_DONE verbs sychronous at the server side

2016-01-18 09:59:34 +02:00

messaging_service.hh

storage_proxy: make MUTATION and MUTATION_DONE verbs sychronous at the server side

2016-01-18 09:59:34 +02:00