RE: [EXTERNAL] Re: Error after 3.1.0 to 3.11.2 upgrade

fetched all the time (especially with the internal Cassandra Authorizer/Authenticator). Sean Durity From: Jeff Jirsa <jji...@gmail.com> Sent: Saturday, May 12, 2018 9:21 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: Error after 3.1.0 to 3.11.2 upgrade RF of one means al

Re: Error after 3.1.0 to 3.11.2 upgrade

RF of one means all auth requests go to the same node, so they’re more likely to time out if that host is overloaded or restarts Increasing it distributed the queries among more hosts -- Jeff Jirsa > On May 12, 2018, at 6:11 AM, Abdul Patel wrote: > > Yeah found that

Re: Error after 3.1.0 to 3.11.2 upgrade

Yeah found that all had 3 replication factor and system_auth had 1 , chnaged to 3 now ..so was this issue due to system_auth replication facyor mismatch? On Saturday, May 12, 2018, Hannu Kröger wrote: > Hi, > > Did you check replication strategy and amounts of replicas of

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 >

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

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: 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

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