[jira] [Commented] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
[
https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Updated] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
[ https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenbing updated CASSANDRA-16123: - Labels: (was: features) > 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
[jira] [Updated] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
[ https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenbing updated CASSANDRA-16123: - Component/s: (was: Consistency/Streaming) Legacy/Core > 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 > Labels: features > 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
[jira] [Updated] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
[ https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenbing updated CASSANDRA-16123: - Labels: features (was: ) > 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: Consistency/Streaming >Reporter: chenbing >Priority: Normal > Labels: features > 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
[jira] [Updated] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
[ https://issues.apache.org/jira/browse/CASSANDRA-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenbing updated CASSANDRA-16123: - Description: 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. was: 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 code Keyspace.applyInternal Caused by a loop call Keyspace.applyInternal， Everybody have any suggessted? The jstack_25640 on Attachment. > 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: Consistency/Streaming >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
[jira] [Created] (CASSANDRA-16123) Use materialized view, CPU usage over 100%
chenbing created CASSANDRA-16123: Summary: 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: Consistency/Streaming Reporter: chenbing 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 code Keyspace.applyInternal Caused by a loop call Keyspace.applyInternal， Everybody have any suggessted? The jstack_25640 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
[jira] [Updated] (CASSANDRA-13791) unable to install apache-cassandra-3.11.0 in linux box
[ https://issues.apache.org/jira/browse/CASSANDRA-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandrasekara Reddy updated CASSANDRA-13791: Status: Open (was: Resolved) Issue exits in Windows 10 environment Cassandra Version: apache-cassandra-3.11.8 jna-4.2.2.jar [^debug.log][^system.log] > unable to install apache-cassandra-3.11.0 in linux box > --- > > Key: CASSANDRA-13791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13791 > Project: Cassandra > Issue Type: Bug > Components: Local/Config > Environment: Linux >Reporter: rajasekhar >Priority: Urgent > Fix For: 3.11.0 > > Attachments: debug.log, log_cassdb.txt, system.log > > > While installing the Cassandra in linux serverr, I am getting below error . > could you please look int it and provide suggestions. PFA atttached log for > more information. > [cassdb@alsc_dev_db bin]$ sh > /u01/Cassandra_home/apache-cassandra-3.11.0/bin/cassandra > Error: > ERROR [main] 2017-08-23 09:48:21,467 NativeLibraryLinux.java:62 - Failed to > link the C library against JNA. Native methods will be unavailable. > java.lang.UnsatisfiedLinkError: > /tmp/jna--1367560132/jna4859101025087222330.tmp: /lib64/libc.so.6: version > `GLIBC_2.14' not found (required by > /tmp/jna--1367560132/jna4859101025087222330.tmp) > at java.lang.ClassLoader$NativeLibrary.load(Native Method) > ~[na:1.8.0_71] > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1938) > ~[na:1.8.0_71] >at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1821) > ~[na:1.8.0_71] > at java.lang.Runtime.load0(Runtime.java:809) ~[na:1.8.0_71] > at java.lang.System.load(System.java:1086) ~[na:1.8.0_71] > at > com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:947) > ~[jna-4.4.0.jar:4.4.0 (b0)] > at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) > ~[jna-4.4.0.jar:4.4.0 (b0)] > at com.sun.jna.Native.(Native.java:190) ~[jna-4.4.0.jar:4.4.0 > (b0)] > at > org.apache.cassandra.utils.NativeLibraryLinux.(NativeLibraryLinux.java:53) > ~[apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:93) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:196) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) > [apache-cassandra-3.11.0.jar:3.11.0] > WARN [main] 2017-08-23 09:48:21,468 StartupChecks.java:127 - jemalloc shared > library could not be preloaded to speed up memory allocations > WARN [main] 2017-08-23 09:48:21,469 StartupChecks.java:160 - JMX is not > enabled to receive remote connections. Please see cassandra-env.sh for more > info. > ERROR [main] 2017-08-23 09:48:21,470 CassandraDaemon.java:706 - The native > library could not be initialized properly -- 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
[jira] [Updated] (CASSANDRA-13791) unable to install apache-cassandra-3.11.0 in linux box
[ https://issues.apache.org/jira/browse/CASSANDRA-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandrasekara Reddy updated CASSANDRA-13791: Attachment: system.log debug.log > unable to install apache-cassandra-3.11.0 in linux box > --- > > Key: CASSANDRA-13791 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13791 > Project: Cassandra > Issue Type: Bug > Components: Local/Config > Environment: Linux >Reporter: rajasekhar >Priority: Urgent > Fix For: 3.11.0 > > Attachments: debug.log, log_cassdb.txt, system.log > > > While installing the Cassandra in linux serverr, I am getting below error . > could you please look int it and provide suggestions. PFA atttached log for > more information. > [cassdb@alsc_dev_db bin]$ sh > /u01/Cassandra_home/apache-cassandra-3.11.0/bin/cassandra > Error: > ERROR [main] 2017-08-23 09:48:21,467 NativeLibraryLinux.java:62 - Failed to > link the C library against JNA. Native methods will be unavailable. > java.lang.UnsatisfiedLinkError: > /tmp/jna--1367560132/jna4859101025087222330.tmp: /lib64/libc.so.6: version > `GLIBC_2.14' not found (required by > /tmp/jna--1367560132/jna4859101025087222330.tmp) > at java.lang.ClassLoader$NativeLibrary.load(Native Method) > ~[na:1.8.0_71] > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1938) > ~[na:1.8.0_71] >at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1821) > ~[na:1.8.0_71] > at java.lang.Runtime.load0(Runtime.java:809) ~[na:1.8.0_71] > at java.lang.System.load(System.java:1086) ~[na:1.8.0_71] > at > com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:947) > ~[jna-4.4.0.jar:4.4.0 (b0)] > at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) > ~[jna-4.4.0.jar:4.4.0 (b0)] > at com.sun.jna.Native.(Native.java:190) ~[jna-4.4.0.jar:4.4.0 > (b0)] > at > org.apache.cassandra.utils.NativeLibraryLinux.(NativeLibraryLinux.java:53) > ~[apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.utils.NativeLibrary.(NativeLibrary.java:93) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:196) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) > [apache-cassandra-3.11.0.jar:3.11.0] > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) > [apache-cassandra-3.11.0.jar:3.11.0] > WARN [main] 2017-08-23 09:48:21,468 StartupChecks.java:127 - jemalloc shared > library could not be preloaded to speed up memory allocations > WARN [main] 2017-08-23 09:48:21,469 StartupChecks.java:160 - JMX is not > enabled to receive remote connections. Please see cassandra-env.sh for more > info. > ERROR [main] 2017-08-23 09:48:21,470 CassandraDaemon.java:706 - The native > library could not be initialized properly -- 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
