I ran nodetool tpstats and see MemtablePostFlush is pending
MemtablePostFlush 1 647 8803 0 0
and I re-ran the same command after a while and still got the same. I also re-start DSE and issue still existed. please help to address it.
Thanks
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
I ran nodetool tpstats and see MemtablePostFlush is pending
MemtablePostFlush 1 647 8803 0 0
and I re-ran the same command after a while and still got the same. I also re-start DSE and issue still existed. please help to address it.
Thanks
@xiaowan2_157616 The MemtablePostFlush
task cleans up the commit log after the memtable data is flushed to disk. The high number of pending tasks indicates that the Cassandra process is not able to access the commit logs. It's highly likely that logs have the wrong file permissions.
Check the permissions of the commitlog
(and its parents). Also make sure that the log files are owned by the same OS user as the Cassandra process (cassandra
user by default) instead of root
. You will need to perform a restart after you have reset the permissions. Cheers!
2 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use