Re: Persistent connection among nodes to communicate and redirect request

2012-10-03 Thread Niteesh kumar
m sry, all connection among servers on port 9160 was some another application... thanx for support regard Niteesh On Wednesday 03 October 2012 02:59 PM, mdione@orange.com wrote: De : Hiller, Dean [mailto:dean.hil...@nrel.gov] Can you just use netstat and dig into the process id and do a

RE: Persistent connection among nodes to communicate and redirect request

2012-10-03 Thread mdione.ext
De : Hiller, Dean [mailto:dean.hil...@nrel.gov] > Can you just use netstat and dig into the process id and do a ps -ef | > grep to clear up all the confusion. A better way is to use: sudo netstat --tcp --programs Optionally, add --numeric to avoid hostname and port resolution. -- Marcos Di

Re: Persistent connection among nodes to communicate and redirect request

2012-10-03 Thread aaron morton
May end up with a local 9160 connection if you are using cassandra-cli, cqlsh or hadoop on the node. > I also observed that local write latency is around 30-40 microsecond, while > its takes around .5 miliseconds if the chosen node is not the node > responsible for the key for 50K QPS What C

Re: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Hiller, Dean
Can you just use netstat and dig into the process id and do a ps -ef | grep to clear up all the confusion. Doing so you can tell which process communicates with which process(I am assuming you are on linuxŠ.on MAC or windows it is different commands). Then, just paste all that in the email to th

Re: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Nick Bailey
The comments here so far are correct. Cassandra itself will never open a thrift connection. Thrift is only for clients. Not sure what exactly you are seeing but I don't think it's cassandra. On Tue, Oct 2, 2012 at 10:48 AM, Niteesh kumar wrote: > not only a node make connection to other nodes. i

Re: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Niteesh kumar
not only a node make connection to other nodes. i can also see nodes making connection to itself on port 9160. On Tuesday 02 October 2012 07:42 PM, Viktor Jevdokimov wrote: not a thrift por

RE: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Viktor Jevdokimov
ediately and irrevocably delete this message and any copies.> -Original Message- > From: rohit bhatia [mailto:rohit2...@gmail.com] > Sent: Tuesday, October 02, 2012 14:35 > To: user@cassandra.apache.org > Subject: Re: Persistent connection among nodes to communicate and >

Re: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread rohit bhatia
ately and > irrevocably delete this message and any copies.> -Original Message- >> From: Niteesh kumar [mailto:nitees...@directi.com] >> Sent: Tuesday, October 02, 2012 12:32 >> To: user@cassandra.apache.org >> Subject: Persistent connection among nodes to comm

RE: Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Viktor Jevdokimov
: Tuesday, October 02, 2012 12:32 > To: user@cassandra.apache.org > Subject: Persistent connection among nodes to communicate and redirect > request > > while looking at netstat table i observed that my cluster nodes not using > persistent connection to talk among themselves on port 91

Persistent connection among nodes to communicate and redirect request

2012-10-02 Thread Niteesh kumar
while looking at netstat table i observed that my cluster nodes not using persistent connection to talk among themselves on port 9160 to redirect request. I also observed that local write latency is around 30-40 microsecond, while its takes around .5 miliseconds if the chosen node is not the n