Yes, and all nodes have had at least two more scheduled repairs since then. On Jul 30, 2014 1:47 AM, "Or Sher" <or.sh...@gmail.com> wrote:
> Did you ran a repair after changing replication factor for system_auth ? > > > On Tue, Jul 29, 2014 at 5:48 PM, Jeremy Jongsma <jer...@barchart.com> > wrote: > >> This is still happening to me; is there anything else I can check? All >> nodes have NTP installed, all are in sync, all have open communication to >> each other. But usually first thing in the morning, I get this auth >> exception. A little while later, it starts working. I'm very puzzled. >> >> >> On Tue, Jul 22, 2014 at 8:53 AM, Jeremy Jongsma <jer...@barchart.com> >> wrote: >> >>> Verified all clocks are in sync. >>> >>> >>> On Mon, Jul 21, 2014 at 10:03 PM, Rahul Menon <ra...@apigee.com> wrote: >>> >>>> I could you perhaps check your ntp? >>>> >>>> >>>> On Tue, Jul 22, 2014 at 3:35 AM, Jeremy Jongsma <jer...@barchart.com> >>>> wrote: >>>> >>>>> I routinely get this exception from cqlsh on one of my clusters: >>>>> >>>>> cql.cassandra.ttypes.AuthenticationException: >>>>> AuthenticationException(why='org.apache.cassandra.exceptions.ReadTimeoutException: >>>>> Operation timed out - received only 2 responses.') >>>>> >>>>> The system_auth keyspace is set to replicate X times given X nodes in >>>>> each datacenter, and at the time of the exception all nodes are reporting >>>>> as online and healthy. After a short period (i.e. 30 minutes), it will let >>>>> me in again. >>>>> >>>>> What could be the cause of this? >>>>> >>>> >>>> >>> >> > > > -- > Or Sher >
