[
https://issues.apache.org/jira/browse/CASSANDRA-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703224#comment-15703224
]
Benjamin Roth commented on CASSANDRA-12905:
-------------------------------------------
Can someone please comment on that:
Is it possible that its "not so cool" to send mutations of CFs with views to
the regular write path during bootstrap?
All the MV sstables are also part of the bootstrapping and range movement
process, right? So why not just stream the SSTables down to files like without
MV?
Why I ask? I am currently bootstrapping a new node with a load of approx 250GB.
The bootstrap started about 12h ago and it still did not finish.
Netstat tells me that all streams have been transferred, but the node has a
load of about 90 and all the CPU is eaten by a bunch of StreamReceiverTasks
applying MV updates.
Btw.: I applied the commit I've posted some comments ago and there is no more
WTE going on any more.
I sometimes got the impression that really nobody out there seriously uses MVs.
> Retry acquire MV lock on failure instead of throwing WTE on streaming
> ---------------------------------------------------------------------
>
> 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
> Priority: Critical
> Fix For: 3.9
>
>
> Hello,
> I performed two upgrades to the current cluster (currently 15 nodes, 1 DC,
> private VLAN),
> 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)
