Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 13 Sep 2017 23:31:00 +0000 (UTC)
From: "Jaydeepkumar Chovatia (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13101533.1505192574000.106940.1505345460383@Atlassian.JIRA>
In-Reply-To: <JIRA.13101533.1505192574000@Atlassian.JIRA>
References: <JIRA.13101533.1505192574000@Atlassian.JIRA> <JIRA.13101533.1505192574880@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-13862) Optimize Paxos prepare and
 propose stage for local requests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 13 Sep 2017 23:31:05 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-13862?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaydeepkumar Chovatia updated CASSANDRA-13862:
----------------------------------------------
    Fix Version/s:     (was: 3.11.x)
                       (was: 3.0.x)

> Optimize Paxos prepare and propose stage for local requests=20
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-13862
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1386=
2
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Streaming and Messaging
>            Reporter: Jaydeepkumar Chovatia
>            Assignee: Jaydeepkumar Chovatia
>            Priority: Minor
>             Fix For: 4.x
>
>
> Currently Paxos prepare and propose messages always go through entire Mes=
sagingService stack in Cassandra even if request is to be served locally, w=
e can enhance and make local requests severed w/o involving MessagingServic=
e. Similar things are done at may [other places | https://github.com/apache=
/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/service/Storage=
Proxy.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 Cassan=
dra 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
> =E2=80=A6                                                                =
                                                                           =
       REQUEST_RESPONSE message received from /A.B.C.D [MessagingService-In=
coming-/A.B.C.D] | 2017-09-11 21:55:18.976000 |  A.B.C.D |          20270
> =E2=80=A6                                                                =
                                                                           =
                                     Processing response from /A.B.C.D [Sha=
redPool-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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org