You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by "Gopal, Dhruva" <Dh...@Aspect.com> on 2017/08/29 23:20:05 UTC

nodetool gossipinfo question

Hi –
  I have a question on the significance a particular attribute in the output result for ‘nodetool gossipinfo’: RELEASE_VERSION. We have a node that is periodically crashing with nothing really of significance in the logs and we’re trying to ascertain if it’s an OS issue or something to do with Cassandra. The output of ‘nodetool gossipinfo’ for this node was different from all other nodes in the cluster – we’re using 2.1.11 in this cluster and it was set to RELEASE_VERSION:6:2.1.11. In a subsequent run, after another crash, while attempting a repair it was set to RELEASE_VERSION:7:2.1.11. All other nodes output RELEASE_VERSION:4:2.1.11. What is the significance of that first digit (the rest appears to be the version of Cassandra running on each node).


Regards,
Dhruva

This email (including any attachments) is proprietary to Aspect Software, Inc. and may contain information that is confidential. If you have received this message in error, please do not read, copy or forward this message. Please notify the sender immediately, delete it from your system and destroy any copies. You may not further disclose or distribute this email or its attachments.

Re: nodetool gossipinfo question

Posted by Blake Eggleston <be...@apple.com>.
That's the value version. Gossip uses versioned values to work out which piece of data is the most recent. Each node has it's own highest version, so I don't think it's unusual for that to be different for different nodes. When you say the node crashes, do you mean the process dies?

On August 29, 2017 at 4:20:30 PM, Gopal, Dhruva (dhruva.gopal@aspect.com) wrote:

Hi –

  I have a question on the significance a particular attribute in the output result for ‘nodetool gossipinfo’: RELEASE_VERSION. We have a node that is periodically crashing with nothing really of significance in the logs and we’re trying to ascertain if it’s an OS issue or something to do with Cassandra. The output of ‘nodetool gossipinfo’ for this node was different from all other nodes in the cluster – we’re using 2.1.11 in this cluster and it was set to RELEASE_VERSION:6:2.1.11. In a subsequent run, after another crash, while attempting a repair it was set to RELEASE_VERSION:7:2.1.11. All other nodes output RELEASE_VERSION:4:2.1.11. What is the significance of that first digit (the rest appears to be the version of Cassandra running on each node).

 

 

Regards,

Dhruva

 

This email (including any attachments) is proprietary to Aspect Software, Inc. and may contain information that is confidential. If you have received this message in error, please do not read, copy or forward this message. Please notify the sender immediately, delete it from your system and destroy any copies. You may not further disclose or distribute this email or its attachments.