beware of https://issues.apache.org/jira/browse/CASSANDRA-3820 though if you have many keys per node
other than that, yep, it seems solid /Marcus On Wed, Feb 29, 2012 at 6:20 PM, Thibaut Britz < thibaut.br...@trendiction.com> wrote: > Thanks! > > We will test it on our test cluster in the coming weeks and hopefully put > it into production on our 200 node main cluster. :) > > Thibaut > > On Wed, Feb 29, 2012 at 5:52 PM, Edward Capriolo <edlinuxg...@gmail.com>wrote: > >> On Wed, Feb 29, 2012 at 10:35 AM, Thibaut Britz >> <thibaut.br...@trendiction.com> wrote: >> > Any more feedback on larger deployments of 1.0.*? >> > >> > We are eager to try out the new features in production, but don't want >> to >> > run into bugs as on former 0.7 and 0.8 versions. >> > >> > Thanks, >> > Thibaut >> > >> > >> > >> > On Tue, Jan 31, 2012 at 6:59 AM, Ben Coverston < >> ben.covers...@datastax.com> >> > wrote: >> >> >> >> I'm not sure what Carlo is referring to, but generally if you have >> done, >> >> thousands of migrations you can end up in a situation where the >> migrations >> >> take a long time to replay, and there are some race conditions that >> can be >> >> problematic in the case where there are thousands of migrations that >> may >> >> need to be replayed while a node is bootstrapped. If you get into this >> >> situation it can be fixed by copying migrations from a known good >> schema to >> >> the node that you are trying to bootstrap. >> >> >> >> Generally I would advise against frequent schema updates. Unlike rows >> in >> >> column families the schema itself is designed to be relatively static. >> >> >> >> On Mon, Jan 30, 2012 at 2:14 PM, Jim Newsham <jnews...@referentia.com> >> >> wrote: >> >>> >> >>> >> >>> Could you also elaborate for creating/dropping column families? We're >> >>> currently working on moving to 1.0 and using dynamically created >> tables, so >> >>> I'm very interested in what issues we might encounter. >> >>> >> >>> So far the only thing I've encountered (with 1.0.7 + hector 1.0-2) is >> >>> that dropping a cf may sometimes fail with UnavailableException. I >> think >> >>> this happens when the cf is busy being compacted. When I sleep/retry >> within >> >>> a loop it eventually succeeds. >> >>> >> >>> Thanks, >> >>> Jim >> >>> >> >>> >> >>> On 1/26/2012 7:32 AM, Pierre-Yves Ritschard wrote: >> >>>> >> >>>> Can you elaborate on the composite types instabilities ? is this >> >>>> specific to hector as the radim's posts suggests ? >> >>>> These one liner answers are quite stressful :) >> >>>> >> >>>> On Thu, Jan 26, 2012 at 1:28 PM, Carlo Pires<carlopi...@gmail.com> >> >>>> wrote: >> >>>>> >> >>>>> If you need to use composite types and create/drop column families >> on >> >>>>> the >> >>>>> fly you must be prepared to instabilities. >> >>>>> >> >>> >> >> >> >> >> >> >> >> -- >> >> Ben Coverston >> >> DataStax -- The Apache Cassandra Company >> >> >> > >> >> I would call 1.0.7 rock fricken solid. Incredibly stable. It has been >> that way since I updated to 0.8.8 really. TBs of data, billions of >> requests a day, and thanks to JAMM, memtable type auto-tuning, and >> other enhancements I rarely, if ever, find a node in a state where it >> requires a restart. My clusters are beast-ing. >> >> There always is bugs in software, but coming from a guy who ran >> cassandra 0.6.1.Administration on my Cassandra cluster is like a >> vacation now. >> > >
