You didn't post any timings, only when it started failing so it's unclear whether performance is dropping off or scaling in some sort of linear or non-linear fashion. Second the recommendation to do some traces which should be much more telling.
On Fri, Jun 13, 2014 at 3:34 AM, Phil Luckhurst < phil.luckhu...@powerassure.com> wrote: > But would you expect performance to drop off so quickly? At 250,000 records > we can still page through the query with LIMIT 50000 but when adding an > additional 50,000 records we can't page past the first 10,000 records even > if we drop to LIMIT 10. > > What about the case where we add 100,000 records for each indexed value? > When we do this for 2 values, i.e. 200,000 records with 2 indexed values, > we > can query all 100,000 records for one of the values using LIMIT 100000. If > we add a third indexed value with another 100,000 records then we can't > page > through any of the indexed values even though the original 2 that worked > previously have not changed. > > Phil > > > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595126.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
