You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2016/05/06 13:53:12 UTC
[jira] [Commented] (CASSANDRA-11727) Streaming error while
Bootstraping Materialized View
[ https://issues.apache.org/jira/browse/CASSANDRA-11727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274054#comment-15274054 ]
Paulo Motta commented on CASSANDRA-11727:
-----------------------------------------
Closing this as a duplicate of CASSANDRA-11670 so we centralize discussion there. Can you double check that the source node of this streaming session (or other nodes in general) do not have a custom {{commitlog_segment_size_in_mb}} or {{max_mutation_size_in_kb}} configuration set? You may check that by grepping your system.log or cassandra.yaml for these properties. Please report back in the other ticket.
> Streaming error while Bootstraping Materialized View
> ----------------------------------------------------
>
> Key: CASSANDRA-11727
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11727
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Ubuntu 14.04
> Oracle JDK 1.8.0_11
> 16GB RAM
> Cassandra Version 3.0.5
> Reporter: Alexander Heiß
> Fix For: 3.0.5
>
>
> We have a Cluster with 4 Servers in 2 Datacenters (2 in DC A and 2 in DC B), Root servers.
> We have a Replication Factor of 2, so atm we have 100% load on all 4 Servers. Around 250GB of Data. Everything works fine. Now we want to add 2 more Servers to the Cluster, one in each Datacenter. But we always get the same Kind of error while Bootstraping:
> {quote}ERROR 13:21:34 Unknown exception caught while attempting to update MaterializedView! messages_dump.messages
> java.lang.IllegalArgumentException: Mutation of 24032623 bytes is too large for the maxiumum size of 16777216
> at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:264) ~[apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:469) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:384) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:205) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:217) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.batchlog.BatchlogManager.store(BatchlogManager.java:146) ~[apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:724) ~[apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.view.ViewManager.pushViewReplicaUpdates(ViewManager.java:149) ~[apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:487) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:384) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:205) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:217) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.db.Mutation.applyUnsafe(Mutation.java:236) [apache-cassandra-3.0.5.jar:3.0.5]
> at org.apache.cassandra.streaming.StreamReceiveTask$OnCompletionRunnable.run(StreamReceiveTask.java:169) [apache-cassandra-3.0.5.jar:3.0.5]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_11]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_11]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_11]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_11]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
> {quote}
> and
> {quote}
> WARN 13:21:34 Some data streaming failed. Use nodetool to check bootstrap state and resume. For more, see `nodetool help bootstrap`. IN_PROGRESS
> {quote}
> And if we Resume the Bootstrap it starts all over again and then it fails with the same Error Message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)