Re: Read exceptions after upgrading to 3.0.10

2017-02-24 Thread kurt greaves
That stacktrace generally implies your clients are resetting connections. The reconnection policy probably handles the issue automatically, however worth investigating. I don't think it normally causes statuslogger output however, what were the log messages prior to the stacktrace? On 24 February

Re: Read exceptions after upgrading to 3.0.10

2017-02-24 Thread Carlos Rolo
By any chances are you using the PHP/C++ driver? -- --

Read exceptions after upgrading to 3.0.10

2017-02-23 Thread Meg Mara
Hello, We have a 6 node cluster which was recently upgraded from 2.2.5 to 3.0.10. Since then, we have been facing a lot of these exceptions. What could be the possible cause for this exception? INFO [SharedPool-Worker-2] 2017-02-23 20:14:04,984 Message.java:611 - Unexpected exception during