INFO [HANDSHAKE-/10.176.249.XX] 2013-10-03 17:36:16,948 OutboundTcpConnection.java (line 399) Handshaking version with /10.176.249.XX
INFO [HANDSHAKE-/10.176.182.YY] 2013-10-03 17:36:17,280 OutboundTcpConnection.java (line 408) Cannot handshake version with /10.176.182.YY
INFO [HANDSHAKE-/10.176.182.YY] 2013-10-03 17:36:17,280 OutboundTcpConnection.java (line 399) Handshaking version with /10.176.182.YY
INFO [HANDSHAKE-/10.188.13.ZZ] 2013-10-03 17:36:17,510 OutboundTcpConnection.java (line 408) Cannot handshake version with /10.188.13.ZZ
INFO [HANDSHAKE-/10.188.13.ZZ] 2013-10-03 17:36:17,511 OutboundTcpConnection.java (line 399) Handshaking version with /10.188.13.ZZ
DEBUG [WRITE-/54.215.70.YY] 2013-10-03 18:01:50,237 OutboundTcpConnection.java (line 338) Target max version is -2147483648
; no version information yet, will retry
TRACE [HANDSHAKE-/10.177.14.XX] 2013-10-03 18:01:50,237 OutboundTcpConnection.java (line 406) Cannot handshake version with /10.177.14.XX
Another fact is that the number of completed compaction tasks decreased as the number of upgraded nodes increased. I don't know if that's related to the increased number read timeouts or just a coincidence. The timeout configuration is the default (10000ms).
Two similar issues were reported, but without satisfactory responses:
Is that an expected behavior or is there something that might be going wrong during the upgrade? Has anyone faced similar issues?
Any help would be very much appreciated.