Hi Edward, Thanks a lot for your help. It helped us narrow down the problem.
Regards On Mon, Oct 17, 2016 at 9:33 PM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > https://issues.apache.org/jira/browse/CASSANDRA-11198 > > Which has problems "maybe" fixed by: > > https://issues.apache.org/jira/browse/CASSANDRA-11475 > > Which has it's own set of problems. > > One of these patches was merged into 3.7 which tells you are running a > version 3.6 with known bugs. Also as the feature is "new ish" you should be > aware that "new ish" major features usually take 4-6 versions to solidify. > > > > On Mon, Oct 17, 2016 at 3:19 AM, siddharth verma < > sidd.verma29.l...@gmail.com> wrote: > >> Hi, >> We have a base table with ~300 million entries. >> And in a recent sanity activity, I saw approx ~33k entires(in one DC) >> which were in the materialized view, but not in the base table. (reads with >> quorum, DCAware) >> (I haven't done it the other way round yet, i.e. entries in base table >> but not in materialized view) >> >> Could someone suggest a possible cause for the same? >> We saw some glitches in cassandra cluster >> 1. node down. >> If this is the case, will repair fix the issue? >> 2. IOPS maxed out in one DC. >> 3. Another DC added with some glitches. >> >> Could someone suggest how could we replicate inconsistency between base >> table and materialized view. Any help would be appreciated. >> >> C* 3.6 >> Regards >> SIddharth Verma >> (Visit https://github.com/siddv29/cfs for a high speed cassandra full >> table scan) >> > > -- Siddharth Verma (Visit https://github.com/siddv29/cfs for a high speed cassandra full table scan)
