[ 
https://issues.apache.org/jira/browse/CASSANDRA-15040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SungJae Yun updated CASSANDRA-15040:
------------------------------------
    Attachment: cassandra_jira_qna.log

> Join / Decommission Cascadra nodes streaming failed
> ---------------------------------------------------
>
>                 Key: CASSANDRA-15040
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15040
>             Project: Cassandra
>          Issue Type: Test
>          Components: Cluster/Gossip, Consistency/Bootstrap and Decommission
>         Environment: Ubuntu 16.04.3 LTS
> AWS EC2 
>            Reporter: SungJae Yun
>            Priority: Major
>             Fix For: 3.10
>
>         Attachments: cassandra_jira_qna.log, cassandra_jira_qna.sql
>
>
> I am having some problem with Cassandra 3.10 that when I try to 
> join/decommission node, it cannot join/decommission the cluster with the 
> "stream failed" exception, then it stops running. Util that time, node stays 
> in JOINING state.
>  
> It succeeds in the following cases.
>  
> case 1. drop index > node join/decommission SUCCEED > create index > node 
> join/decommission FAIL
> case 2. table data backup (copy to command) > truncate table > data recovery 
> (copy from command) > node join/decommission SUCCEED > New DATA insert from 
> service > node join/decommission FAIL
> case 3.table data backup (copy to command) > drop table > create table >data 
> recovery (copy from command) >node join/decommission SUCCEED > New DATA 
> insert from service > node join/decommission FAIL
>  
> Unfortunately, I do not know about new insert queries from the service.
>  
> Q1. Can I check queries from the service session? 
>  
> Q2. Do you have any idea why stream fails in cassandra?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to