[ https://issues.apache.org/jira/browse/CASSANDRA-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-6488: -------------------------------------- Attachment: 6488-v2.txt v2 to move the caching logic inside cloneOnlyTokenMap > Batchlog writes consume unnecessarily large amounts of CPU on vnodes clusters > ----------------------------------------------------------------------------- > > Key: CASSANDRA-6488 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6488 > Project: Cassandra > Issue Type: Bug > Reporter: Rick Branson > Assignee: Aleksey Yeschenko > Attachments: 6488-rbranson-patch.txt, 6488-v2.txt, graph (21).png > > > The cloneTokenOnlyMap call in StorageProxy.getBatchlogEndpoints causes > enormous amounts of CPU to be consumed on clusters with many vnodes. I > created a patch to cache this data as a workaround and deployed it to a > production cluster with 15,000 tokens. CPU consumption drop to 1/5th. This > highlights the overall issues with cloneOnlyTokenMap() calls on vnodes > clusters. I'm including the maybe-not-the-best-quality workaround patch to > use as a reference, but cloneOnlyTokenMap is a systemic issue and every place > it's called should probably be investigated. -- This message was sent by Atlassian JIRA (v6.1.4#6159)