Re: re-add column with same UDT fail

) isCompatibleWith check, it would have passed since it treats both as tuple type. Also, you are able to re-add the column as a tuple, which would be incompatible with non-frozen UDT data. On Thu, Nov 21, 2019 at 5:59 AM Tommy Stendahl wrote: Hi, I run in to problem with 3.11.5, I think its related

re-add column with same UDT fail

Hi, I run in to problem with 3.11.5, I think its related to "* Toughen up column drop/recreate type validations (CASSANDRA-15204)" I have a user defined type and I have a table with a column that has this UDF as type, if I drop the column and recreate it with the same name it fails. I think

Re: Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException:

Hi, Have you tried to change the page size? I think cqlsh use a page size of 100 and the java driver use 5000 as default, sometimes this can make a difference. /Tommy On tis, 2019-04-16 at 23:38 -0700, Dinesh Joshi wrote: More info with detailed explanation:

Using compressed hints in Cassandra 3.0

Hi, Have anyone used compressed hints in Cassandra 3.0? or are we the only ones that do this? If you use compressed hints have ever seen that sending the hints fails and you get this exception in the log: 2018-04-04T13:27:48.948+0200 ERROR [HintsDispatcher:14] CassandraDaemon.java:207

Re: Node fails to start - error in Log (CassandraDaemon.java:710 - Exception encountered during startup)

Hi, Check the value of "concurrent_materialized_view_writes" in the cassandra.yaml file. /Tommy On 2018-02-23 12:11, Jonathan Baynes wrote: Hi Community, Can anyone give me some pointers where to look, or start to look for where this issue is coming from? On startup I get this in the

Re: Upgrade to 3.11.1 give SSLv2Hello is disabled error

I have continued the upgrade of the cluster using the default protocol setting and after upgrading all nodes there were no problems switching back to "TLSv1.2". But I will try to reproduce the problem using a ccm cluster, I think that should be relatively easy, and when  can try the

Re: Upgrade to 3.11.1 give SSLv2Hello is disabled error

the protocol names differ between some JRE vendors. With IBM Java for instance the protocol name would be TLSv12 ( without . ). Are you using the same JRE on all nodes and is the protocol name and cipher names exactly the same on all nodes? 2018-01-17 14:51 GMT+01:00 Tommy Stendahl <tommy.st

Re: Upgrade to 3.11.1 give SSLv2Hello is disabled error

side, but not on the server side. Cassandra should be able to accept SSLv2Hello connections from 3.0 nodes just fine. What JRE do you use? Any custom ssl specific settings that might be effective here? On 16.01.2018 15:13, Tommy Stendahl wrote: Hi, I have problems upgrading a cluster from 3.0.14

Re: Upgrade to 3.11.1 give SSLv2Hello is disabled error

Thanks for your response. I removed the protocol setting from the server_encryption_options in the 3.11.1 node so it use the default value instead and now it works. I have to analyse if this has any impact on my security requirements but at least its working now. /Tommy On 2018-01-16

Upgrade to 3.11.1 give SSLv2Hello is disabled error

Hi, I have problems upgrading a cluster from 3.0.14 to 3.11.1 but when I upgrade the first node it fails to gossip. I have server encryption enabled on all nodes with this setting: server_encryption_options:     internode_encryption: all     keystore:

Re: lots of DigestMismatchException in cassandra3

Hi, Could it be CASSANDRA-12090 ? Regards, /Tommy On 2016-11-17 09:47, adeline@thomsonreuters.com wrote: Hi, We are using Cassandra 3.7 and we have a single datacenter of 4 nodes, RF =3, and the consistency level is quorum. I

Re: Why I can not do a "count(*) ... allow filtering " without facing operation timeout?

Hi, Checkout CASSANDRA-8899, my guess is that you have to increase the timeout in cqlsh. /Tommy On 2015-09-04 10:31, shahab wrote: Hi, This is probably a silly problem , but it is really serious for me. I have a cluster of 3 nodes, with replication factor 2. But still I can not do a

Re: TTL question

which you've defined. Second mutation has exactly the same primary key - it overwrote row that you previously had. On Fri, Aug 28, 2015 at 1:14 PM, Tommy Stendahl tommy.stend...@ericsson.com wrote: Hi, I did a small test using TTL but I didn't get the result I expected. I did this in sqlsh: cqlsh

TTL question

Hi, I did a small test using TTL but I didn't get the result I expected. I did this in sqlsh: cqlsh create TABLE foo.bar ( key int, cluster int, col int, PRIMARY KEY (key, cluster)) ; cqlsh INSERT INTO foo.bar (key, cluster ) VALUES ( 1,1 ); cqlsh SELECT * FROM foo.bar ; key | cluster |

Re: TTL question

SELECT * FROM foo.bar ; key | cluster | col -+-+-- 1 | 1 | null (1 rows) /Tommy On 2015-08-28 14:20, Jacques-Henri Berthemet wrote: What if you use an update statement in the second query? -- Jacques-Henri Berthemet -Original Message- From: Tommy Stendahl

Re: OperationTimedOut in selerct count statement in cqlsh

Hi, Checkout CASSANDRA-8899, my guess is that you have to increase the timeout in cqlsh. /Tommy On 2015-04-22 11:15, Mich Talebzadeh wrote: Hi, I have a table of 300,000 rows. When I try to do a simple cqlsh:ase select count(1) from t; OperationTimedOut: errors={}, last_host=127.0.0.1