-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse order query causes performance bottleneck of cassandra cluster #240
Comments
I am not sure why the Cassandra plugin needs this at recovering. but we could optimize the execution plan by cutting the result set. i.e., |
Can we just use max?
This stackoverflow answer says that Cassandra supports it. |
@ZhiXingHeYiApple as a workaround until we can fix the code, is it possible for you to add an index to |
It will ignore the null value, but still sorting a large set. https://stackoverflow.com/questions/34246403/performance-of-max-vs-order-by-desc-limit-1 |
CassandraJournalStatements.scala
journal messages table of cassandra below:
When business application actors are restored from cassandra disks, there will be a large number of slow queries. Is there any way to eliminate this reverse order query? Thank you!
The text was updated successfully, but these errors were encountered: