RE: Commissioning failure
Thanks Rob. We have disabled firewalls between the nodes and yet getting the same error. I have one more doubt. In our cluster we configured size tiered compaction strategy on JBOD and we are facing issues like uneven distribution of data. Is it possible to change compaction strategy of tables with data? Which compaction strategy will be ideal for data directories in JBOD ? Date: Thu, 30 Oct 2014 11:16:59 -0700 Subject: Re: Commissioning failure From: rc...@eventbrite.com To: user@cassandra.apache.org On Wed, Oct 29, 2014 at 10:39 PM, Aravindan T aravinda...@tcs.com wrote: What could be the reasons for the stream error other than SSTABLE corruption? There's tons of reasons streams fail. Cassandra team is aware of how painful it makes things, so they are working on them. Be sure that a firewall is not dropping long running connections. =Robhttp://twitter.com/rcolidba
Re: Commissioning failure
Hi, I think only LevelledCompactionStrategy makes sense on JBOD because that can distribute data more evenly. Although I don't know what is the exact strategy where each compaction strategy will store sstables. If you use SizeTieredCompactionStrategy you might run into problems when sstables get big enough. I think the theoretical maximum size for an STCS table is the half of one disk size. Because you might be able to run major compaction in that situation. I wouldn't actually use JBOD with anything else than LCS. With smaller tables it doesn't really matter that much but with big tables you would run into problem with anything else. Please correct me if I am wrong. Hannu 2014-10-31 12:16 GMT+02:00 venkat sam samvenkat...@outlook.com: Thanks Rob. We have disabled firewalls between the nodes and yet getting the same error. I have one more doubt. In our cluster we configured size tiered compaction strategy on JBOD and we are facing issues like uneven distribution of data. Is it possible to change compaction strategy of tables with data? Which compaction strategy will be ideal for data directories in JBOD ? -- Date: Thu, 30 Oct 2014 11:16:59 -0700 Subject: Re: Commissioning failure From: rc...@eventbrite.com To: user@cassandra.apache.org On Wed, Oct 29, 2014 at 10:39 PM, Aravindan T aravinda...@tcs.com wrote: What could be the reasons for the stream error other than SSTABLE corruption? There's tons of reasons streams fail. Cassandra team is aware of how painful it makes things, so they are working on them. Be sure that a firewall is not dropping long running connections. =Rob http://twitter.com/rcolidba
RE: Commissioning failure
Yes Hannu, Initially for one month we didn't face any problem. But once tables got bigger we are getting the disk space issues. Can I change the compaction strategy. Will changing compaction strategy have an impact on data consistency? Will it cause corruption of SSTable . -Venkat Date: Fri, 31 Oct 2014 13:43:11 +0200 Subject: Re: Commissioning failure From: hkro...@gmail.com To: user@cassandra.apache.org Hi, I think only LevelledCompactionStrategy makes sense on JBOD because that can distribute data more evenly. Although I don't know what is the exact strategy where each compaction strategy will store sstables. If you use SizeTieredCompactionStrategy you might run into problems when sstables get big enough. I think the theoretical maximum size for an STCS table is the half of one disk size. Because you might be able to run major compaction in that situation. I wouldn't actually use JBOD with anything else than LCS. With smaller tables it doesn't really matter that much but with big tables you would run into problem with anything else. Please correct me if I am wrong. Hannu 2014-10-31 12:16 GMT+02:00 venkat sam samvenkat...@outlook.com: Thanks Rob. We have disabled firewalls between the nodes and yet getting the same error. I have one more doubt. In our cluster we configured size tiered compaction strategy on JBOD and we are facing issues like uneven distribution of data. Is it possible to change compaction strategy of tables with data? Which compaction strategy will be ideal for data directories in JBOD ? Date: Thu, 30 Oct 2014 11:16:59 -0700 Subject: Re: Commissioning failure From: rc...@eventbrite.com To: user@cassandra.apache.org On Wed, Oct 29, 2014 at 10:39 PM, Aravindan T aravinda...@tcs.com wrote: What could be the reasons for the stream error other than SSTABLE corruption? There's tons of reasons streams fail. Cassandra team is aware of how painful it makes things, so they are working on them. Be sure that a firewall is not dropping long running connections. =Robhttp://twitter.com/rcolidba
Re: Commissioning failure
You can change it on the fly. That will just compact all the data that you have so it will take a long time and cause some io load. Hannu On 31.10.2014, at 14.07, venkat sam samvenkat...@outlook.com wrote: Yes Hannu, Initially for one month we didn't face any problem. But once tables got bigger we are getting the disk space issues. Can I change the compaction strategy. Will changing compaction strategy have an impact on data consistency? Will it cause corruption of SSTable . -Venkat Date: Fri, 31 Oct 2014 13:43:11 +0200 Subject: Re: Commissioning failure From: hkro...@gmail.com To: user@cassandra.apache.org Hi, I think only LevelledCompactionStrategy makes sense on JBOD because that can distribute data more evenly. Although I don't know what is the exact strategy where each compaction strategy will store sstables. If you use SizeTieredCompactionStrategy you might run into problems when sstables get big enough. I think the theoretical maximum size for an STCS table is the half of one disk size. Because you might be able to run major compaction in that situation. I wouldn't actually use JBOD with anything else than LCS. With smaller tables it doesn't really matter that much but with big tables you would run into problem with anything else. Please correct me if I am wrong. Hannu 2014-10-31 12:16 GMT+02:00 venkat sam samvenkat...@outlook.com: Thanks Rob. We have disabled firewalls between the nodes and yet getting the same error. I have one more doubt. In our cluster we configured size tiered compaction strategy on JBOD and we are facing issues like uneven distribution of data. Is it possible to change compaction strategy of tables with data? Which compaction strategy will be ideal for data directories in JBOD ? Date: Thu, 30 Oct 2014 11:16:59 -0700 Subject: Re: Commissioning failure From: rc...@eventbrite.com To: user@cassandra.apache.org On Wed, Oct 29, 2014 at 10:39 PM, Aravindan T aravinda...@tcs.com wrote: What could be the reasons for the stream error other than SSTABLE corruption? There's tons of reasons streams fail. Cassandra team is aware of how painful it makes things, so they are working on them. Be sure that a firewall is not dropping long running connections. =Rob http://twitter.com/rcolidba
Re: Commissioning failure
On Wed, Oct 29, 2014 at 10:39 PM, Aravindan T aravinda...@tcs.com wrote: What could be the reasons for the stream error other than SSTABLE corruption? There's tons of reasons streams fail. Cassandra team is aware of how painful it makes things, so they are working on them. Be sure that a firewall is not dropping long running connections. =Rob http://twitter.com/rcolidba
Re: Commissioning failure
On Wed, Oct 29, 2014 at 12:49 PM, venkat sam samvenkat...@outlook.com wrote: I have a 5 node cassandra cluster and i commissioned 1 new node to the cluster. when i added 1 node. it received streams from 3 nodes out of which 2 were completed successfully and one stream got failed. how can i resume the stream which has failed? You can't, you have to wipe the node and start over. =Rob http://twitter.com/rcolidba
Re: Commissioning failure
What could be the reasons for the stream error other than SSTABLE corruption? Aravind -Robert Coli rc...@eventbrite.com wrote: - To: user@cassandra.apache.org user@cassandra.apache.org From: Robert Coli rc...@eventbrite.com Date: 10/30/2014 02:21AM Subject: Re: Commissioning failure On Wed, Oct 29, 2014 at 12:49 PM, venkat sam samvenkat...@outlook.com wrote: I have a 5 node cassandra cluster and i commissioned 1 new node to the cluster. when i added 1 node. it received streams from 3 nodes out of which 2 were completed successfully and one stream got failed. how can i resume the stream which has failed? You can't, you have to wipe the node and start over. =Rob http://twitter.com/rcolidba =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
