Re: running TPC-C on cassandra clusters
Thanks! 2011/5/12 Jonathan Ellis > Not if you want the pausing/marking down fixes that were done more > recently. :) > > On Thu, May 12, 2011 at 8:39 PM, Xiaowei Wang > wrote: > > Oh sorry, we use cassandra-0.7.4 already. Is the version fine? > > > > 2011/5/12 Jonathan Ellis > >> > >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7 > >> > >> On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang > >> wrote: > >> > Thanks Jonathan, but can you provide some links about 0.7 svn branch? > >> > > >> > 2011/5/12 Jonathan Ellis > >> >> > >> >> I'd recommend trying the 0.7 svn branch (soon to be voted on as > 0.7.6) > >> >> > >> >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang > >> >> wrote: > >> >> > Hi all, > >> >> > > >> >> > My partner and I currently using cassandra cluster to run TPC-C. We > >> >> > first > >> >> > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 > cores, > >> >> > the > >> >> > other(worker node) has 4 cores. During the loading time, either the > >> >> > client > >> >> > node or the worker node will "down"(cannot be detected) randomly > and > >> >> > then > >> >> > "up" again in a short time. If the two nodes both down, we failed > in > >> >> > loading. If only one of them down, we can continue to load data. > >> >> > > >> >> > The problem is if we use multiple threads(we write multiprocess > >> >> > code), > >> >> > say 4 > >> >> > clients threads, some of them might be stop at the point one of the > >> >> > nodes > >> >> > first down, and the dead threads will never come back This will > >> >> > not > >> >> > only > >> >> > enlarge our loading time, but also effect the amount of data we can > >> >> > load. > >> >> > > >> >> > So we need to figure out why the nodes continue to be up and down > and > >> >> > fix > >> >> > this problem. > >> >> > > >> >> > Thanks for any help! > >> >> > > >> >> > Best, > >> >> > Xiaowei > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Jonathan Ellis > >> >> Project Chair, Apache Cassandra > >> >> co-founder of DataStax, the source for professional Cassandra support > >> >> http://www.datastax.com > >> > > >> > > >> > >> > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder of DataStax, the source for professional Cassandra support > >> http://www.datastax.com > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: running TPC-C on cassandra clusters
Not if you want the pausing/marking down fixes that were done more recently. :) On Thu, May 12, 2011 at 8:39 PM, Xiaowei Wang wrote: > Oh sorry, we use cassandra-0.7.4 already. Is the version fine? > > 2011/5/12 Jonathan Ellis >> >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7 >> >> On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang >> wrote: >> > Thanks Jonathan, but can you provide some links about 0.7 svn branch? >> > >> > 2011/5/12 Jonathan Ellis >> >> >> >> I'd recommend trying the 0.7 svn branch (soon to be voted on as 0.7.6) >> >> >> >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang >> >> wrote: >> >> > Hi all, >> >> > >> >> > My partner and I currently using cassandra cluster to run TPC-C. We >> >> > first >> >> > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, >> >> > the >> >> > other(worker node) has 4 cores. During the loading time, either the >> >> > client >> >> > node or the worker node will "down"(cannot be detected) randomly and >> >> > then >> >> > "up" again in a short time. If the two nodes both down, we failed in >> >> > loading. If only one of them down, we can continue to load data. >> >> > >> >> > The problem is if we use multiple threads(we write multiprocess >> >> > code), >> >> > say 4 >> >> > clients threads, some of them might be stop at the point one of the >> >> > nodes >> >> > first down, and the dead threads will never come back This will >> >> > not >> >> > only >> >> > enlarge our loading time, but also effect the amount of data we can >> >> > load. >> >> > >> >> > So we need to figure out why the nodes continue to be up and down and >> >> > fix >> >> > this problem. >> >> > >> >> > Thanks for any help! >> >> > >> >> > Best, >> >> > Xiaowei >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Jonathan Ellis >> >> Project Chair, Apache Cassandra >> >> co-founder of DataStax, the source for professional Cassandra support >> >> http://www.datastax.com >> > >> > >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: running TPC-C on cassandra clusters
Oh sorry, we use cassandra-0.7.4 already. Is the version fine? 2011/5/12 Jonathan Ellis > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7 > > On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang > wrote: > > Thanks Jonathan, but can you provide some links about 0.7 svn branch? > > > > 2011/5/12 Jonathan Ellis > >> > >> I'd recommend trying the 0.7 svn branch (soon to be voted on as 0.7.6) > >> > >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang > >> wrote: > >> > Hi all, > >> > > >> > My partner and I currently using cassandra cluster to run TPC-C. We > >> > first > >> > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, > >> > the > >> > other(worker node) has 4 cores. During the loading time, either the > >> > client > >> > node or the worker node will "down"(cannot be detected) randomly and > >> > then > >> > "up" again in a short time. If the two nodes both down, we failed in > >> > loading. If only one of them down, we can continue to load data. > >> > > >> > The problem is if we use multiple threads(we write multiprocess code), > >> > say 4 > >> > clients threads, some of them might be stop at the point one of the > >> > nodes > >> > first down, and the dead threads will never come back This will > not > >> > only > >> > enlarge our loading time, but also effect the amount of data we can > >> > load. > >> > > >> > So we need to figure out why the nodes continue to be up and down and > >> > fix > >> > this problem. > >> > > >> > Thanks for any help! > >> > > >> > Best, > >> > Xiaowei > >> > > >> > > >> > >> > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder of DataStax, the source for professional Cassandra support > >> http://www.datastax.com > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: running TPC-C on cassandra clusters
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7 On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang wrote: > Thanks Jonathan, but can you provide some links about 0.7 svn branch? > > 2011/5/12 Jonathan Ellis >> >> I'd recommend trying the 0.7 svn branch (soon to be voted on as 0.7.6) >> >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang >> wrote: >> > Hi all, >> > >> > My partner and I currently using cassandra cluster to run TPC-C. We >> > first >> > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, >> > the >> > other(worker node) has 4 cores. During the loading time, either the >> > client >> > node or the worker node will "down"(cannot be detected) randomly and >> > then >> > "up" again in a short time. If the two nodes both down, we failed in >> > loading. If only one of them down, we can continue to load data. >> > >> > The problem is if we use multiple threads(we write multiprocess code), >> > say 4 >> > clients threads, some of them might be stop at the point one of the >> > nodes >> > first down, and the dead threads will never come back This will not >> > only >> > enlarge our loading time, but also effect the amount of data we can >> > load. >> > >> > So we need to figure out why the nodes continue to be up and down and >> > fix >> > this problem. >> > >> > Thanks for any help! >> > >> > Best, >> > Xiaowei >> > >> > >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: running TPC-C on cassandra clusters
Thanks Jonathan, but can you provide some links about 0.7 svn branch? 2011/5/12 Jonathan Ellis > I'd recommend trying the 0.7 svn branch (soon to be voted on as 0.7.6) > > On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang > wrote: > > Hi all, > > > > My partner and I currently using cassandra cluster to run TPC-C. We first > > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, > the > > other(worker node) has 4 cores. During the loading time, either the > client > > node or the worker node will "down"(cannot be detected) randomly and then > > "up" again in a short time. If the two nodes both down, we failed in > > loading. If only one of them down, we can continue to load data. > > > > The problem is if we use multiple threads(we write multiprocess code), > say 4 > > clients threads, some of them might be stop at the point one of the nodes > > first down, and the dead threads will never come back This will not > only > > enlarge our loading time, but also effect the amount of data we can load. > > > > So we need to figure out why the nodes continue to be up and down and fix > > this problem. > > > > Thanks for any help! > > > > Best, > > Xiaowei > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: running TPC-C on cassandra clusters
I'd recommend trying the 0.7 svn branch (soon to be voted on as 0.7.6) On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang wrote: > Hi all, > > My partner and I currently using cassandra cluster to run TPC-C. We first > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, the > other(worker node) has 4 cores. During the loading time, either the client > node or the worker node will "down"(cannot be detected) randomly and then > "up" again in a short time. If the two nodes both down, we failed in > loading. If only one of them down, we can continue to load data. > > The problem is if we use multiple threads(we write multiprocess code), say 4 > clients threads, some of them might be stop at the point one of the nodes > first down, and the dead threads will never come back This will not only > enlarge our loading time, but also effect the amount of data we can load. > > So we need to figure out why the nodes continue to be up and down and fix > this problem. > > Thanks for any help! > > Best, > Xiaowei > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
running TPC-C on cassandra clusters
Hi all, My partner and I currently using cassandra cluster to run TPC-C. We first use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 cores, the other(worker node) has 4 cores. During the loading time, either the client node or the worker node will "down"(cannot be detected) randomly and then "up" again in a short time. If the two nodes both down, we failed in loading. If only one of them down, we can continue to load data. The problem is if we use multiple threads(we write multiprocess code), say 4 clients threads, some of them might be stop at the point one of the nodes first down, and the dead threads will never come back This will not only enlarge our loading time, but also effect the amount of data we can load. So we need to figure out why the nodes continue to be up and down and fix this problem. Thanks for any help! Best, Xiaowei
