You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Viktor Jevdokimov <Vi...@adform.com> on 2010/04/29 13:12:53 UTC
Cassandra on Windows network latency
Hi all,
We have installed Cassandra on Windows and found that with any number of Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server 2008, 32 or 64 bit, with any load or number of requests we, have:
When client and server are on the same machine, connect/read/write latencies ~0-1ms
When client on another machine, same network, on the same switch, connection latency 0-1ms (as a ping), read/write latencies >=200ms.
What causes 200ms latency accessing Cassandra on Windows through network? Does anybody experience such behavior?
Cassandra 0.6.1
Java SE 6 u20
Best regards,
Viktor
Re: Primary and Backup clusters
Posted by Jonathan Ellis <jb...@gmail.com>.
I suppose you could use rsync (sstable files are immutable, so you
don't need to worry about not getting a "consistent" version of the
data files), but compared to letting Cassandra handle the replication
the way it's designed to,
# you'll generate a lot of disk i/o doing that vs
# your backup cluster will miss a relatively large amount of the most
recent updates
# your failover process will be more error-prone
On Mon, May 3, 2010 at 8:05 AM, Viktor Jevdokimov
<Vi...@adform.com> wrote:
> Hello,
>
> Our system (not Cassandra) have backup cluster in different datacenter in case of primary cluster unavailability or for software upgrades.
> 100% of traffic goes to primary cluster. We switch 100% traffic to backup cluster in case above for a short time, then when issues are resolved, traffic is switched back to primary.
>
> We'd like to have primary and backup Cassandra clusters in different datacenters for the same reasons.
> We do not want to have a high traffic between primary and backup datacenters.
>
> Now the questions:
>
> 1. How to sync Cassandra clusters (backup<->primary) with minimal traffic?
> 2. How to configure Cassandra in such case?
>
>
> Thanks,
>
> Viktor
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
Primary and Backup clusters
Posted by Viktor Jevdokimov <Vi...@adform.com>.
Hello,
Our system (not Cassandra) have backup cluster in different datacenter in case of primary cluster unavailability or for software upgrades.
100% of traffic goes to primary cluster. We switch 100% traffic to backup cluster in case above for a short time, then when issues are resolved, traffic is switched back to primary.
We'd like to have primary and backup Cassandra clusters in different datacenters for the same reasons.
We do not want to have a high traffic between primary and backup datacenters.
Now the questions:
1. How to sync Cassandra clusters (backup<->primary) with minimal traffic?
2. How to configure Cassandra in such case?
Thanks,
Viktor
RE: Cassandra on Windows network latency
Posted by Viktor Jevdokimov <Vi...@adform.com>.
Yes, we have already figured that out :)
Thanks!
-----Original Message-----
From: Carlos Alvarez [mailto:cbalvarez@gmail.com]
Sent: Thursday, April 29, 2010 4:03 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra on Windows network latency
Are you using TSocket in the client?. If yes, use TbufferedTransport instead.
Carlos
On 4/29/10, Viktor Jevdokimov <Vi...@adform.com> wrote:
> Thrift C# sources, thrift generated Cassandra sources, test app built with
> C#. Simple connect/write/read operations. No pooling or anything else.
>
> From: Heath Oderman [mailto:heath@526valley.com]
> Sent: Thursday, April 29, 2010 2:17 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra on Windows network latency
>
> I learned the hard way, that running py_stress in the src/contrib directory
> is a great way to test what kind of speeds you are really getting.
>
> What tools / client are you using to test to get the 200ms number?
>
> stu
> On Thu, Apr 29, 2010 at 7:12 AM, Viktor Jevdokimov
> <Vi...@adform.com>> wrote:
> Hi all,
>
> We have installed Cassandra on Windows and found that with any number of
> Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server
> 2008, 32 or 64 bit, with any load or number of requests we, have:
>
> When client and server are on the same machine, connect/read/write latencies
> ~0-1ms
> When client on another machine, same network, on the same switch, connection
> latency 0-1ms (as a ping), read/write latencies >=200ms.
>
> What causes 200ms latency accessing Cassandra on Windows through network?
> Does anybody experience such behavior?
>
> Cassandra 0.6.1
> Java SE 6 u20
>
>
> Best regards,
> Viktor
>
>
>
--
Sent from my mobile device
Tal vez hubo un error en la grafía. O en la articulación del Sacro Nombre.
Re: Cassandra on Windows network latency
Posted by Carlos Alvarez <cb...@gmail.com>.
Are you using TSocket in the client?. If yes, use TbufferedTransport instead.
Carlos
On 4/29/10, Viktor Jevdokimov <Vi...@adform.com> wrote:
> Thrift C# sources, thrift generated Cassandra sources, test app built with
> C#. Simple connect/write/read operations. No pooling or anything else.
>
> From: Heath Oderman [mailto:heath@526valley.com]
> Sent: Thursday, April 29, 2010 2:17 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra on Windows network latency
>
> I learned the hard way, that running py_stress in the src/contrib directory
> is a great way to test what kind of speeds you are really getting.
>
> What tools / client are you using to test to get the 200ms number?
>
> stu
> On Thu, Apr 29, 2010 at 7:12 AM, Viktor Jevdokimov
> <Vi...@adform.com>> wrote:
> Hi all,
>
> We have installed Cassandra on Windows and found that with any number of
> Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server
> 2008, 32 or 64 bit, with any load or number of requests we, have:
>
> When client and server are on the same machine, connect/read/write latencies
> ~0-1ms
> When client on another machine, same network, on the same switch, connection
> latency 0-1ms (as a ping), read/write latencies >=200ms.
>
> What causes 200ms latency accessing Cassandra on Windows through network?
> Does anybody experience such behavior?
>
> Cassandra 0.6.1
> Java SE 6 u20
>
>
> Best regards,
> Viktor
>
>
>
--
Sent from my mobile device
Tal vez hubo un error en la grafía. O en la articulación del Sacro Nombre.
RE: Cassandra on Windows network latency
Posted by Viktor Jevdokimov <Vi...@adform.com>.
Thrift C# sources, thrift generated Cassandra sources, test app built with C#. Simple connect/write/read operations. No pooling or anything else.
From: Heath Oderman [mailto:heath@526valley.com]
Sent: Thursday, April 29, 2010 2:17 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra on Windows network latency
I learned the hard way, that running py_stress in the src/contrib directory is a great way to test what kind of speeds you are really getting.
What tools / client are you using to test to get the 200ms number?
stu
On Thu, Apr 29, 2010 at 7:12 AM, Viktor Jevdokimov <Vi...@adform.com>> wrote:
Hi all,
We have installed Cassandra on Windows and found that with any number of Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server 2008, 32 or 64 bit, with any load or number of requests we, have:
When client and server are on the same machine, connect/read/write latencies ~0-1ms
When client on another machine, same network, on the same switch, connection latency 0-1ms (as a ping), read/write latencies >=200ms.
What causes 200ms latency accessing Cassandra on Windows through network? Does anybody experience such behavior?
Cassandra 0.6.1
Java SE 6 u20
Best regards,
Viktor
Re: Cassandra on Windows network latency
Posted by Heath Oderman <he...@526valley.com>.
I learned the hard way, that running py_stress in the src/contrib directory
is a great way to test what kind of speeds you are really getting.
What tools / client are you using to test to get the 200ms number?
stu
On Thu, Apr 29, 2010 at 7:12 AM, Viktor Jevdokimov <
Viktor.Jevdokimov@adform.com> wrote:
> Hi all,
>
>
>
> We have installed Cassandra on Windows and found that with any number of
> Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server
> 2008, 32 or 64 bit, with any load or number of requests we, have:
>
>
>
> When client and server are on the same machine, connect/read/write
> latencies ~0-1ms
>
> When client on another machine, same network, on the same switch,
> connection latency 0-1ms (as a ping), read/write latencies >=200ms.
>
>
>
> What causes 200ms latency accessing Cassandra on Windows through network?
> Does anybody experience such behavior?
>
>
>
> Cassandra 0.6.1
>
> Java SE 6 u20
>
>
>
>
>
> Best regards,
>
> Viktor
>
>
>