[
https://issues.apache.org/jira/browse/CASSANDRA-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ariel Weisberg reassigned CASSANDRA-13862:
------------------------------------------
Assignee: Jaydeepkumar Chovatia
> Optimize Paxos prepare and propose stage for local requests
> ------------------------------------------------------------
>
> Key: CASSANDRA-13862
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13862
> Project: Cassandra
> Issue Type: Improvement
> Components: Streaming and Messaging
> Reporter: Jaydeepkumar Chovatia
> Assignee: Jaydeepkumar Chovatia
> Priority: Minor
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> 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 |
> https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/StorageProxy.java#L1244]
> 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.
> {quote}
> 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
> {quote}
> Same thing applies for {{Propose stage}} as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
