Hi Jason -
Did you run a major compaction after the repair completed? Do you have
other reasons besides the number/size of sstables to believe all nodes
don't have a copy of the current data at the end of the repair operation?
Thanks,
Paul
On Wed, Jun 8, 2016 at 8:12 AM, Jason Kania
If pub_timestamp could possibly match I'd suggest making it a timeuuid type
instead. With the above schema it's not a failure or data loss if the
timestamp is duplicated - your writes all probably made it - the
duplicates just got overwritten.
On Tue, Jun 14, 2016 at 9:40 PM, linbo liao
the first
time, but when I moved around to the other nodes it no longer worked.
Thanks,
Paul Fife
Hello Melinda,
1. My recommendation is to script your database creation instead of copying
database files around. You could use code executing statements via a
driver, or simply write a CQL script and execute with CQLSH to create your
schema and possibly some minimal data set if needed. This is a
Thanks Dominik - I was doing a nodetool flush like the instructions said,
but it wasn't actually flushing the system keyspace. Using nodetool flush
system made it work as expected!
Thanks,
Paul Fife
On Wed, Jun 29, 2016 at 7:37 AM, Dominik Keil <dominik.k...@movilizer.com>
wrote:
>
Hello Amit -
I can confirm that we also experienced this issue in 2.0.x and were not
able to find a solution other than a restart. Since upgrading to 2.2.x the
problem did disappear.
Thanks,
Paul Fife
On Fri, Sep 30, 2016 at 6:48 AM, Amit Singh F <amit.f.si...@ericsson.com>
wrote:
&g
