Then that's the cause for the node negotiating down to an older protocol version by design for dealing with mixed-version clusters as Sam described in his response. As Bowen stated, you must have had an old node back from when it was still a C* 2.2 cluster that you probably tried to remove/decommission but ran into issues so it's still hanging around in gossip.
You can manually delete that node to get rid of it with: cqlsh> DELETE FROM system.peers WHERE peer = '10.39.36.152'; There's a good chance that you need to delete it multiple times -- it's a race with gossip re-populating the table. Also check that it's completely gone from nodetool gossipinfo. Once you're convinced that it's no longer in gossip and in peers, you'll need to restart the node so it defaults back to v4. Good luck!
