[CASSANDRA-13862] Optimize Paxos prepare and propose stage for local requests

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Streaming and Messaging
• Assignee: Jaydeepkumar Chovatia
• Reporter: Jaydeepkumar Chovatia

Authors

Jaydeepkumar Chovatia

Reviewers

Ariel Weisberg

• Created: 12/Sep/17 05:02
• Updated: 15/May/20 08:01
• Resolved: 28/Sep/17 21:14

Description

Currently Paxos prepare and propose messages always go through entire MessagingService stack in Cassandra even if request is to be served locally, we can enhance and make local requests severed w/o involving MessagingService. Similar things are done at may other places in Cassandra which skips MessagingService stage for local requests.

This is what it looks like currently if we have tracing on and run Cassandra light weight transaction.

Sending PAXOS_PREPARE message to /A.B.C.D [MessagingService-Outgoing-/A.B.C.D] | 2017-09-11 21:55:18.971000 | A.B.C.D | 15045
… REQUEST_RESPONSE message received from /A.B.C.D [MessagingService-Incoming-/A.B.C.D] | 2017-09-11 21:55:18.976000 | A.B.C.D | 20270
… Processing response from /A.B.C.D [SharedPool-Worker-4] | 2017-09-11 21:55:18.976000 | A.B.C.D | 20372

Same thing applies for Propose stage as well.