> Seems like when we have updates that are large (10k rows in one mutate) the > problem is more likely to occur. 10K rows in one mutate is a very bad idea. It will take the nodes a long time to process them, risking time out, and it will essentially starving other requests.
You should also specify a CL level so we understand if this you are using cassandra in an eventually consistent or strongly consistent way. Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 19/03/2013, at 11:02 AM, Brett Tinling <btinl...@lacunasystems.com> wrote: > Aaron, > > No recipe yet. It pops up randomly and, i think due to the nature of our > app, goes away. > > Seems like when we have updates that are large (10k rows in one mutate) the > problem is more likely to occur. > > I'll try to workout a repro... > > -Brett > > On Mar 18, 2013, at 10:18 AM, aaron morton wrote: > >> Brett, >> Do you have some steps to reproduce the problem ? If so please create a >> ticket on jira. >> >> Cheers >> >> ----------------- >> Aaron Morton >> Freelance Cassandra Consultant >> New Zealand >> >> @aaronmorton >> http://www.thelastpickle.com >> >> On 16/03/2013, at 11:40 AM, Janne Jalkanen <janne.jalka...@ecyrd.com> wrote: >> >>> >>> This could be either of the following bugs (which might be the same thing). >>> I get it too every time I recycle a node on 1.1.10. >>> >>> https://issues.apache.org/jira/browse/CASSANDRA-4973 >>> or >>> https://issues.apache.org/jira/browse/CASSANDRA-4785 >>> >>> /Janne >>> >>> On Mar 15, 2013, at 23:24 , Brett Tinling <btinl...@lacunasystems.com> >>> wrote: >>> >>>> We have a CF with an indexed column 'type', but we get incomplete results >>>> when we query that CF for all rows matching 'type'. We can find the >>>> missing rows if we query by key. >>>> >>>> * we are seeing this on a small, single node, 1.2.2 instance with few rows. >>>> * we use thrift execute_cql_query, no CL is specified >>>> * none of repair, restart, compact, scrub helped >>>> >>>> Finally, nodetool rebuild_index fixed it. >>>> >>>> Is index rebuild something we need to do periodically? How often? Is >>>> there a way to know when it needs to be done? Do we have to run rebuild >>>> on all nodes? >>>> >>>> We have not noticed this until 1.2 >>>> >>>> Regards, >>>> - Brett >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >
