cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Wong <gokoproj...@gmail.com>
Subject Re: What are problems with schema disagreement
Date Fri, 03 Jul 2015 04:31:22 GMT
On Thu, Jul 2, 2015 at 11:01 PM, graham sanderson <graham@vast.com> wrote:

> What version of C* are you running? Some versions of 2.0.x might
> occasionally fail to propagate schema changes in a timely fashion (though
> they would fix themselves eventually - in the order of a few minutes)
>
>
Hi Graham. Thanks. We are still running on 1.2.16, but we do plan to
upgrade in the near future. The load on the cluster at the time was very
very low. All nodes were responsive, except nothing was show up in the logs
after certain time, which led me to believe something happened internal,
although that was a poor wild guess.

But is it safe to be okay with schema disagreement? I worry about data
consistency if I let it sit too long.

Thanks.

John

> > On Jul 2, 2015, at 9:37 PM, John Wong <gokoproject@gmail.com> wrote:
> >
> > Hi.
> >
> > Here is a schema disagreement we encountered.
> > Schema versions:
> >         b6467059-5897-3cc1-9ee2-73f31841b0b0: [10.0.1.100, 10.0.1.109]
> >         c8971b2d-0949-3584-aa87-0050a4149bbd: [10.0.1.55, 10.0.1.16,
> 10.0.1.77]
> >         c733920b-2a31-30f0-bca1-45a8c9130a2c: [10.0.1.221]
> >
> > We deployed an application which would send a schema update (DDL=auto).
> We found this prod cluster had 3 schema difference. Other existing
> applications were fine, so some people were curious what if we left this
> problem alone until off hours.
> >
> > Is there any concerns with not resolve schema disagreement right away?
> FWIW we went ahead and restarted 221 first, and continue with the rest of
> the minors.
> >
> > Thanks.
> >
> > John
> >
>
>

Mime
View raw message