Ok thanks - I guess I can at least enable the debug logging added for that issue to see if it is deliberately choosing not to pull the schema… no repro case, but it may happen again!
On Aug 8, 2014, at 4:21 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Fri, Aug 8, 2014 at 1:45 PM, graham sanderson <gra...@vast.com> wrote: > We have some data that is partitioned in tables created periodically (once a > day). This morning, this automated process timed out because the schema did > not reach agreement quickly enough after we created a new empty table. > > I have seen this on 1.2.16, but it was supposed to be fixed in 1.2.18 and > 2.0.7. > > https://issues.apache.org/jira/browse/CASSANDRA-6971 > > If you can repro on 2.0.9, I would file a JIRA with repro steps and link it > on a reply to this thread. > > =Rob
smime.p7s
Description: S/MIME cryptographic signature
