You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Don Branson (JIRA)" <ji...@apache.org> on 2016/05/15 18:40:12 UTC

[jira] [Commented] (CASSANDRA-11806) sstableloader fails with "Remote peer failed stream session" on small table

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

Don Branson commented on CASSANDRA-11806:
-----------------------------------------

I can see that `upgradesstables` would work where a node is upgraded as 10990 discusses, and the sstables need to be upgraded. That works because there's a running node with old tables in place. The difference here is that the tables were captured with `nodetool snapshot` and I'm trying to stream them from a workstation to a fresh 3.5 install. So, there's no local node running node. There's no node to upgrade. Are you saying there's a way to run nodetool without a node to connect to? Or (as I suspect) are you saying that it's necessary to 1) stand up the new node with the old version of cassandra, 2) load the data into that node, and 3) upgrade the node to the new version?

> sstableloader fails with "Remote peer <ipaddr> failed stream session" on small table
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11806
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11806
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Linux ny2-proda-app01 3.13.0-86-generic #130-Ubuntu SMP Mon Apr 18 18:27:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Don Branson
>             Fix For: 3.5
>
>         Attachments: roles_table.txt, roles_table_error.txt
>
>
> This error is with sstableloader loading a 2-column table with 20 rows. All other tables in the keyspace load clean. The database dump is from cassandra 2.1.9, the target is cassandra 3.5. 14 of the 20 rows load successfully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)