src/community.md

layout: page permalink: /community/ title: Community is_homepage: false is_sphinx_doc: false

Community

Getting and keeping in touch

Mailing lists

Discussion and questions on Cassandra's usage and development happens mainly on the following mailing lists:

Users: General mailing list for user questions and discussions. This is also where new releases are announced (subscribe | unsubscribe | Archives).
Developers: Questions and discussions related to Cassandra development (subscribe | unsubscribe | Archives).
Commits: Notification on commits done to the source repository and on JIRA updates. This is a fairly noisy mailing list mostly useful for Cassandra developers and those who would like to keep close tabs on Cassandra's development (subscribe | unsubscribe | Archives).

Slack

We have recently moved to the ASF Slack organization for all chat. Please sign up for an account to participate.

#cassandra - for user questions and general discussions.
#cassandra-dev - strictly for questions or discussions related to Cassandra development.

IRC

Note: Most discussion has been moved to the above Slack channels.

#cassandra-dev - strictly for questions or discussions related to Cassandra development.
#cassandra-builds - results of automated test builds.

Communication on the #cassandra-dev channel is publicly archived.

Stack Overflow

You can also check the Q&A about using Cassandra on Stack Overflow.

Books and Publications

Cassandra: The Definitive Guide, 3rd Edition, by Jeff Carpenter and Eben Hewitt. Updated for Cassandra 4.0
Mastering Apache Cassandra, 2nd Edition, by Nishant Neeraj
Learning Apache Cassandra - Manage Fault Tolerant and Scalable Real-Time Data, by Mat Brown
Cassandra: a decentralized structured storage system, by Avinash Lakshman and Prashant Malik

Reporting bugs

If you encounter a problem with Cassandra, the first places to ask for help are the user mailing list and the #cassandra IRC channel.

If, after having asked for help, you suspect that you have found a bug in Cassandra, you should report it by opening a ticket through the Apache Cassandra JIRA. Please provide as much details as you can on your problem, and don't forget to indicate which version of Cassandra you are running and on which environment.