Re: Cqlsh timeout and schema refresh exceptions

Hi Matija, I know about the API. I am using isSchemaInAgreement, but problem is that when I am giving CREATE TABLE requests quickly. its timing out after 30 seconds. Same CF creation happens successfully(with agreement) *within 2 seconds* when I give it in isolation on a fresh cluster, or after go

Re: Cqlsh timeout and schema refresh exceptions

There is an exposed API for schema agreement and I would advise you to use that if you can. Look at this JIRA ticket . On Mon, Dec 19, 2016 at 8:46 PM, Vladimir Yudovin wrote: > Regarding schema agreement - try to increase time between CF creat

Re: Cqlsh timeout and schema refresh exceptions

Regarding schema agreement - try to increase time between CF creation. Also stress-tool waits for schema, look on its code, probably it uses some methods to ensure schema distribution. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Mon, 19 Dec 2016 14:35:

Re: Cqlsh timeout and schema refresh exceptions

Thanks Vladimir! Is there any known issue in 3.0.10, where creating "CF with large number of cols" or "creating large number of CFs quickly" one after other gives schema agreement issue? What other things can I try to support ~12000 CF without hitting schema agreement related issues? I can put mo

Re: Cqlsh timeout and schema refresh exceptions

>I want to dig deeper into what all things happen in C* at time of CF creation It starts somewhere in MigrationManager.announceNewColumnFamily function, I guess. >imitation of number of keyspaces which can be created. Actually it's CF limitation, not keyspaces. >if you can also poin

Re: Cqlsh timeout and schema refresh exceptions

Hi Vladimir, Thanks for the response. When I see *"**com.datastax.driver.core.ControlConnection"* exceptions, I see that keyspaces and CF are created. But when I create CF with large number of columns(2400 cols) quickly one after the other(with 2 seconds gap between CREATE TABLE queries), I get s

Re: Cqlsh timeout and schema refresh exceptions

Hi, Question: Does C* reads some schema/metadata on calling cqlsh, which is causing timeout with large number of keyspaces? A lot ). cqlsh reads schemas, cluster topology, each node tokens, etc. You can just capture TCP port 9042 (unless you use SSL) and view all negotiation between cqlsh a

Cqlsh timeout and schema refresh exceptions

Hi All, I have a 2 node cluster(32gb ram/8cpu) running 3.0.10 and I created 50 keyspaces in it. Each keyspace has 25 CF. Column count in each CF ranges between 5 to 30. I am getting few issues once keyspace count reaches ~50. *Issue 1:* When I try to use cqlsh, I get timeout. *$ cqlsh `hostnam