Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Message-ID: <BLU184-W131EC3A2CBFA000F847411B9E00@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_b3b85aeb-3ddf-4adb-9487-c2e88a4a2098_"
From: Jun Wu <wuxiaomin98@hotmail.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: How to get information of each read/write request?
Date: Tue, 30 Aug 2016 12:20:52 -0500
Importance: Normal
MIME-Version: 1.0
archived-at: Tue, 30 Aug 2016 17:21:06 -0000

--_b3b85aeb-3ddf-4adb-9487-c2e88a4a2098_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi there=2C
     I'm very interested in the read/write path of Cassandra. Specifically=
=2C I'd like to know the whole process when a read/write request comes in.=
=20
    I noticed that for reach request it could go through multiple stages. F=
or example=2C for read request=2C it could be in ReadStage=2C RequestRespon=
seStage=2C ReadRepairStage. For each stage=2C actually it's a queue and thr=
ead pool to serve the request.=20
   First question is how to track each request in which stage.    Also I'm =
very interested int the waiting time for each request to be in the queue=2C=
 also the total queue in each stage. I noticed that in nodetool tpstats wil=
l have this information. However=2C I may want to get the real-time informa=
tion of this=2C like print it out in the terminal.=20
    I'm wondering  whether someone has hints on this.=20
   Thanks in advance!
Jun
      		 	   		  =

--_b3b85aeb-3ddf-4adb-9487-c2e88a4a2098_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hi there=2C<div><br></div><div>&=
nbsp=3B &nbsp=3B &nbsp=3BI'm very interested in the read/write path of Cass=
andra. Specifically=2C I'd like to know the whole process when a read/write=
 request comes in.&nbsp=3B</div><div><br></div><div>&nbsp=3B &nbsp=3B I not=
iced that for reach request it could go through multiple stages. For exampl=
e=2C for read request=2C it could be in ReadStage=2C RequestResponseStage=
=2C ReadRepairStage. For each stage=2C actually it's a queue and thread poo=
l to serve the request.&nbsp=3B</div><div><br></div><div>&nbsp=3B &nbsp=3BF=
irst question is how to track each request in which stage.</div><div>&nbsp=
=3B</div><div>&nbsp=3B &nbsp=3BAlso I'm very interested int the waiting tim=
e for each request to be in the queue=2C also the total queue in each stage=
. I noticed that in nodetool tpstats will have this information. However=2C=
 I may want to get the real-time information of this=2C like print it out i=
n the terminal.&nbsp=3B</div><div><br></div><div>&nbsp=3B &nbsp=3B I'm wond=
ering &nbsp=3Bwhether someone has hints on this.&nbsp=3B</div><div><br></di=
v><div>&nbsp=3B &nbsp=3BThanks in advance!</div><div><br></div><div>Jun</di=
v><div><br></div><div>&nbsp=3B &nbsp=3B &nbsp=3B</div> 		 	   		  </div></b=
ody>
</html>=

--_b3b85aeb-3ddf-4adb-9487-c2e88a4a2098_--