Multiple data center nodetool ring output display 0% owns
Hi I have deployed Cassandra 1.0.6 to a 2 data center and one data center (DC1) having one node and the other data center (DC2) having two nodes. But when I do a nodetool ring using one IP, the output says 0% owns of DC1 node. Please see the output below. # sh nodetool -h 10.XXX.XXX.XX ring Address DC RackStatus State LoadOwns Token 85070591730234615865843651857942052864 XXX.XXX.XXX.XXX DC2 RAC1Up Normal 83.89 KB 50.00% 0 YYY.YYY.YY.YYY DC1 RAC1Up Normal 71.4 KB 0.00% 1 ZZ.ZZZ.ZZZ.ZZ DC2 RAC1Up Normal 65.94 KB 50.00% 85070591730234615865843651857942052864 Could someone explain this behavior. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Multiple-data-center-nodetool-ring-output-display-0-owns-tp7279122p7279122.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: Multiple data center nodetool ring output display 0% owns
There was a thread on this a couple days ago -- short answer, the 'owns %' column is effectively incorrect when you're using multiple DCs. If you had all 3 servers in 1 DC, since server YYY has token 1 and server XXX has token 0, then server XXX would truly 'own' 0% (actually, 1/(2^128) :) ), and depending on your replication factor might have no data (if replication were 1). But two data centers is effectively like two rings - since the two nodes in DC2 are token-balanced, you'd see even distribution between them, and DC1 has only one server, so that would be even as well (assuming you replicate to both sites). --DRS On Feb 12, 2012, at 5:42 PM, Roshan wrote: > Hi > > I have deployed Cassandra 1.0.6 to a 2 data center and one data center (DC1) > having one node and the other data center (DC2) having two nodes. But when I > do a nodetool ring using one IP, the output says 0% owns of DC1 node. Please > see the output below. > > # sh nodetool -h 10.XXX.XXX.XX ring > Address DC RackStatus State LoadOwns > Token > > 85070591730234615865843651857942052864 > XXX.XXX.XXX.XXX DC2 RAC1Up Normal 83.89 KB > 50.00% 0 > YYY.YYY.YY.YYY DC1 RAC1Up Normal 71.4 KB 0.00% > 1 > ZZ.ZZZ.ZZZ.ZZ DC2 RAC1Up Normal 65.94 KB > 50.00% 85070591730234615865843651857942052864 > > Could someone explain this behavior. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Multiple-data-center-nodetool-ring-output-display-0-owns-tp7279122p7279122.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
Re: Multiple data center nodetool ring output display 0% owns
> There was a thread on this a couple days ago -- short answer, the 'owns %' > column is effectively incorrect when you're using multiple DCs. If you had > all 3 servers in 1 DC, since server YYY has token 1 and server XXX has token > 0, then server XXX would truly 'own' 0% (actually, 1/(2^128) :) ), and > depending on your replication factor might have no data (if replication were > 1). It's also incorrect for rack awareness if your topology is such that the rack awareness changes ownership (see https://issues.apache.org/jira/browse/CASSANDRA-3810). -- / Peter Schuller (@scode, http://worldmodscode.wordpress.com)
How to find a commit for specific release on git?
Hello, How to find the right commit SHA for specific cassandra release? For example, how to checkout 0.8.9 release on git repository? With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 was --- commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 Author: Sylvain Lebresne Date: Sun Dec 11 00:02:14 2011 + prepare for release 0.8.9 git-svn-id: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 13f79535-47bb-0310-9956-ffa450edef68 --- However I don't think it's a reliable way. I've also checked CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. regards, -- maki
Re: How to find a commit for specific release on git?
Based on the tags listed here: http://git-wip-us.apache.org/repos/asf?p=cassandra.git I would look here http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=9d4c0d9a37c7d77a05607b85611c3abdaf75be94 On 02/12/2012 10:39 PM, Maki Watanabe wrote: Hello, How to find the right commit SHA for specific cassandra release? For example, how to checkout 0.8.9 release on git repository? With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 was --- commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 Author: Sylvain Lebresne Date: Sun Dec 11 00:02:14 2011 + prepare for release 0.8.9 git-svn-id: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 13f79535-47bb-0310-9956-ffa450edef68 --- However I don't think it's a reliable way. I've also checked CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. regards,
Re: How to find a commit for specific release on git?
Perfect! Thanks. 2012/2/13 Dave Brosius : > Based on the tags listed here: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git > > I would look here > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=9d4c0d9a37c7d77a05607b85611c3abdaf75be94 > > > > On 02/12/2012 10:39 PM, Maki Watanabe wrote: > > Hello, > > How to find the right commit SHA for specific cassandra release? > For example, how to checkout 0.8.9 release on git repository? > With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 > was > --- > commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 > Author: Sylvain Lebresne > Date: Sun Dec 11 00:02:14 2011 + > > prepare for release 0.8.9 > > git-svn-id: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 > 13f79535-47bb-0310-9956-ffa450edef68 > --- > > However I don't think it's a reliable way. I've also checked > CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. > > regards, > > -- w3m
Unsubscribe
-- Sent using BlackBerry
Re: How to find a commit for specific release on git?
I found I can get the info by "git tag". I should better to learn git more to switch... 2012/2/13 Maki Watanabe : > Perfect! Thanks. > > 2012/2/13 Dave Brosius : >> Based on the tags listed here: >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git >> >> I would look here >> >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=9d4c0d9a37c7d77a05607b85611c3abdaf75be94 >> >> >> >> On 02/12/2012 10:39 PM, Maki Watanabe wrote: >> >> Hello, >> >> How to find the right commit SHA for specific cassandra release? >> For example, how to checkout 0.8.9 release on git repository? >> With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 >> was >> --- >> commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 >> Author: Sylvain Lebresne >> Date: Sun Dec 11 00:02:14 2011 + >> >> prepare for release 0.8.9 >> >> git-svn-id: >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 >> 13f79535-47bb-0310-9956-ffa450edef68 >> --- >> >> However I don't think it's a reliable way. I've also checked >> CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. >> >> regards, >> >> > > > > -- > w3m -- w3m
Re: Unsubscribe
On 02/12/2012 10:53 PM, Shubham Srivastava wrote: -- Sent using BlackBerry send an email to user-unsubscr...@cassandra.apache.org
R: Re: How to find a commit for specific release on git?
unsubscribe Inviato dal mio smartphone BlackBerry® www.blackberry.com -Original Message- From: Maki Watanabe Date: Mon, 13 Feb 2012 12:50:13 To: Dave Brosius Reply-To: user@cassandra.apache.org Cc: Subject: Re: How to find a commit for specific release on git? Perfect! Thanks. 2012/2/13 Dave Brosius : > Based on the tags listed here: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git > > I would look here > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=9d4c0d9a37c7d77a05607b85611c3abdaf75be94 > > > > On 02/12/2012 10:39 PM, Maki Watanabe wrote: > > Hello, > > How to find the right commit SHA for specific cassandra release? > For example, how to checkout 0.8.9 release on git repository? > With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 > was > --- > commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 > Author: Sylvain Lebresne > Date: Sun Dec 11 00:02:14 2011 + > > prepare for release 0.8.9 > > git-svn-id: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 > 13f79535-47bb-0310-9956-ffa450edef68 > --- > > However I don't think it's a reliable way. I've also checked > CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. > > regards, > > -- w3m
Re: How to find a commit for specific release on git?
Updated http://wiki.apache.org/cassandra/HowToBuild . 2012/2/13 Maki Watanabe : > I found I can get the info by "git tag". > I should better to learn git more to switch... > > 2012/2/13 Maki Watanabe : >> Perfect! Thanks. >> >> 2012/2/13 Dave Brosius : >>> Based on the tags listed here: >>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git >>> >>> I would look here >>> >>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=9d4c0d9a37c7d77a05607b85611c3abdaf75be94 >>> >>> >>> >>> On 02/12/2012 10:39 PM, Maki Watanabe wrote: >>> >>> Hello, >>> >>> How to find the right commit SHA for specific cassandra release? >>> For example, how to checkout 0.8.9 release on git repository? >>> With git log --grep=0.8.9, I found the latest commit mentioned about 0.8.9 >>> was >>> --- >>> commit 1f92277c4bf9f5f71303ecc5592e27603bc9dec1 >>> Author: Sylvain Lebresne >>> Date: Sun Dec 11 00:02:14 2011 + >>> >>> prepare for release 0.8.9 >>> >>> git-svn-id: >>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@1212938 >>> 13f79535-47bb-0310-9956-ffa450edef68 >>> --- >>> >>> However I don't think it's a reliable way. I've also checked >>> CHANGES.txt and NEW.txt but thoese say nothing on commit SHA. >>> >>> regards, >>> >>> >> >> >> >> -- >> w3m > > > > -- > w3m -- w3m
keycache persisted to disk ?
Hi, I am testing Cassandra on Amazon and finding performance can vary fairly wildly. I'm leaning towards it being an artifact of the AWS I/O system but have one other possibility. Are keycaches persisted to disk and restored on a clean shutdown and restart ? cheers -- *Franc Carter* | Systems architect | Sirca Ltd franc.car...@sirca.org.au | www.sirca.org.au Tel: +61 2 9236 9118 Level 9, 80 Clarence St, Sydney NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215
Re: keycache persisted to disk ?
I think the keycaches and rowcahches are bothe persisted to disk when shutdown, and restored from disk when restart, then improve the performance. 2012-02-13 zhangcheng 发件人： Franc Carter 发送时间： 2012-02-13 13:53:56 收件人： user 抄送： 主题： keycache persisted to disk ? Hi, I am testing Cassandra on Amazon and finding performance can vary fairly wildly. I'm leaning towards it being an artifact of the AWS I/O system but have one other possibility. Are keycaches persisted to disk and restored on a clean shutdown and restart ? cheers -- Franc Carter | Systems architect | Sirca Ltd franc.car...@sirca.org.au | www.sirca.org.au Tel: +61 2 9236 9118 Level 9, 80 Clarence St, Sydney NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215
Re: keycache persisted to disk ?
On Mon, Feb 13, 2012 at 5:03 PM, zhangcheng wrote: > ** > > I think the keycaches and rowcahches are bothe persisted to disk when > shutdown, and restored from disk when restart, then improve the performance. > Thanks - that would explain at least some of what I am seeing cheers > > 2012-02-13 > -- > zhangcheng > -- > *发件人：* Franc Carter > *发送时间：* 2012-02-13 13:53:56 > *收件人：* user > *抄送：* > *主题：* keycache persisted to disk ? > > Hi, > > I am testing Cassandra on Amazon and finding performance can vary fairly > wildly. I'm leaning towards it being an artifact of the AWS I/O system but > have one other possibility. > > Are keycaches persisted to disk and restored on a clean shutdown and > restart ? > > cheers > > -- > > *Franc Carter* | Systems architect | Sirca Ltd > > > franc.car...@sirca.org.au | www.sirca.org.au > > Tel: +61 2 9236 9118 > > Level 9, 80 Clarence St, Sydney NSW 2000 > > PO Box H58, Australia Square, Sydney NSW 1215 > > -- *Franc Carter* | Systems architect | Sirca Ltd franc.car...@sirca.org.au | www.sirca.org.au Tel: +61 2 9236 9118 Level 9, 80 Clarence St, Sydney NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215
