You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nir Zilka (JIRA)" <ji...@apache.org> on 2016/11/12 18:55:58 UTC
[jira] [Updated] (CASSANDRA-12905) streaming issues with 3.9
(repair)
[ https://issues.apache.org/jira/browse/CASSANDRA-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nir Zilka updated CASSANDRA-12905:
----------------------------------
Description:
Hello,
I performed two upgrades to the current cluster (currently 15 nodes),
first it was 2.2.5.1 and repair worked flawlessly,
second upgrade was to 3.0.9 (with upgradesstables) and also repair worked well,
then i upgraded 2 weeks ago to 3.9 - and the repair problems started.
there are several errors types from the system.log (different nodes) :
- Sync failed between /xxx.xxx.xxx.xxx and /xxx.xxx.xxx.xxx
- Streaming error occurred on session with peer xxx.xxx.xxx.xxx Operation timed out - received only 0 responses
- Remote peer xxx.xxx.xxx.xxx failed stream session
- Session completed with the following error
org.apache.cassandra.streaming.StreamException: Stream failed
----
i use 3.9 default configuration with the cluster settings adjustments (3 seeds, GossipingPropertyFileSnitch).
streaming_socket_timeout_in_ms is the default (86400000).
i'm afraid from consistency problems while i'm not performing repair.
Any ideas?
Thanks,
Nir.
was:
Hello,
I performed two upgrades to the current cluster (currently 15 nodes),
first it was 2.2.5.1 and repair worked flawlessly,
second upgrade was to 3.0.9 (with upgradesstables) and also repair worked well,
then i upgraded 2 weeks ago to 3.9 - and the repair problems started.
there are several errors types from the system.log :
- Sync failed between /xxx.xxx.xxx.xxx and /xxx.xxx.xxx.xxx
- Streaming error occurred on session with peer xxx.xxx.xxx.xxx Operation timed out - received only 0 responses
- Remote peer xxx.xxx.xxx.xxx failed stream session
- Session completed with the following error
org.apache.cassandra.streaming.StreamException: Stream failed
----
i use 3.9 default configuration with the cluster settings adjustments (3 seeds, GossipingPropertyFileSnitch).
streaming_socket_timeout_in_ms is the default (86400000).
i'm afraid from consistency problems while i'm not performing repair.
Any ideas?
Thanks,
Nir.
> streaming issues with 3.9 (repair)
> ----------------------------------
>
> Key: CASSANDRA-12905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12905
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: centos 6.7 x86_64
> Reporter: Nir Zilka
> Fix For: 3.9
>
>
> Hello,
> I performed two upgrades to the current cluster (currently 15 nodes),
> first it was 2.2.5.1 and repair worked flawlessly,
> second upgrade was to 3.0.9 (with upgradesstables) and also repair worked well,
> then i upgraded 2 weeks ago to 3.9 - and the repair problems started.
> there are several errors types from the system.log (different nodes) :
> - Sync failed between /xxx.xxx.xxx.xxx and /xxx.xxx.xxx.xxx
> - Streaming error occurred on session with peer xxx.xxx.xxx.xxx Operation timed out - received only 0 responses
> - Remote peer xxx.xxx.xxx.xxx failed stream session
> - Session completed with the following error
> org.apache.cassandra.streaming.StreamException: Stream failed
> ----
> i use 3.9 default configuration with the cluster settings adjustments (3 seeds, GossipingPropertyFileSnitch).
> streaming_socket_timeout_in_ms is the default (86400000).
> i'm afraid from consistency problems while i'm not performing repair.
> Any ideas?
> Thanks,
> Nir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)