Re: Error after 3.1.0 to 3.11.2 upgrade

No applicatiom isnt impacted ..no complains .. Also its an 4 node cluster in lower non production and all are on same version. On Friday, May 11, 2018, Jeff Jirsa wrote: > The read is timing out - is the cluster healthy? Is it fully upgraded or > mixed versions? Repeated isn’t

Re: Error after 3.1.0 to 3.11.2 upgrade

The read is timing out - is the cluster healthy? Is it fully upgraded or mixed versions? Repeated isn’t great, but is the application impacted? -- Jeff Jirsa > On May 12, 2018, at 6:17 AM, Abdul Patel wrote: > > Seems its coming from 3.10, got bunch of them today for

Re: Error after 3.1.0 to 3.11.2 upgrade

Hi, Did you check replication strategy and amounts of replicas of system_auth keyspace? Hannu > Abdul Patel kirjoitti 12.5.2018 kello 5.21: > > No applicatiom isnt impacted ..no complains .. > Also its an 4 node cluster in lower non production and all are on same >

Error after 3.1.0 to 3.11.2 upgrade

HI All, Seen below stack trace messages , in errorlog one day after upgrade. one of the blogs said this might be due to old drivers, but not sure on it. FYI : INFO [HANDSHAKE-/10.152.205.150] 2018-05-09 10:22:27,160 OutboundTcpConnection.java:510 - Handshaking version with /10.152.205.150

Re: Error after 3.1.0 to 3.11.2 upgrade

That looks like Cassandra 3.10 not 3.11.2 It’s also just the auth cache failing to refresh - if it’s transient it’s probably not a big deal. If it continues then there may be an issue with the cache refresher. -- Jeff Jirsa > On May 12, 2018, at 5:55 AM, Abdul Patel

Re: Error after 3.1.0 to 3.11.2 upgrade

Seems its coming from 3.10, got bunch of them today for 3.11.2, so if this is repeatedly coming , whats solution for this? WARN [Native-Transport-Requests-24] 2018-05-11 16:46:20,938 CassandraAuthorizer.java:96 - CassandraAuthorizer failed to authorize # for ERROR [Native-Transport-Requests-24]

Re: Database not getting updated

This usually happens when you’ve got weird timestamps or a delete in the future - check your clocks, make sure your timestamp resolution uses the same units in all applications (likely microseconds), make sure you’re running NTP everywhere -- Jeff Jirsa > On May 11, 2018, at 5:37 PM,

Database not getting updated

Dear community, Sometimes I've noticed that the changes done in the database, even when done successfully are not reflected e.g. I added/deleted a row via cqlsh/Datastax C++ driver, the command/API was successful, yet when I fetched the contents of the table, the row that I had added/deleted,

RE: Database not getting updated

Who’s awesome? Jeff Jirsa is awesome! ☺ Thanks and regards, Vishal Sharma From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Friday, May 11, 2018 5:51 PM To: user@cassandra.apache.org Subject: Re: Database not getting updated This usually happens when you’ve got weird timestamps or a delete in

Re: Cassandra upgrade from 2.1 to 3.0

After further analyzing the data. I see some pattern. The rows which were updated in last 2-3 weeks, the column which were not part of this update have the null values.  Has anyone encountered this issue during the upgrade? Thank you, On Thursday, 10 May 2018, 19:49:50 GMT-7,