Gleb Natapov d28dd4957b lwt: Process lwt request on a owning shard ...

LWT is much more efficient if a request is processed on a shard that owns
a token for the request. This is because otherwise the processing will
bounce to an owning shard multiple times. The patch proposes a way to
move request to correct shard before running lwt.  It works by returning
an error from lwt code if a shard is incorrect one specifying the shard
the request should be moved to. The error is processed by transport code
that jumps to a correct shard and re-process incoming message there.

2020-01-13 10:26:02 +02:00

..

handler.cc

lwt: Process lwt request on a owning shard

2020-01-13 10:26:02 +02:00

handler.hh

cql3, treewide: introduce empty cql3::cql_config class and propagate it

2019-08-21 19:35:59 +02:00

server.cc

treewide: silence discarded future warnings for legit discards

2019-08-26 18:54:44 +03:00

server.hh

cql3, treewide: introduce empty cql3::cql_config class and propagate it

2019-08-21 19:35:59 +02:00

thrift_validation.cc

types: Add cql_serialization_format parameter to validate

2019-04-09 16:58:22 +02:00

thrift_validation.hh

thrift: change generated code namespace

2017-05-05 05:26:20 +03:00

utils.hh

thrift: Extract make_exception to common header

2016-06-23 11:40:52 +02:00