Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of clint.kelly@gmail.com
 designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACz-ikt4_TDqdGiigpQankJXb8Ove=XAFzCjaxdpuQ4cyg4K=Q@mail.gmail.com>
References: 
 <CACz-ikt4_TDqdGiigpQankJXb8Ove=XAFzCjaxdpuQ4cyg4K=Q@mail.gmail.com>
Date: Tue, 3 Feb 2015 07:47:29 -0800
Message-ID: 
 <CACz-iks1w8AXsqvvUesZRJYyn8baiZCdwRnSHHUeKfoPkGB+7Q@mail.gmail.com>
Subject: Re: No schema agreement from live replicas?
From: Clint Kelly <clint.kelly@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8

FWIW increasing the threshold for withMaxSchemaAgreementWaitSeconds to
30sec was enough to fix my problem---I would like to understand
whether the cluster has some kind of configuration problem that made
doing so necessary, however.

Thanks!

On Tue, Feb 3, 2015 at 7:44 AM, Clint Kelly <clint.kelly@gmail.com> wrote:
> Hi all,
>
> I have an application that uses the Java driver to create a table and then
> immediately write to it.  I see the following warning in my logs:
>
> [10.241.17.134] out: 15/02/03 09:32:24 WARN
> com.datastax.driver.core.Cluster: No schema agreement from live replicas
> after 10 s. The schema may not be up to date on some nodes.
>
> ...this seems to happen after creating a table, and the schema not being up
> to date leads to errors when trying to write the the new tables:
>
> [10.241.17.134] out: Exception in thread "main"
> com.datastax.driver.core.exceptions.InvalidQueryException: unconfigured
> columnfamily schema_hash
>
> Any suggestions on what to do about this (other than increasing
> "withMaxSchemaAgreementWaitSeconds")?  This is only a three-node test
> cluster.  I have not gotten this warning before, even on much bigger
> clusters.
>
> Best regards,
> Clint