[
https://issues.apache.org/jira/browse/CASSANDRA-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338151#comment-15338151
]
Chris Love commented on CASSANDRA-11983:
----------------------------------------
I understand what you are saying, and I agree that removing the code is not a
fix.
The new nodes were getting stuck in a loop starting. Above 30 nodes it start to
take 10 min plus to lanch a node. That is not acceptable. What is the node
doing? I don't understand why it is taking so long.
As I mentioned in a perfect world I would disable autoboostrap, but the config
needs to be immutable.
What are the nodes doing? How can we speed up what they are doing. To me this
doesn't seem to be a good approach.
> Migration task failed to complete
> ---------------------------------
>
> Key: CASSANDRA-11983
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11983
> Project: Cassandra
> Issue Type: Bug
> Components: Lifecycle
> Environment: Docker / Kubernetes running
> Linux cassandra-21 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06)
> x86_64 GNU/Linux
> openjdk version "1.8.0_91"
> OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-1~bpo8+1-b14)
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> Cassnadra 3.5 installed from
> deb-src http://www.apache.org/dist/cassandra/debian 35x main
> Reporter: Chris Love
> Attachments: cass.log
>
>
> When nodes are boostrapping I am getting mulitple errors: "Migration task
> failed to complete", from MigrationManager.java
> The errors increase as more nodes are added to the ring, as I am creating a
> ring of 1k nodes.
> Cassandra yaml i here
> https://github.com/k8s-for-greeks/gpmr/blob/3d50ff91a139b9c4a7a26eda0fb4dcf9a008fbed/pet-race-devops/docker/cassandra-debian/files/cassandra.yaml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
