Is there a C* summit this year?
Hi All, I was wondering if there is going to be a C* summit this year? If so, when can we expect? Thanks!
Re: Is it safe to upgrade 2.2.6 to 3.0.13?
We upgraded from 2.2.5 to 3.0.11 and it works fine. I will suggest not to go with 3.013, we are seeing some issues with schema mismatch due to which we had to rollback to 3.0.11. Thanks, Varun > On May 19, 2017, at 7:43 AM, Stefano Ortolani wrote: > > Here (https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt) is > stated that the minimum supported version for the 2.2.X branch is 2.2.2. > >> On Fri, May 19, 2017 at 2:16 PM, Nicolas Guyomar >> wrote: >> Hi Xihui, >> >> I was looking for this documentation also, but I believe datastax removed >> it, and it is not available yet on the apache website >> >> As far as I remember, intermediate version was needed if C* Version < 2.1.7. >> >> You should be safe starting from 2.2.6, but testing the upgrade on a >> dedicated platform is always a good idea. >> >> Nicolas >> >>> On 19 May 2017 at 09:02, Xihui He wrote: >>> Hi All, >>> >>> We are planning to upgrade our production cluster to 3.x, but I can't find >>> the upgrade guide anymore. >>> Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version necessary? >>> >>> Thanks, >>> Xihui >> >
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
Yes the bugs need to be fixed, but as a work around on dev environment, you can enable cassandra.yaml option to override any corrupted commit log file. Thanks, Varun > On May 19, 2017, at 11:31 AM, Jeff Jirsa wrote: > > > >> On 2017-05-19 08:13 (-0700), Haris Altaf wrote: >> Hi All, >> I am using Cassandra 3.10 for my project and whenever my local windows >> system, which is my development environment, crashes then cassandra server >> is unable to start. I have to delete commitlog directory after every system >> crash. This is actually annoying and what's the purpose of commitlog if it >> itself gets crashed. I have uploaded the entire dump of Cassandra Server >> (along with logs, commitlogs, data, configs etc) at the link below. Kindly >> share its solution. I believe it needs to be fixed. >> > > You need to share the exact stack trace. In cassandra 3.0+, we became much > less tolerant of surprises in commitlog state - perhaps a bit too aggressive, > failing to start in many cases when only minor things were wrong. We've > recently fixed a handful of these, but they may not be released yet for the > version you're using. > > > > - > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
Re: Cassandra Node Density thresholds
50% free is unnecessary. The only reason to keep that much free is if you wanted to regularly run major compactions, which you shouldn't. I'd aim for 75%. Bootstrap new nodes in when you get close to that number. Ensure you don't have any sstables larger than your available space and you'll be just fine. Run cleanup on all nodes after you finish bootstrapping new nodes in to reclaim disk space. On Fri, May 19, 2017 at 9:42 AM Nitan Kainth wrote: > Asad, > > Ideally you should keep 50% free disk space. Yes, right now you have good > option to scale horizontally or add more disk space if you can. Adding more > nodes will give you more scalability for reads/writes and disk space will > just give you more capacity for current load. > > Sent from my iPhone > > On May 19, 2017, at 11:04 AM, ZAIDI, ASAD A wrote: > > Hello Folks - > > I'm using open source apache Cassandra 2.2 .My cluster is spread over 14 > nodes in cluster in two data centers. > > > > My DC1 data center nodes are reaching 2TB of consumed volume. we don't > have much space left on disk. > > I am wondering if there is guideline available that can point me to > certain best practice that describe when we should add more nodes to the > cluster. should we add more storage or add more nodes. I guess we should > scale Cassandra horizontally so adding node may be better option.. i am > looking for a criteria that describes node density thresholds, if there are > any. > > Can you guys please share your thoughts , experience. I'll much appreciate > your reply. Thanks/Asad > > > > > >
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
On 2017-05-19 08:13 (-0700), Haris Altaf wrote: > Hi All, > I am using Cassandra 3.10 for my project and whenever my local windows > system, which is my development environment, crashes then cassandra server > is unable to start. I have to delete commitlog directory after every system > crash. This is actually annoying and what's the purpose of commitlog if it > itself gets crashed. I have uploaded the entire dump of Cassandra Server > (along with logs, commitlogs, data, configs etc) at the link below. Kindly > share its solution. I believe it needs to be fixed. > You need to share the exact stack trace. In cassandra 3.0+, we became much less tolerant of surprises in commitlog state - perhaps a bit too aggressive, failing to start in many cases when only minor things were wrong. We've recently fixed a handful of these, but they may not be released yet for the version you're using. - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
Re: Cassandra Node Density thresholds
Asad, Ideally you should keep 50% free disk space. Yes, right now you have good option to scale horizontally or add more disk space if you can. Adding more nodes will give you more scalability for reads/writes and disk space will just give you more capacity for current load. Sent from my iPhone > On May 19, 2017, at 11:04 AM, ZAIDI, ASAD A wrote: > > Hello Folks - > > I'm using open source apache Cassandra 2.2 .My cluster is spread over 14 > nodes in cluster in two data centers. > > My DC1 data center nodes are reaching 2TB of consumed volume. we don't have > much space left on disk. > > I am wondering if there is guideline available that can point me to certain > best practice that describe when we should add more nodes to the cluster. > should we add more storage or add more nodes. I guess we should scale > Cassandra horizontally so adding node may be better option.. i am looking for > a criteria that describes node density thresholds, if there are any. > > Can you guys please share your thoughts , experience. I'll much appreciate > your reply. Thanks/Asad > > > >
Re: Cassandra Node Density thresholds
500 nodes, 20tb of ACTIVE DATA per node in hdfs, no brainer, no problem. But remember the cross DC traffic will get substantial. “All men dream, but not equally. Those who dream by night in the dusty recesses of their minds wake up in the day to find it was vanity, but the dreamers of the day are dangerous men, for they may act their dreams with open eyes, to make it possible.” — T.E. Lawrence sent from my mobile Daemeon Reiydelle skype daemeon.c.m.reiydelle USA 415.501.0198 On May 19, 2017 9:05 AM, "ZAIDI, ASAD A" wrote: > Hello Folks - > > I'm using open source apache Cassandra 2.2 .My cluster is spread over 14 > nodes in cluster in two data centers. > > > > My DC1 data center nodes are reaching 2TB of consumed volume. we don't > have much space left on disk. > > I am wondering if there is guideline available that can point me to > certain best practice that describe when we should add more nodes to the > cluster. should we add more storage or add more nodes. I guess we should > scale Cassandra horizontally so adding node may be better option.. i am > looking for a criteria that describes node density thresholds, if there are > any. > > Can you guys please share your thoughts , experience. I'll much appreciate > your reply. Thanks/Asad > > > > >
Cassandra Node Density thresholds
Hello Folks - I'm using open source apache Cassandra 2.2 .My cluster is spread over 14 nodes in cluster in two data centers. My DC1 data center nodes are reaching 2TB of consumed volume. we don't have much space left on disk. I am wondering if there is guideline available that can point me to certain best practice that describe when we should add more nodes to the cluster. should we add more storage or add more nodes. I guess we should scale Cassandra horizontally so adding node may be better option.. i am looking for a criteria that describes node density thresholds, if there are any. Can you guys please share your thoughts , experience. I'll much appreciate your reply. Thanks/Asad
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
I have seen this happen as well. Deleting commit logs helps to Cassandra start but of course if you are very unlucky you might lose some data. Hannu > On 19 May 2017, at 18.13, Haris Altaf wrote: > > Hi All, > I am using Cassandra 3.10 for my project and whenever my local windows > system, which is my development environment, crashes then cassandra server is > unable to start. I have to delete commitlog directory after every system > crash. This is actually annoying and what's the purpose of commitlog if it > itself gets crashed. I have uploaded the entire dump of Cassandra Server > (along with logs, commitlogs, data, configs etc) at the link below. Kindly > share its solution. I believe it needs to be fixed. > > Crashed Cassandra 3.10 Server Link: > https://drive.google.com/open?id=0BxE52j6oo6cEYXJvdGhBNHNQd0E > > regards, > Haris > -- > regards, > Haris
Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
Hi All, I am using Cassandra 3.10 for my project and whenever my local windows system, which is my development environment, crashes then cassandra server is unable to start. I have to delete commitlog directory after every system crash. This is actually annoying and what's the purpose of commitlog if it itself gets crashed. I have uploaded the entire dump of Cassandra Server (along with logs, commitlogs, data, configs etc) at the link below. Kindly share its solution. I believe it needs to be fixed. Crashed Cassandra 3.10 Server Link: https://drive.google.com/open?id=0BxE52j6oo6cEYXJvdGhBNHNQd0E regards, Haris -- regards, Haris
Re: Is it safe to upgrade 2.2.6 to 3.0.13?
Here (https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt) is stated that the minimum supported version for the 2.2.X branch is 2.2.2. On Fri, May 19, 2017 at 2:16 PM, Nicolas Guyomar wrote: > Hi Xihui, > > I was looking for this documentation also, but I believe datastax removed > it, and it is not available yet on the apache website > > As far as I remember, intermediate version was needed if C* Version < > 2.1.7. > > You should be safe starting from 2.2.6, but testing the upgrade on a > dedicated platform is always a good idea. > > Nicolas > > On 19 May 2017 at 09:02, Xihui He wrote: > >> Hi All, >> >> We are planning to upgrade our production cluster to 3.x, but I can't >> find the upgrade guide anymore. >> Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version >> necessary? >> >> Thanks, >> Xihui >> > >
Re: Is it safe to upgrade 2.2.6 to 3.0.13?
Hi Xihui, I was looking for this documentation also, but I believe datastax removed it, and it is not available yet on the apache website As far as I remember, intermediate version was needed if C* Version < 2.1.7. You should be safe starting from 2.2.6, but testing the upgrade on a dedicated platform is always a good idea. Nicolas On 19 May 2017 at 09:02, Xihui He wrote: > Hi All, > > We are planning to upgrade our production cluster to 3.x, but I can't find > the upgrade guide anymore. > Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version > necessary? > > Thanks, > Xihui >
Is it safe to upgrade 2.2.6 to 3.0.13?
Hi All, We are planning to upgrade our production cluster to 3.x, but I can't find the upgrade guide anymore. Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version necessary? Thanks, Xihui
