This has been reported by other users with very large clusters and vnodes.
https://issues.apache.org/jira/browse/CASSANDRA-9258 Both this thread and 9258 call this a regression, but don’t mention which version you’re upgrading from (or which of your two versions below see the high CPU). This is a compelling reason to use fewer vnodes per instance if you expect to have a very large cluster. -- Jeff Jirsa > On Sep 22, 2017, at 4:44 AM, Durity, Sean R <sean_r_dur...@homedepot.com> > wrote: > > I don’t know a specific issue with these versions, but in general you do not > want to do ANY streaming operations (bootstrap or repair) between Cassandra > versions. I would get all the nodes (in all DCs) to the same version and then > try the bootstrap. > > > Sean Durity > > From: Peng Xiao [mailto:2535...@qq.com] > Sent: Friday, September 22, 2017 3:56 AM > To: user <user@cassandra.apache.org> > Subject: Pending-range-calculator during bootstrapping > > Dear All, > > when we are bootstrapping a new node,we are experiencing high cpu load which > affect the rt ,and we noticed that it's mainly costing on > Pending-range-calculator ,this did not happen before. > We are using C* 2.1.13 in one DC,2.1.18 in another DC. > Could anyone please advise on this? > > Thanks, > Peng Xiao > > > The information in this Internet Email is confidential and may be legally > privileged. It is intended solely for the addressee. Access to this Email by > anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be taken > in reliance on it, is prohibited and may be unlawful. When addressed to our > clients any opinions or advice contained in this Email are subject to the > terms and conditions expressed in any applicable governing The Home Depot > terms of business or client engagement letter. The Home Depot disclaims all > responsibility and liability for the accuracy and content of this attachment > and for any damages or losses arising from any inaccuracies, errors, viruses, > e.g., worms, trojan horses, etc., or other items of a destructive nature, > which may be contained in this attachment and shall not be liable for direct, > indirect, consequential or special damages in connection with this e-mail > message or its attachment.
