cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13351) CASSANDRA-11345 why not fix on 2.1.x?
Date Mon, 20 Mar 2017 06:01:41 GMT

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

Yuki Morishita commented on CASSANDRA-13351:
--------------------------------------------

2.1 is only maintained for critical fixes only. It even states so in download page of Apache
Cassandra. (But apparently it's not it seems...)
You can work around by setting {{streaming_socket_timeout_in_ms}} high.


> CASSANDRA-11345 why not fix on 2.1.x?
> -------------------------------------
>
>                 Key: CASSANDRA-13351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13351
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>         Environment: cassandra 2.1.15
> jdk 1.8
>            Reporter: zhaoyan
>
> I found same problem on cassandra 2.1.15
> the problem was reproduced In 2.1.13
> I don't know why not fix it on 2.1.x ?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message