Yes, and all nodes have had at least two more scheduled repairs since then.
On Jul 30, 2014 1:47 AM, "Or Sher" wrote:
> Did you ran a repair after changing replication factor for system_auth ?
>
>
> On Tue, Jul 29, 2014 at 5:48 PM, Jeremy Jongsma
> wrote:
>
>> This is still happening to me; is t
Did you ran a repair after changing replication factor for system_auth ?
On Tue, Jul 29, 2014 at 5:48 PM, Jeremy Jongsma 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
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
Verified all clocks are in sync.
On Mon, Jul 21, 2014 at 10:03 PM, Rahul Menon wrote:
> I could you perhaps check your ntp?
>
>
> On Tue, Jul 22, 2014 at 3:35 AM, Jeremy Jongsma
> wrote:
>
>> I routinely get this exception from cqlsh on one of my clusters:
>>
>> cql.cassandra.ttypes.Authentica
I could you perhaps check your ntp?
On Tue, Jul 22, 2014 at 3:35 AM, Jeremy Jongsma wrote:
> I routinely get this exception from cqlsh on one of my clusters:
>
> cql.cassandra.ttypes.AuthenticationException:
> AuthenticationException(why='org.apache.cassandra.exceptions.ReadTimeoutException:
>
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
