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 > >
