[CASSANDRA-5494] Inconsistent view of nodes in CommandDroppedTasks

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Invalid
• Severity: Normal
• Assignee: Unassigned
• Reporter: Ondřej Černoš
• Created: 18/Apr/13 12:45
• Updated: 16/Apr/19 09:32
• Resolved: 18/Apr/13 14:07

Description

Please see related CASSANDRA-5493 for context.

On our testing platform we saw output from get CommandDroppedTasks in jmxterm, which was different on different DCs. In DC1, we saw 3x public IPs of remote DC nodes, 2x public IPs of local DC nodes, 2x private IPs of local DC nodes. We don't see stats for the very node the command is run on.

On the other hand, on the remote DC, we see stats for the node the command is run on, stored under the node's public IP.

This is at least confusing, maybe even a bug.

After restarting all the nodes in the cluster (both datacenters) the situation settled - now we don't see stats for the node the command is run on. This is however inconsistent with the situation on production (see CASSANDRA-5493).

Issue Links

• relates to: CASSANDRA-5493 Confusing output of CommandDroppedTasks