cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Karunaratne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7318) Unable to truncate column family on node which has been decommissioned and re-bootstrapped
Date Mon, 16 Jun 2014 23:17:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033161#comment-14033161
] 

Kishan Karunaratne commented on CASSANDRA-7318:
-----------------------------------------------

Reproduced on 2.0 head (2.0.9-SNAPSHOT)
Output from gossipinfo:

/10.240.78.13
  generation:1402959702
  heartbeat:2212
  LOAD:62059.0
  STATUS:NORMAL,-9223372036854775808
  SCHEMA:302e036e-8cfc-3d91-b9c1-16f226e2f19b
  RACK:rack1
  SEVERITY:0.0
  HOST_ID:f60de575-4300-484f-85e0-801d8c5d7945
  NET_VERSION:7
  RPC_ADDRESS:0.0.0.0
  DC:datacenter1
  RELEASE_VERSION:2.0.8-SNAPSHOT
/10.240.169.242
  generation:1402960280
  heartbeat:456
  LOAD:97239.0
  STATUS:NORMAL,0
  SCHEMA:302e036e-8cfc-3d91-b9c1-16f226e2f19b
  RACK:rack1
  SEVERITY:0.0
  HOST_ID:93467f7f-3ae3-444d-a40a-0807a9e8eff9
  NET_VERSION:7
  RPC_ADDRESS:0.0.0.0
  DC:datacenter1

> Unable to truncate column family on node which has been decommissioned and re-bootstrapped
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7318
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7318
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Seen running cassandra 2.0.7 running on Red Hat Linux
>            Reporter: Thomas Whiteway
>            Assignee: Yuki Morishita
>            Priority: Minor
>
> After decommissioning a node, then re-bootstrapping it, it's not possible to truncate
column families until cassandra is restarted.
> Steps to reproduce:
> - Start with a two node deployment (nodes A and B)
> - Run nodetool decommission on node B
> - Stop cassandra on node B
> - Delete the contents of the cassandra data and commitlog directories
> - Start cassandra on node B with node A as the seed
> - Run cqlsh on node B and try to truncate a column family
> - cqlsh displays: "Unable to complete request: one or more nodes were unavailable."
> According to the logs node B seems to think that itself is down.  The follow logs appear
when the server is started and there are no further logs to indicate the B is now UP (A=10.225.45.150,
B=10.225.45.151):
>  INFO [main] 2014-05-29 10:40:11,090 MessagingService.java (line 461) Starting Messaging
Service on port 7000
>  INFO [HANDSHAKE-/10.225.45.150] 2014-05-29 10:40:11,106 OutboundTcpConnection.java (line
386) Handshaking version with /10.225.45.150
>  INFO [GossipStage:1] 2014-05-29 10:40:11,182 Gossiper.java (line 903) Node /10.225.45.150
is now part of the cluster
>  INFO [GossipStage:1] 2014-05-29 10:40:11,185 Gossiper.java (line 883) InetAddress /10.225.45.151
is now DOWN
>  INFO [RequestResponseStage:1] 2014-05-29 10:40:11,215 Gossiper.java (line 869) InetAddress
/10.225.45.150 is now UP
> This problem isn't hit if cassandra is restarted on node A while node B is stopped. 
The problem goes away if node B is restarted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message