Avi Kivity f9d66f88bb transport: advertise the shard serving a connection ...

It is useful for the client driver to know which shard is serving a
particular connection, so it can only send requests through that connection
which will be served by the same shard, eliminating a hop.

Support that by advertising a "SCYLLA_SHARD" option, with a value
corresponding to the shard number.

Acked-by: Glauber Costa <glauber@scylladb.com>
Message-Id: <20180606203437.1198-1-avi@scylladb.com>

2018-06-07 10:43:16 +03:00

..

messages

transport: add ostream support to result_message

2018-05-06 16:28:35 +03:00

event_notifier.cc

cql_server: fix a race between closing of a connection and notifier registration

2018-04-12 16:56:50 +03:00

event.cc

Merge seatar upstream (seastar namespace)

2017-05-21 12:26:15 +03:00

event.hh

Merge seatar upstream (seastar namespace)

2017-05-21 12:26:15 +03:00

messages_fwd.hh

Merge seatar upstream (seastar namespace)

2017-05-21 12:26:15 +03:00

server.cc

transport: advertise the shard serving a connection

2018-06-07 10:43:16 +03:00

server.hh

transport: make write_repsonse() return void

2018-05-14 09:41:06 +03:00