Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 585ED11886 for ; Wed, 30 Jul 2014 13:11:51 +0000 (UTC) Received: (qmail 75352 invoked by uid 500); 30 Jul 2014 13:11:43 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 75146 invoked by uid 500); 30 Jul 2014 13:11:43 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 75130 invoked by uid 500); 30 Jul 2014 13:11:43 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 75127 invoked by uid 99); 30 Jul 2014 13:11:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jul 2014 13:11:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeremy.jongsma@barchart.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jul 2014 13:11:39 +0000 Received: by mail-qa0-f49.google.com with SMTP id dc16so1242021qab.22 for ; Wed, 30 Jul 2014 06:11:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=q94tWIfI88Za7bgwQN4p0g1YzdMX1K98HVoNGWSLNwE=; b=cf0Muv/NnIAwJCk6r/cbB/nVYEd8gy6kjhNfl8wBuHjrbyhR3Yma2QbHI9WG39dzKo Z1yJiLNtSdb7iTpZYL9Cnf7MpUpB8MCzlpyQ5mLnT0Hx3jLhqHKxomc/bZT/BktoGmR3 9zOWbN8IKnS7RnZJOondD9przQmYFgTxo6+y48NfktiAaAqg1T1harTzD7BbeyHxBt3R AGfHCQLZbZG9PaX9C3e1/ulYPJgRJvP2nPxYffB6Y74C4TDH0hp6ryDu0Rs+wPjgLpq2 GkATJ4agiV1u8wxcArdWLkrrfOPsfhh+wPkkyukcbScQvUmrBWJiHiIGkrolB4Mu53vB V03w== X-Gm-Message-State: ALoCoQmK5SjEhnOVvJ6kd2l6rRXrjFLkBQu4J/6qGP3MgBrCmInmD8GAocrJF6o8Y3wJxmUH2gds MIME-Version: 1.0 X-Received: by 10.224.11.212 with SMTP id u20mr6828009qau.82.1406725878994; Wed, 30 Jul 2014 06:11:18 -0700 (PDT) Received: by 10.96.187.130 with HTTP; Wed, 30 Jul 2014 06:11:18 -0700 (PDT) Received: by 10.96.187.130 with HTTP; Wed, 30 Jul 2014 06:11:18 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Jul 2014 08:11:18 -0500 Message-ID: Subject: Re: Authentication exception From: Jeremy Jongsma To: user@cassandra.apache.org Cc: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=089e015375505071d404ff68e4fe X-Virus-Checked: Checked by ClamAV on apache.org --089e015375505071d404ff68e4fe Content-Type: text/plain; charset=UTF-8 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 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 >> wrote: >> >>> 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.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 > --089e015375505071d404ff68e4fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, and all nodes have had at least two more scheduled repa= irs since then.

On Jul 30, 2014 1:47 AM, "Or Sher" <= ;or.sher1@gmail.com> wrote:
Did you ran a repair after changing replication factor for= =C2=A0system_au= th=C2=A0?


On Tue, Jul 29, 2014 at 5:48 PM, Jeremy Jongsma = <jeremy@barchar= t.com> wrote:
This is still happening to = me; is there anything else I can check? All nodes have NTP installed, all a= re in sync, all have open communication to each other. But usually first th= ing in the morning, I get this auth exception. A little while later, it sta= rts working. I'm very puzzled.


On Tue, Jul 2= 2, 2014 at 8:53 AM, Jeremy Jongsma <jeremy@barchart.com> w= rote:
Verified all clocks are in = sync.


On Mon, Jul 21, 2014 at 10:03 PM, Rahul Menon <r= ahul@apigee.com> wrote:
I could you per= haps check your ntp?


On Tue, Jul 22, 2014 at 3:35 AM, Jeremy Jongsma = <jeremy@barchar= t.com> wrote:
I routinely get this except= ion from cqlsh on one of my clusters:

cql.cassandra.ttyp= es.AuthenticationException: AuthenticationException(why=3D'org.apache.c= assandra.exceptions.ReadTimeoutException: Operation timed out - received on= ly 2 responses.')

The system_auth keyspace is set to replicate X ti= mes 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 mi= nutes), it will let me in again.

What could be the cause of this?






--
= Or Sher
--089e015375505071d404ff68e4fe--