[ https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194804#comment-17194804 ]
ZhaoYang commented on CASSANDRA-16123: -------------------------------------- The jstack showed HintsDispatcher is running and it may generate writes with MV. {\{"Keyspace.applyInternal,line 545"}} will retry until writes timeout, 2s. So I don't think it will consume CPU indefinitely. > Use materialized view, CPU usage over 100% > ------------------------------------------ > > Key: CASSANDRA-16123 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16123 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Core > Reporter: chenbing > Priority: Normal > Attachments: image-2020-09-12-16-50-41-341.png, > image-2020-09-12-16-52-46-581.png, image-2020-09-12-16-55-49-813.png, > jstack_25640.txt > > > env info: > os: CentOS Linux release 7.4.1708 > cassandra: apache-cassandra-3.11.8 > jdk:1.8.0_261 > > I used materialized view,but the cpu use over 100 when not cql client > request, > My analysis process is as follows: > 1. top > find pid is:25640 > 2. top -pH 25640 > !image-2020-09-12-16-52-46-581.png! > 3. printf "%x\n" 26065 > convert threadid 26065 ,hex value is :65d1 > 4.jstack -l 26065 > jstack_25640.txt > find 65d1 ind jstask_25640.txt > !image-2020-09-12-16-55-49-813.png! > > 5.find in source code on org.apache.cassandra.db.Keyspace.applyInternal,line > 545 > I guess used cpu over 100% caused by a loop call Keyspace.applyInternal. > > Everybody have any suggessted? > The jstack_25640.txt file on Attachment. > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org