Re: Call for Presentations closing TOMORROW: Community over Code EU 2024

[Mick Semb Wever]

The CFP for the Cassandra track at the Community Over Code EU conference,
June in Bratislava, closes tomorrow (Friday) !!

We'd love to hear your Cassandra experience, operating or coding.
Submit before it's too late 拾

see you there,
Mick


On Mon, 8 Jan 2024 at 20:24, Paulo Motta  wrote:

> I wanted to remind that the call for speakers for Community Over Code EU
> 2024 (formerly Apachecon EU) will be closing this Friday 2024/01/12
> 23:59:59 GMT.
>
> If you reside in Europe/EMEA and have an interesting talk proposal about
> using, deploying or modifying Apache Cassandra please see details below to
> submit a proposal to this conference.
>
> -- Forwarded message -
> From: Ryan Skraba 
> Date: Mon, Oct 30, 2023 at 1:07 PM
> Subject: Call for Presentations now open: Community over Code EU 2024
> To:
>
>
> (Note: You are receiving this because you are subscribed to the dev@
> list for one or more projects of the Apache Software Foundation.)
>
> It's back *and* it's new!
>
> We're excited to announce that the first edition of Community over
> Code Europe (formerly known as ApacheCon EU) which will be held at the
> Radisson Blu Carlton Hotel in Bratislava, Slovakia from June 03-05,
> 2024! This eagerly anticipated event will be our first live EU
> conference since 2019.
>
> The Call for Presentations (CFP) for Community Over Code EU 2024 is
> now open at https://eu.communityovercode.org/blog/cfp-open/
> 
> ,
> and will close 2024/01/12 23:59:59 GMT.
>
> We welcome submissions on any topic related to the Apache Software
> Foundation, Apache projects, or the communities around those projects.
> We are specifically looking for presentations in the following
> categories:
>
> * API & Microservices
> * Big Data Compute
> * Big Data Storage
> * Cassandra
> * CloudStack
> * Community
> * Data Engineering
> * Fintech
> * Groovy
> * Incubator
> * IoT
> * Performance Engineering
> * Search
> * Tomcat, Httpd and other servers
>
> Additionally, we are thrilled to introduce a new feature this year: a
> poster session. This addition will provide an excellent platform for
> showcasing high-level projects and incubator initiatives in a visually
> engaging manner. We believe this will foster lively discussions and
> facilitate networking opportunities among participants.
>
> All my best, and thanks so much for your participation,
>
> Ryan Skraba (on behalf of the program committee)
>
> [Countdown]:
> https://www.timeanddate.com/countdown/to?iso=20240112T2359=1440
> 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

[RELEASE] Apache Cassandra Java Driver 4.18.0 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Cassandra Java
Driver version 4.18.0

The Source release and Binary convenience artifacts are available here:
https://dist.apache.org/repos/dist/release/cassandra/cassandra-java-driver/4.18.0/

The Maven artifacts can be found at:
https://repository.apache.org/content/groups/public/org/apache/cassandra/
These will be mirrored to other repositories.

Note: this is the first release post-donation of the Java Driver.  The
maven coordinates have changed from com.datastax.oss to
org.apache.cassandra, while all package names remain the same.  Migration
of docs and download links on the website are still in progress.


Enjoy!

[RELEASE] Apache Cassandra 5.0-beta1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-beta1.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a beta release[1] on the 5.0 series. As always, please pay
attention to the release notes[2] and let us know[3] if you were to
encounter any problem.

Please note what our definition of a beta release means, further info at
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

For more information on what's in 5.0:
https://cassandra.apache.org/_/Apache-Cassandra-5.0-Moving-Toward-an-AI-Driven-Future.html


Enjoy!

[1]: CHANGES.txt
https://github.com/apache/cassandra/blob/cassandra-5.0-beta1/CHANGES.txt
[2]: NEWS.txt
https://github.com/apache/cassandra/blob/cassandra-5.0-beta1/NEWS.txt
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Cassandra Summit: Engage those networks!

[Mick Semb Wever]

Looking forward to seeing you all!   Cassandra 5* has so many game changing
features in it, I'm super excited.



On Thu, 30 Nov 2023 at 07:55, Bhagdev, Meet  wrote:

> I’m going and hope to see you there 
>
>
>
> Cheers,
>
> Meet
>
> *From: *Paulo Motta 
> *Reply-To: *"user@cassandra.apache.org" 
> *Date: *Wednesday, November 29, 2023 at 7:12 PM
> *To: *"user@cassandra.apache.org" 
> *Subject: *RE: [EXTERNAL] Cassandra Summit: Engage those networks!
>
>
>
> *CAUTION*: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> This Cassandra Summit is going to be epic!
>
> Looking forward to meet the Cassandra community in two weeks! 落
>
>
>
> On Wed, 29 Nov 2023 at 18:26 Patrick McFadin  wrote:
>
> Hi everyone,
>
>
>
> We are a couple of weeks away from Cassandra Summit. People get busy and
> forget to register or miss that there is even a summit happening. Let's
> make sure everyone who wants to go gets a chance!
>
>
>
>  - If you are going, get on the social media of your choice and let
> everyone know you'll be there. Use the hashtag #cassandrasmunnit
>
>  - If you aren't going, you can still remind other folks that it's
> happening and the talks you think they should check out.
>
>
>
> Either way, here is the basic info to include in your post:
>
>
>
> Schedule:
> https://events.linuxfoundation.org/cassandra-summit/program/schedule/
> 
>
> Register:
> https://events.linuxfoundation.org/cassandra-summit/register/#register-now
> 
>
> Discount code: 23CS20
>
>
>
> One more thing! If you are going and reading this, reply to this email
> with a "Going!" or "See you there!" I would love to see who will be there
> in two weeks.
>
>
>
> Patrick
>
>

[RELEASE] Apache Cassandra 5.0-alpha2 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of
 Apache Cassandra version 5.0-alpha2.

This release contains Vector Similarity Search (CEP-30).

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is an alpha preview release[1] on the 5.0 series. As
always, please pay attention to the release notes[2] and let us
know[3] if you were to encounter any problem.

Please also note what our definition of an alpha release means,
further info at
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

DISCLAIMER, this alpha release does not contain the features:
Transactional Cluster Metadata (CEP-21) and Accord Transactions
(CEP-15).  These features are under discussion to be pushed to a
5.1-alpha1 release, with an eta still this year.

Enjoy!

[1]: CHANGES.txt
https://github.com/apache/cassandra/blob/cassandra-5.0-alpha2/CHANGES.txt
[2]: NEWS.txt 
https://github.com/apache/cassandra/blob/cassandra-5.0-alpha2/NEWS.txt
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 5.0-alpha1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of
Apache Cassandra version 5.0-alpha1.

DISCLAIMER, this alpha release does not contain the expected 5.0 features:
Vector Search (CEP-30), Transactional Cluster Metadata (CEP-21) and Accord
Transactions (CEP-15).  These features will land in a later alpha release.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are found here:

 https://downloads.apache.org/cassandra/5.0-alpha1/

 https://debian.cassandra.apache.org/pool/main/c/cassandra/
 https://redhat.cassandra.apache.org/50x/


This version is an alpha preview release[1] on the 5.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you were
to encounter any problem.

Please also note what our definition of an alpha release means, further
info at
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/50x/ .

Enjoy!

[1]: CHANGES.txt
https://github.com/apache/cassandra/blob/cassandra-5.0-alpha1/CHANGES.txt
[2]: NEWS.txt
https://github.com/apache/cassandra/blob/cassandra-5.0-alpha1/NEWS.txt
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.1.2 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1.2.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.1 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/41x/ .

Enjoy!

[1]: CHANGES.txt
https://github.com/apache/cassandra/blob/cassandra-4.1.2/CHANGES.txt
[2]: NEWS.txt
https://github.com/apache/cassandra/blob/cassandra-4.1.2/NEWS.txt
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0.10 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.10.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/40x/ .

Enjoy!

[1]: CHANGES.txt
https://github.com/apache/cassandra/blob/cassandra-4.0.10/CHANGES.txt
[2]: NEWS.txt
https://github.com/apache/cassandra/blob/cassandra-4.0.10/NEWS.txt
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: JIRA account creation request

[Mick Semb Wever]

> HI Mick,
>
> Could you pls. help with JIRA account for me as well ?
>




Done Srinivas. You should have received an email.

Welcome to the Cassandra community.

Re: JIRA account creation request

[Mick Semb Wever]

> I would like to get my JIRA account created as I would like to contribute.
> Here are my details
>
> email address : manishkhandelwa...@gmail.com
>


Your jira account has been created. You should have received an email.

regards,
Mick

Re: Upgrading Cassandra 3.11.14 → 4.1

[Mick Semb Wever]

On Mon, 16 Jan 2023 at 14:38, Lapo Luchini  wrote:

> is upgrading Cassandra 3.11.14 → 4.1 supported,
>


3.11.14 → 4.1 is supported.

It is recommended to go to the last patch version (i.e. 3.11.14) before the
major upgrade.
Make sure to ensure all sstables are upgraded to the current format before
performing the upgrade.

Re: [DISCUSS] Formation of Apache Cassandra Publicity & Marketing Group

[Mick Semb Wever]

The market...@cassandra.apache.org list is created.

To subscribe send an email to marketing-subscr...@cassandra.apache.org from
the email address you want to subscribe from.

If you are a committer you can alternately use Whimsy:
https://whimsy.apache.org/committers/subscribe

regards,
Mick


On Fri, 20 Jan 2023 at 00:31, Patrick McFadin  wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Hello Cassandra Community!We are at a pivotal moment for the Cassandra
> community, with the first Cassandra Summit in 7 years coming up on March
> 13th, and a major release coming later this year with Cassandra 5.0. It is
> important that we come together to set the publicity strategy and direction
> for these important moments, and that we work together to define how
> Cassandra shows up across the technology industry.To achieve this, we are
> proposing the formation of a Publicity & Marketing Working Group, and we
> are requesting your participation.What is the Publicity & Marketing Working
> Group?This is a working group open to community members who have the
> insight and skills to help define Cassandra’s public narrative and
> participate in our marketing strategy and execution. The group will meet
> once a month for an hour to discuss important marketing topics. You can
> find us on #cassandra-events. We also propose adding a mailing list,
> marketing@cassandra.a.o, to handle day-to-day marketing needs and async
> communication. Our publicity and marketing partners from Constantia - Molly
> Monroy  and Melissa Logan  -
> will work with us to build this working group. What will this group be
> responsible for?Our initial vision for this group is to accelerate how we
> do marketing & publicity for Cassandra. We will refine and advance
> Cassandra’s public perception of the tech industry, to show how Cassandra
> has grown, innovated, and revitalized itself as a community. We will do
> this through: - Participating in marketing strategy for major moments (in
> particular, C* Summit in March and Cassandra 5.0 release later this year)-
> Expanding our local meetup and events presence- Sourcing end-user case
> studies for marketing and PR collateral- Making sure the Cassandra
> community shows up at third-party events- Contributing content - from blogs
> to documentation - to ensure we have a robust stream of content for our end
> usersOur first two orders of business will be: 1. Jointly determine
> operating model and governance, and get input and alignment on the above
> goals/responsibilities. 2. Discuss marketing for Cassandra Summit,
> primarily defining the news we will share at the event from the project
> directly and from our sponsors. This is coming up quickly and we will need
> community assistance to achieve our publicity goals. As this is a
> community-driven group, please share ideas and feedback on the purpose of
> this group and what we need to achieve. When is the meeting?We are
> proposing the meetings take place on the 4th Wednesday of each month. We
> will alternate times of the day to try to accommodate. We can adjust based
> on member attendance.  - Jan, March, May, July, Sept, Nov.  - 4th Wed of
> the month,  8a PT- Feb, April, June, August, October, Dec - 4th Wed of the
> month, Wed 4p PTWe will create a centralized document to share and document
> information about the working group, including meeting minutes, monthly
> tasks, and priorities. Decisions will be discussed and finalized using the
> project mailing list. Patrick*
>

[RELEASE] Apache Cassandra 4.1.0 GA released

[Mick Semb Wever]

The Cassandra team is pleased to announce the GA release of Apache
Cassandra version 4.1.0.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is the first GA release of the 4.1 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/41x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.1.0
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.1.0
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.1-rc1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1-rc1.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are available in the following
locations:

 https://downloads.apache.org/cassandra/4.1-rc1/
 https://debian.cassandra.apache.org/
 https://redhat.cassandra.apache.org/41x/

The 4.1 releases will not be listed on our website downloads page until the
GA.

This version is our first release candidate[1] of 4.1. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/41x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.1-rc1
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.1-rc1
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0.7 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.7.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/40x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.7
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.7
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.11.14 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.14.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/311x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.14
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.14
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.0.28 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.28.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/30x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.28
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.28
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: [RELEASE] Apache Cassandra 4.1-beta1 released

[Mick Semb Wever]

Correction…


Downloads of source and binary distributions are listed in our download
> section:
>
>  http://cassandra.apache.org/download/
>


The source and binary distributions are to be found here:
https://downloads.apache.org/cassandra/4.1-beta1/

(4.1 won't appear on our downloads page until it reaches RC)

[RELEASE] Apache Cassandra 4.1-beta1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1-beta1.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is the first beta release[1] on the 4.1 series.

[WARNING] Debian and RedHat package repositories have moved! Debian
/etc/apt/sources.list.d/cassandra.sources.list and RedHat
/etc/yum.repos.d/cassandra.repo files must be updated to the new repository
URLs. For Debian it is now https://debian.cassandra.apache.org . For RedHat
it is now https://redhat.cassandra.apache.org/41x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.1-beta1
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.1-beta1
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[ANNOUNCE] Debian and RedHat package repositories are moving!

[Mick Semb Wever]

Your Debian `cassandra.sources.list` and RedHat `cassandra.repo` files must
be updated to the new repository URLs.

The Debian file is typically at
`/etc/apt/sources.list.d/cassandra.sources.list`.
The RedHat file is typically at `/etc/yum.repos.d/cassandra.repo`.

For Debian the repository is now at https://debian.cassandra.apache.org

For RedHat the repository is now at https://redhat.cassandra.apache.org/40x/


These repositories offer past versions as well, so it is easier to pin
versions and to roll back.

The existing repositories under downloads.apache.org/cassandra/ will be
removed without further notice.

Reach out if you have any questions or any problems.

[RELEASE] Apache Cassandra 4.0.6 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.6.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

[WARNING] Debian and RedHat package repositories have moved! Debian
`/etc/apt/sources.list.d/cassandra.sources.list` and RedHat
`/etc/yum.repos.d/cassandra.repo` files must be updated to the new
repository URLs. For Debian it is now https://debian.cassandra.apache.org .
For RedHat it is now https://redhat.cassandra.apache.org/40x/ .

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.6
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.6
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0.5 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.5.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

IMPORTANT: this artifact contains CASSANDRA-15511, which will significantly
reduce allocations and improve the write throughput, particularly on
collections and contended partitions.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.5
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.5
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: [RELEASE] Apache Cassandra 4.1-alpha1 released

[Mick Semb Wever]

>
> Downloads of source and binary distributions are listed in our download
> section:
>
>  http://cassandra.apache.org/download/
>
> This version is the first alpha release[1] on the 4.1 series. As always,
> please pay attention to the release notes[2] and Let us know[3] if you were
> to encounter any problem.
>
> Please note that APIs may change and not all tests in CI are fixed/stable
> during our alpha releases. For more information on our release lifecycle
> and quality requirements please read
> https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle
>


FYI, until we start advertising 4.1 releases on the website, you can found
this release here: https://downloads.apache.org/cassandra/4.1-alpha1/

[RELEASE] Apache Cassandra 4.1-alpha1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1-alpha1.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is the first alpha release[1] on the 4.1 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you were
to encounter any problem.

Please note that APIs may change and not all tests in CI are fixed/stable
during our alpha releases. For more information on our release lifecycle
and quality requirements please read
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.1-alpha1
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.1-alpha1
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Last week to submit a talk to ApacheCon New Orleans and the Cassandra track

[Mick Semb Wever]

ApacheCon North America will be held October 3-6, at the Sheraton
Hotel in New Orleans.

The CFP closes this weekend!
 https://www.apachecon.com/acna2022/cfp.html

It will be fantastic to catch up with as many of you as possible. Even
better will be the talks you share with us, but you gotta submit this
week (or weekend) if you haven't already!

warm regards,
Apache Cassandra PMC


p.s. when submitting your talk, please remember to choose from the
drop-down Category "Cassandra".

[RELEASE] Apache Cassandra 4.0.4 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.4.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.4
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.4
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.11.13 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.13.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.13
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.13
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.0.27 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.27.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.27
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.27
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Applications for Travel Assistance to ApacheCon NA 2022 now open

[Mick Semb Wever]

(On behalf of the TAC)

The ASF Travel Assistance Committee (TAC) is pleased to announce that travel
assistance applications for ApacheCon NA 2022 are now open!

We will be supporting ApacheCon North America in New Orleans, Louisiana,
on October 3rd through 6th, 2022.

TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons. This year, We are supporting
both committers and non-committers involved with projects at the
Apache Software Foundation, or open source projects in general.

For more info on this year's applications and qualifying criteria, please
visit the TAC website at http://www.apache.org/travel/
Applications opened today and will close on the 1st of July 2022.

Important: Applicants have until the closing date above to submit their
applications (which should contain as much supporting material as required
to efficiently and accurately process their request), this will enable TAC
to announce successful awards shortly afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.

Cassandra track Call for Papers. ApacheCon NA October 3-6, 2022

[Mick Semb Wever]

We are excited to announce that the upcoming ApacheCon North America will
have a two day Cassandra track.

ApacheCon North America will be held October 3-6, at the Sheraton Hotel in
New Orleans.

The CFP is now open, and will be until May 23rd.

We are interested in all talks with anything related to developing, using,
or deploying Apache Cassandra.  You will be surprised how useful your open
source stories and experiences are to others and to our dev community.  It
might be how you solved a specific problem or just a general picture into
how your organization uses Apache Cassandra. And of course, upgrading and
running on 4.0 is a particularly hot topic we won't be able to get enough
of.  This will be a fantastic opportunity to network with peers, ask
questions, get answers, etc.

When submitting your talk, please remember to choose from the drop-down
Category "Cassandra".

For more information please read our blog post:
https://cassandra.apache.org/_/blog/ApacheCon-NA-2022-Call-for-Papers-Open.html


To go directly to submit your paper, go to
https://www.apachecon.com/acna2022/cfp.html

Any questions, just reach out…

[RELEASE] Apache Cassandra 4.0.3 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.3.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.3
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.3
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0.2 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.2.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.11.12 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.12.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.12
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.12

[RELEASE] Apache Cassandra 3.0.26 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.26.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.26
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.26
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: 4.1 Release Date

[Mick Semb Wever]

>
> Apache Cassandra 3.0
> Released on 2021-02-01, and supported until 4.1 release
> (April 2022).
>


Would the wording "… and supported until 4.1.0 release (May-June 2022)." be
enough?
(it would be nice to keep the text brief on this page)

If you would like to…
this is the file to create a PR off
https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/download.adoc

[RELEASE] Apache Cassandra 4.0-rc2 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-rc2.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:
 http://cassandra.apache.org/download/

This version is a release candidate[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and let us know[3] if you were to
encounter any problem.

Please note, the bintray location is now replaced with the ASF's JFrog
Artifactory location: https://apache.jfrog.io/artifactory/cassandra/

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-rc2
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-rc2
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0-rc1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-rc1.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a release candidate[1] on the 4.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Debian users shall note, as the docs are not yet updated, the bintray
location is now replaced with the ASF's JFrog Artifactory location:
 https://apache.jfrog.io/artifactory/cassandra/

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-rc1
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-rc1
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0-beta4 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-beta4.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a beta release[1] on the 4.0 series. As always, please pay
attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-beta4
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-beta4
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Enable Ttracing

[Mick Semb Wever]

> I just took a cursory look at the presentation and Zipkin.io. Would using
> Zipkin degrade performance? Would it be considerable?
>


In comparison, no.
>
>
Traces (spans) are immediately off-threaded into a Kafka Zipkin transport,
and then the Zipkin server has its own Cassandra cluster. This offloads the
tracing implementation, through the instrumentation itself always has a
small measurable impact. But nothing compared to the 10-20x write
amplification of C*'s default tracing implementation.

Re: Enable Ttracing

[Mick Semb Wever]

> I have a feeling that this tool will give me hell. 
> I'll just have to wait till they implement it and monitor the clusters,
> but at least I know what to expect.
>


The tracing implementation is pluggable in 3.11.

For example you can push traces into Zipkin (and a separate C* cluster)
using
 https://github.com/thelastpickle/cassandra-zipkin-tracing

Full sampling is possible this way.

[RELEASE] Apache Cassandra 4.0-beta3 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-beta3.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-beta3
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-beta3
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.0.23 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.23.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.23
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.23
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.11.9 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.9.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.9
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.9
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 2.2.19 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.19.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.19
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.19
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0-beta2 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-beta2.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-beta2
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-beta2
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.0.22 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.22.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.22
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.22
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.11.8 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.8.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.8
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.8
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 2.2.18 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.18.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.18
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.18
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 2.1.22 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.22.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.1.22
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.1.22
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.0.21 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.21.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:
 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Please note: bintray.com is, at time of writing, suffering an outage,
so deb and rpm packages may not be immediately available. Ref:
https://status.bintray.com

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.21
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.21
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.11.7 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.7.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:
 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.7
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.7
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 2.2.17 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.17.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:
 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always, please
pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.17
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.17
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: [RELEASE] Apache Cassandra 4.0-beta1 released

[Mick Semb Wever]

> This version is a beta release[1] on the 4.0 series. As always, please
> pay attention to the release notes[2] and let us know[3] if you were
> to encounter any problem.



A quick followup note to both user and dev groups.

Our Beta release guidelines¹ states that there will be no further API
changes leading up to 4.0 GA.
But we do currently have in place three planned exceptions to this, found in
the following tickets:

- CASSANDRA-15299 –  "CASSANDRA-13304 follow-up: improve checksumming and
compression in protocol v5-beta"
- CASSANDRA-15234 – Standardise config and JVM parameters
- CASSANDRA-13701 – Lower default num_tokens


The API changes to these are minimal, and part of the reason these were
allowed to slip into the beta phase.
For example…
* CASSANDRA-15299 only affects those that are using the not yet stabilised
v5 native protocol.
* CASSANDRA-15234 will introduce cleaner, easier to use, cassandra.yaml
settings, but all existing yaml setting names will still work.
* CASSANDRA-13701 will change the default num_tokens setting to 16 (from
256), a change that will only impact provisioning of new clusters (because
existing clusters must configure any new nodes to use the existing
num_tokens value).

All three tickets have fixVersion still set to `4.0-alpha` because of this
situation.


References:
 [1] https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

[RELEASE] Apache Cassandra 4.0-beta1 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-beta1.

Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a beta release[1] on the 4.0 series. As always, please
pay attention to the release notes[2] and let us know[3] if you were
to encounter any problem.

Enjoy!
 And check out our blog post on Cassandra 4.0 beta1
https://cassandra.apache.org/blog/2020/07/20/apache-cassandra-4-0-beta1.html


[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-beta1
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-beta1
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 4.0-alpha4 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-alpha4.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:
 http://cassandra.apache.org/download/


Downloads of source and binary distributions:
http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha4/apache-cassandra-4.0-alpha4-bin.tar.gz
http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha4/apache-cassandra-4.0-alpha4-src.tar.gz

Debian and Redhat configurations.

  sources.list:
  deb http://www.apache.org/dist/cassandra/debian 40x main

  yum config:
  baseurl=https://www.apache.org/dist/cassandra/redhat/40x/

See http://cassandra.apache.org/download/ for full install instructions.

This is an ALPHA version! It is not intended for production use, however
the project would appreciate your testing and feedback to make the final
release better. As always, please pay attention to the release notes[2] and
let us know[3] if you encounter any problems.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-alpha4
[2]: NEWS.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-alpha4
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 4.0-alpha3 released

[Mick Semb Wever]

The Cassandra team is pleased to announce the release of Apache Cassandra 
version 4.0-alpha3.

Apache Cassandra is a fully distributed database. It is the right choice when 
you need scalability and high availability without compromising performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download section:
 http://cassandra.apache.org/download/


Downloads of source and binary distributions:
http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha3/apache-cassandra-4.0-alpha3-bin.tar.gz
http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha3/apache-cassandra-4.0-alpha3-src.tar.gz

Debian and Redhat configurations.

  sources.list:
  deb http://www.apache.org/dist/cassandra/debian 40x main

  yum config:
  baseurl=https://www.apache.org/dist/cassandra/redhat/40x/

See http://cassandra.apache.org/download/ for full install instructions.

This is an ALPHA version! It is not intended for production use, however
the project would appreciate your testing and feedback to make the final
release better. As always, please pay attention to the release notes[2]
and let us know[3] if you encounter any problems.

Enjoy!

[1]: CHANGES.txt 
?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-alpha3
[2]: NEWS.txt 
?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-alpha3
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

JOB | The Last Pickle (Consultant) in USA

[Mick Semb Wever]

The Last Pickle is hiring in the US:  
https://thelastpickle.com/blog/2019/10/24/tlp-is-hiring-another-consultant.html

If you enjoy Cassandra like we do, and are keen to join our team, reach out 
(see details in link above).

regards,
Mick

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)

[Mick Semb Wever]

Ninad,

> Here's a bit more information:
>
> -Few rows in this column family can grow quite wide (> 100K columns)
>
> -But we keep seeing this behavior most frequently with rows with just 1 or 
> two columns . The typical behavior is: Machine A adds a new row and a column. 
> 30-60 seconds later Machine B tries to read this row. It doesn't find the 
> row. So the application retries within 500ms. This time it finds the row.


You wrote a lot of useful info in your original post, sorry I missed
it in my first reply.
Only thing there that stands out, apart from short reads that Jeff's
already pointed out, is the use of `speculative_retry='ALWAYS'`. Has
there topology changes in your cluster recently?

Next step would be to try and repeat it with tracing.

regards,
Mick


-- 
Mick Semb Wever
Australia

The Last Pickle
Apache Cassandra Consulting
http://www.thelastpickle.com

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)

[Mick Semb Wever]

> Thanks James. Yeah, we're using the datastax java driver. But we're on 
> version 2.1.10.2. And we are not using the client side timestamps.


Just to check Ninad. If you are using Cassandra-2.1 (native protocol
v3) and the java driver version 3.0 or above, then you would be using
client-side timestamps by default.
https://github.com/datastax/java-driver/tree/3.x/manual/query_timestamps

With client-side timestamps all client servers and all C* nodes must
be kept tightly in-sync, as Elliot said. Monitoring and alerting on
any clock skew on any of these machines is important.

Also worth checking that any local_quorum requests are not
accidentally go to the wrong datacenter.

regards,
Mick

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Reaper 1.2 released

[Mick Semb Wever]

Feel free to file issues at 
https://github.com/thelastpickle/cassandra-reaper/issues
or chat with us at https://gitter.im/thelastpickle/cassandra-reaper

regards,
Mick



On Thu, 26 Jul 2018, at 06:18, Abdul Patel wrote:
> Was abke start it but unable to start any repair manually it says
> POST/repair_run
> Unit conflits with exiting in clustername
> 
> On Wednesday, July 25, 2018, Abdul Patel  wrote:
> 
> > Ignore , alter and create permission were missing ..will msg if i actually
> > see an showstopper
> >
> > On Wednesday, July 25, 2018, Abdul Patel  wrote:
> >
> >> I am trying to uograde to 1.2.2 version of reaper the instance isnt
> >> starting and giving error that unable to create table snapshot ..do we need
> >> to create it under reaper-db?
> >>
> >> On Wednesday, July 25, 2018, Steinmaurer, Thomas <
> >> thomas.steinmau...@dynatrace.com> wrote:
> >>
> >>> Jon,
> >>>
> >>>
> >>>
> >>> eager trying it out.  Just FYI. Followed the installation
> >>> instructions on http://cassandra-reaper.io/docs/download/install/
> >>> Debian-based.
> >>>
> >>>
> >>>
> >>> 1) Importing the key results in:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
> >>> 2895100917357435
> >>>
> >>> Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
> >>>
> >>> keyserver.ubuntu.com
> >>>
> >>> --recv-keys
> >>>
> >>> 2895100917357435
> >>>
> >>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
> >>>
> >>> ?: [fd 4]: read error: Connection reset by peer
> >>>
> >>> gpgkeys: HTTP fetch error 7: couldn't connect: eof
> >>>
> >>> gpg: no valid OpenPGP data found.
> >>>
> >>> gpg: Total number processed: 0
> >>>
> >>> gpg: keyserver communications error: keyserver unreachable
> >>>
> >>> gpg: keyserver communications error: public key not found
> >>>
> >>> gpg: keyserver receive failed: public key not found
> >>>
> >>>
> >>>
> >>> I had to change the keyserver URL then the import worked:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-key adv --keyserver *hkp://keyserver.ubuntu.com:80
> >>> * --recv-keys 2895100917357435
> >>>
> >>> Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
> >>>
> >>> hkp://keyserver.ubuntu.com:80
> >>>
> >>> --recv-keys
> >>>
> >>> 2895100917357435
> >>>
> >>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
> >>>
> >>> gpg: key 17357435: public key "TLP Reaper packages <
> >>> rea...@thelastpickle.com>" imported
> >>>
> >>> gpg: Total number processed: 1
> >>>
> >>> gpg:   imported: 1  (RSA: 1)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 2) Running apt-get update fails with:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-get update
> >>>
> >>> Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
> >>>
> >>> Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb 

Re: Inconsistent Quorum Read after Quorum Write

[Mick Semb Wever]

Li,

I did not reset repairedAt and ran repair with -pr directly. That’s
> probably why the inconsistency occurred.
>

Yes, this will be a likely cause. There's enough docs out there to help you
with this. Shout out if not.



> As our tables are pretty big, full repair takes many days to finish. Given
> the 10 days gc period, it means repair almost will run all the time.
> Consistency is more important to us and the cluster takes the same amount
> of write and read requests. Temporary outage is allowed but if a dead node
> can’t come back in time, we will go back to Quorum mode.
>

Yes, repairs can be a real headache.
Install Reaper. Seriously. http://cassandra-reaper.io/



> What’s new in 3.11.3? We’ve been running on C* for almost 2 years. The
> biggest pain point is about repair. Especially with 3.11.1, incremental
> repair doesn’t work well compared to our experience with 3.10. Maybe it’s
> just because our data size wasn’t that big before upgrade...
>


3.11.2 and 3.11.3 are just patch releases on top of 3.11.1.
It's definitely recommended to always *test* and upgrade to the latest
patch release. And it's kinda a prerequisite if you want help from the open
source community, none of us really enjoy debugging old code  :-)

regards,
Mick

-- 
Mick Semb Wever
Australia

The Last Pickle
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Inconsistent Quorum Read after Quorum Write

[Mick Semb Wever]

Li,


I’ve confirmed that the inconsistency issues disappeared after repair
> finished.
>
> Anything changed with repair in 3.11.1? One difference I noticed is that
> the validation step during repair could turn down the node upon large
> tables, which never happen in 3.10. I had to throttle validation requests
> to let it pass. Also I switched back to -pr instead of incremental repair
> which is a resource killer and often hangs for the first node to be
> repaired.
>


When you switched back to non-incremental did you set `repairedAt` on all
sstables (on all nodes) back to zero (or unrepaired state)?
This should have been done with `sstablerepairedset --is-unrepaired … `
while the node is stopped.



> To address the inconsistency issue, I could do Write All and Read One by
> giving up availability and stop running repair. Any comments on that?
>


You loose availability doing this, and at the number of reads you're doing
I would not recommend it.
You could think about using a fallback strategy that initially tries CL.ALL
and falls back to CL.QUORUM. But this is a hack, could overload your
cluster, and if there's any correlation to dropped messages or flapping
nodes won't help.

I'd also be prepared to upgrade to 3.11.3, when it does get released.

regards,
Mick

-- 
Mick Semb Wever
Australia

The Last Pickle
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: How to Protect Tracing Requests From Client Side

[Mick Semb Wever]

>
> Is there a way to protect C* on the server side from tracing commands that
> are executed from clients?
>


If you really needed a way to completely disable all and any possibility of
tracing you could start each C* node with tracing switched to a noop
implementation.

eg, add to the jvm.options file the line

-Dcassandra.custom_tracing_class=somepackage.NoOpTracing


while also putting into each $CASSANDRA_HOME/lib/ a jar file containing
this NoOpTracing class…

```
package somepackage;

import java.net.InetAddress;
import java.nio.ByteBuffer;
import java.util.Map;
import java.util.UUID;
import org.apache.cassandra.tracing.*;
import org.apache.cassandra.utils.FBUtilities;

/** Starting Cassandra with
'-Dcassandra.custom_tracing_class=org.apache.cassandra.tracing.NoOpTracing'
 * will forcibly disable all tracing.
 *
 * This can be useful in defensive environments.
 */
public final class NoOpTracing extends Tracing {

@Override
protected void stopSessionImpl() {}

@Override
public TraceState begin(String request, InetAddress client, Map<String,
String> parameters) {
return NoOpTraceState.INSTANCE;
}

@Override
protected TraceState newTraceState(InetAddress coordinator, UUID
sessionId, TraceType traceType) {
return NoOpTraceState.INSTANCE;
}

@Override
public void trace(ByteBuffer sessionId, String message, int ttl) {}

private static class NoOpTraceState extends TraceState {
private static final NoOpTraceState INSTANCE = new NoOpTraceState();
private NoOpTraceState() {
super(FBUtilities.getBroadcastAddress(), UUID.randomUUID(),
TraceType.NONE);
}
@Override
protected void traceImpl(String message) {}
}
}
```

regards,
Mick


-- 
Mick Semb Wever
Australia

The Last Pickle
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: 3.0.15 or 3.11.1

[Mick Semb Wever]

>
> Can you please provide dome JIRAs for superior fixes and performance
> improvements which are present in 3.11.1 but are missing in 3.0.15.
>


Some that come to mind…

Cassandra Storage Engine: CASSANDRA-12269, CASSANDRA-12731

Streaming and Compaction: CASSANDRA-11206, CASSANDRA-9766, CASSANDRA-11623,

Reintroduce off heap memtables –  CASSANDRA-9472

Re: Why does SASI index consume such a huge disk space?

[Mick Semb Wever]

> I use zipkin (https://github.com/openzipkin/zipkin) to trace my system.
>
> When I upgraded to the latest version ,3.23 be specific. I met a problem
which our monitor keep alerting that there is not enough disk space for
cassandra.


You're right. CONTAINS SASI indexes do indeed use a lot of disk space.

If you don't search by annotations in Zipkin feel free to drop that index.

`DROP INDEX zipkin2.span (annotation_query)`

We're looking into a more effective approach with this.
The CONTAINS SASI was used here because SASI on collections are not yet
supported: CASSANDRA-11182

An obvious improvement would be to manually denormalise the collection
first.

ref: https://github.com/openzipkin/zipkin/issues/1861#issuecomment-353510778

regards,
Mick

Re: 3.0.15 or 3.11.1

[Mick Semb Wever]

>
> I want to upgrade from 2.x to 3.x.
>
> I can definitely use the features in 3.11.1 but it's not a must.
> So my question is, is 3.11.1 stable and suitable for Production compared
> to 3.0.15?
>


Use 3.11.1 and don't use any 3.0.x or 3.x features.
3.11.1 is effectively three sequential patch releases, and the tick-tock
releases offered a number of superior fixes and performance improvements
over what was done in 3.0.x.

Introduce the use of new features later on, one at a time, after thorough
testing and staging.

regards,
Mick

Re: LegacySchemaTables.createKeyspaceFromSchemaPartition fails with an IllegalStateException

[Mick Semb Wever]

On 29 July 2016 at 05:13, Sotirios Delimanolis <sotodel...@yahoo.com> wrote:

> java.lang.IllegalStateException: One row required, 0 found
> at
> org.apache.cassandra.cql3.UntypedResultSet$FromResultSet.one(UntypedResultSet.java:77)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartition(LegacySchemaTables.java:758)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartitions(LegacySchemaTables.java:737)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at
> org.apache.cassandra.schema.LegacySchemaTables.readSchemaFromSystemTables(LegacySchemaTables.java:219)
> ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
>



Soto,
 I've created the following issue for this –
https://issues.apache.org/jira/browse/CASSANDRA-12351


-- 
Mick Semb Wever
Australia

The Last Pickle
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: CASSANDRA-2388 - ColumnFamilyRecordReader fails for a given split because a host is down

[Mick Semb Wever]

Sorry for such a late reply. I'm not always keeping up with the mailing
list.

 Is the following scenario covered by 2388? I have a test cluster of 6
 nodes with a replication factor of 3. Each server can execute hadoop
 tasks. 1 cassandra node is down for the test.
 
 The job is kicked off from node 1 jobtracker.
 A task is executed from node 1, and fails because the local cassandra
 instance is down
 retry on node 6, this tries to connect to node 1 and fails
 retry on node 5, this tries to connect to node 1 and fails
 retry on node 4, this tries to connect to node 1 and fails
 After 4 failures the task is killed and the job fails.
 
 Node 2 and 3 which contain the other replicas never run the task. The
 node selection seems to be random. I can modify the cassandra code to
 check connectivity in ColumnFamilyRecordReader but I suspect this is
 fixing the wrong problem.

There are two problems here.

1) hadoop's jobtracker isn't preferencing tasks to tasktracker that
would provide data locality.

2) connection replica nodes are never attempted directly, instead the
task must fail and be re-submitted to another tasktracker which
hopefully is a replica node.

 [snip] but this comment from mck seems to say it should work
 http://mail-archives.apache.org/mod_mbox/cassandra-user/201109.mbox/%
 3C1315253057.7466.222.camel@localhost%3E

not in your case. 
ColumnFamilyInputFormat splits the query into InputSplits. This is done
via the api calls describe_ring and describe_splits. These InputSplits
(ColumnFamilySplit) each has a list of locations which are the replica
nodes.

Now hadoop is supposed to preference sending tasks to tasktrackers based
on the split's location. This is problem (1). I haven't seen it actually
work. The closest information i got is
http://abel-perez.com/hadoop-task-assignment

Problem (2) is ColumnFamilyRecordReader.getLocation() returns you the
address from the list of locations for the current split that matches
the localhost. This preferences data locality. If none of the locations
is local then it simply returns the first location in the list. This
explains your use case not working. One fix for you to experiment with
is to increase the allowed task failures (i think it is
mapred.max.tracker.failures) to the number of nodes you have. Then each
node would be (randomly) tried before the task killed and job failed.

~mck


-- 
Friendship with the upright, with the truthful and with the well
informed is beneficial. Friendship with those who flatter, with those
who are meek and who compromise with principles, and with those who talk
cleverly is harmful. Confucius 

| http://github.com/finn-no | http://tech.finn.no |



signature.asc
Description: This is a digitally signed message part

Re: OOM opening bloom filter

[Mick Semb Wever]

 How much smaller did the BF get to ? 

After pending compactions completed today, i'm presuming fp_ratio is
applied now to all sstables in the keyspace, it has gone from 20G+ down
to 1G. This node is now running comfortably on Xmx4G (used heap ~1.5G).


~mck


-- 
A Microsoft Certified System Engineer is to information technology as a
McDonalds Certified Food Specialist is to the culinary arts. Michael
Bacarella 

| http://github.com/finn-no | http://tech.finn.no |


signature.asc
Description: This is a digitally signed message part

Re: OOM opening bloom filter

[Mick Semb Wever]

It's my understanding then for this use case that bloom filters are of
little importance and that i can


Ok. To summarise our actions to get us out of this situation, in hope
that it may help others one day, we did the following actions:

 1) upgrade to 1.0.7
 2) set fp_ratio=0.99
 3) set index_interval=4096
 4) restarted the node with Xmx30G
 5) run `nodetool scrub` 
  and monitor total size of bf files
  using `du -hc *-Filter.db | grep total`
 6) restart node with original Xmx setting once total bf size is under
  (scrub was running for 12hrs)
  (remaining bloom filters can be rebuilt later from normal compact)

Hopefully it will also eventuate that this cluster can run with a more
normal Xmx4G rather than the previous Xmx12G.

(2) and (3) are very much dependent on our set up using hadoop where all
reads are get_range_slice with 16k rows per request. Both could be tuned
correctly but they're the numbers that worked first up.

~mck

-- 
When there is no enemy within, the enemies outside can't hurt you.
African proverb 

| http://github.com/finn-no | http://tech.finn.no |


signature.asc
Description: This is a digitally signed message part

OOM opening bloom filter

[Mick Semb Wever]

Using cassandra-1.0.6 one node fails to start.

java.lang.OutOfMemoryError: Java heap space
at org.apache.cassandra.utils.obs.OpenBitSet.init(OpenBitSet.java:104)
at org.apache.cassandra.utils.obs.OpenBitSet.init(OpenBitSet.java:92)
at 
org.apache.cassandra.utils.BloomFilterSerializer.deserialize(BloomFilterSerializer.java:55)
at 
org.apache.cassandra.io.sstable.SSTableReader.loadBloomFilter(SSTableReader.java:308)
at 
org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:168)
at 
org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:205)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


This happens with (our normal) -Xmx12g setting.

How did this this bloom filter get too big?
Is the best option to keep trying with larger Xmx settings until i can
startup the node and then to do a `nodetool scrub` ?

~mck


-- 
Don't use Outlook. Outlook is really just a security hole with a small
e-mail client attached to it. Brian Trosko 

| http://github.com/finn-no | http://tech.finn.no |


signature.asc
Description: This is a digitally signed message part

Re: OOM opening bloom filter

[Mick Semb Wever]

On Sun, 2012-03-11 at 15:06 -0700, Peter Schuller wrote:
 If it is legitimate use of memory, you *may*, depending on your
 workload, want to adjust target bloom filter false positive rates:
 
https://issues.apache.org/jira/browse/CASSANDRA-3497 

This particular cf has up to ~10 billion rows over 3 nodes. Each row is
very small, 1k. Data from this cf is only read via hadoop jobs in batch
reads of 16k rows at a time. 

*-Data.db files are typically ~50G, and *-Filter.db files typically 2G
although some are 7Gb.
At the moment there are many pending compactions, but i can't do any
because the node crashes at startup.

It's my understanding then for this use case that bloom filters are of
little importance and that i can 
 - upgrade to 1.0.7
 - set fp_ratio=0.99
 - set index_interval=1024

This should alleviate much of the memory problems.
Is this correct?

~mck

-- 
It seems that perfection is reached not when there is nothing left to
add, but when there is nothing left to take away Antoine de Saint
Exupéry (William of Ockham) 

| http://github.com/finn-no | http://tech.finn.no |



signature.asc
Description: This is a digitally signed message part

Re: OOM opening bloom filter

[Mick Semb Wever]

On Sun, 2012-03-11 at 15:36 -0700, Peter Schuller wrote:
 Are you doing RF=1? 

That is correct. So are you calculations then :-)


  very small, 1k. Data from this cf is only read via hadoop jobs in batch
  reads of 16k rows at a time.
 [snip]
  It's my understanding then for this use case that bloom filters are of
  little importance and that i can
 
 Depends. I'm not familiar enough with how the hadoop integration works
 so someone else will have to comment, but if your hadoop jobs are just
 performan normal reads of keys via thrift and the keys they are
 grabbing are not in token order, those reads would be effectively
 random and bloom filters should still be highly relevant to the amount
 of I/O operations you need to perform. 

They are thrift get_range_slice reads of 16k rows per request.
Hadoop reads are based on tokens, but in my use case the keys are also
ordered and this cluster is using BOP.

~mck

-- 
Living on Earth is expensive, but it does include a free trip around
the sun every year. Unknown 

| http://github.com/finn-no | http://tech.finn.no |


signature.asc
Description: This is a digitally signed message part

memory problems still post- CASSANDRA-3492

[Mick Semb Wever]

I've got a following problem to CASSANDRA-3492, also related to
ridiculously high memory. 

After the fix yesterday for CASSANDRA-3492 I have that node in question
up and running. 

But another node (on the same machine but different cluster), even after
an upgrade to the staging 1.0.3 and a `nodetool scrub`, always soaks all
available memory (up to and plateau at 30G). In fact no cf there use
compression anymore. 

  It has been down for some days now while I was working on that other
node.
  After it has finished startup memory just keeps growing to 30G.
Although i don't see any OOM when Xmx is set lower the node basically
becomes unusable.
  I can see in tpstats 

HintedHandoff  (active)1(pending)2

 and it just seems to stay like that. 

Is there a way to more closely monitor that active hinted handoff? 
Can one hinted handoff be responsible for such heap?

~mck


-- 
Driving ambition is the last refuge of the failure. Oscar Wilde 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: range slice with TimeUUID column names

[Mick Semb Wever]

On Thu, 2011-11-10 at 22:35 -0800, footh wrote:
 
 UUID startId = new UUID(UUIDGen.createTime(start), 
 UUIDGen.getClockSeqAndNode());
 UUID finishId = new UUID(UUIDGen.createTime(finish), 
 UUIDGen.getClockSeqAndNode()); 

You have got comparator_type = TimeUUIDType ?

~mck


-- 
The old law about 'an eye for an eye' leaves everybody blind. Martin
Luther King. Jr. 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

get_range_slices OOM on CompressionMetadata.readChunkOffsets(..)

[Mick Semb Wever]

After an upgrade to cassandra-1.0 any get_range_slices gives me:

java.lang.OutOfMemoryError: Java heap space
at 
org.apache.cassandra.io.compress.CompressionMetadata.readChunkOffsets(CompressionMetadata.java:93)
at 
org.apache.cassandra.io.compress.CompressionMetadata.init(CompressionMetadata.java:66)
at 
org.apache.cassandra.io.compress.CompressedRandomAccessReader.metadata(CompressedRandomAccessReader.java:53)
at 
org.apache.cassandra.io.compress.CompressedRandomAccessReader.open(CompressedRandomAccessReader.java:63)
at 
org.apache.cassandra.io.sstable.SSTableReader.openDataReader(SSTableReader.java:896)
at 
org.apache.cassandra.io.sstable.SSTableScanner.init(SSTableScanner.java:72)
at 
org.apache.cassandra.io.sstable.SSTableReader.getScanner(SSTableReader.java:748)
at 
org.apache.cassandra.db.RowIteratorFactory.getIterator(RowIteratorFactory.java:88)
at 
org.apache.cassandra.db.ColumnFamilyStore.getRangeSlice(ColumnFamilyStore.java:1310)
at 
org.apache.cassandra.service.StorageProxy.getRangeSlice(StorageProxy.java:840)
at 
org.apache.cassandra.thrift.CassandraServer.get_range_slices(CassandraServer.java:698)


I set chunk_length_kb to 16 as my rows are very skinny (typically 100b)

Any way around this?

~mck

-- 
Physics is the universe's operating system. Steven R Garman 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |



signature.asc
Description: This is a digitally signed message part

Re: get_range_slices OOM on CompressionMetadata.readChunkOffsets(..)

[Mick Semb Wever]

On Mon, 2011-10-31 at 08:00 +0100, Mick Semb Wever wrote:
 After an upgrade to cassandra-1.0 any get_range_slices gives me:
 
 java.lang.OutOfMemoryError: Java heap space
   at 
 org.apache.cassandra.io.compress.CompressionMetadata.readChunkOffsets(CompressionMetadata.java:93)
   at 
 org.apache.cassandra.io.compress.CompressionMetadata.init(CompressionMetadata.java:66)
   at 
 org.apache.cassandra.io.compress.CompressedRandomAccessReader.metadata(CompressedRandomAccessReader.java:53)
   at 
 org.apache.cassandra.io.compress.CompressedRandomAccessReader.open(CompressedRandomAccessReader.java:63)
   at 
 org.apache.cassandra.io.sstable.SSTableReader.openDataReader(SSTableReader.java:896)
   at 
 org.apache.cassandra.io.sstable.SSTableScanner.init(SSTableScanner.java:72)
   at 
 org.apache.cassandra.io.sstable.SSTableReader.getScanner(SSTableReader.java:748)
   at 
 org.apache.cassandra.db.RowIteratorFactory.getIterator(RowIteratorFactory.java:88)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getRangeSlice(ColumnFamilyStore.java:1310)
   at 
 org.apache.cassandra.service.StorageProxy.getRangeSlice(StorageProxy.java:840)
   at 
 org.apache.cassandra.thrift.CassandraServer.get_range_slices(CassandraServer.java:698)
 
 
 I set chunk_length_kb to 16 as my rows are very skinny (typically 100b)


I see now this was a bad choice.
The read pattern of these rows is always in bulk so the chunk_length
could have been much higher so to reduce memory usage (my largest
sstable is 61G).

After changing the ckunk_length is there any way to rebuild just some
sstables rather than having to do a full nodetool scrub ?

~mck

-- 
“An idea is a point of departure and no more. As soon as you elaborate
it, it becomes transformed by thought.” - Pablo Picasso 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: get_range_slices OOM on CompressionMetadata.readChunkOffsets(..)

[Mick Semb Wever]

On Mon, 2011-10-31 at 10:08 +0100, Sylvain Lebresne wrote:
  I set chunk_length_kb to 16 as my rows are very skinny (typically 100b)
 
 
  I see now this was a bad choice.
  The read pattern of these rows is always in bulk so the chunk_length
  could have been much higher so to reduce memory usage (my largest
  sstable is 61G).
 
  After changing the ckunk_length is there any way to rebuild just some
  sstables rather than having to do a full nodetool scrub ?
 
 Provided you're using SizeTieredCompaction (i.e, the default), you can
 trigger a user defined compaction through JMX on each of the sstable
 you want to rebuild. Not necessarily a fun process though. Also note that
 you can scrub only an individual column family if that was the question. 

Actually this won't work i think.

I presume that scrub or any user defined compaction will still need to
SSTableReader.openDataReader(..) and so will still OOM no matter what...

How the hell am i supposed to re-chunk_length an sstable? :-(

~mck

-- 
We all may have come on different ships, but we’re in the same boat
now. Martin Luther King. Jr. 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |



signature.asc
Description: This is a digitally signed message part

Re: OOM on CompressionMetadata.readChunkOffsets(..)

[Mick Semb Wever]

On Mon, 2011-10-31 at 09:07 +0100, Mick Semb Wever wrote:
 The read pattern of these rows is always in bulk so the chunk_length
 could have been much higher so to reduce memory usage (my largest
 sstable is 61G). 

Isn't CompressionMetadata.readChunkOffsets(..) rather dangerous here?

Given a 60G sstable, even with 64kb chunk_length, to read just that one
sstable requires close to 8G free heap memory...

Especially when the default for cassandra is 4G heap in total.

~mck

-- 
Anyone who has attended a computer conference in a fancy hotel can tell
you that a sentence like You're one of those computer people, aren't
you? is roughly equivalent to Look, another amazingly mobile form of
slime mold! in the mouth of a hotel cocktail waitress. Elizabeth
Zwicky 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: OOM on CompressionMetadata.readChunkOffsets(..)

[Mick Semb Wever]

On Mon, 2011-10-31 at 13:05 +0100, Mick Semb Wever wrote:
 Given a 60G sstable, even with 64kb chunk_length, to read just that one
 sstable requires close to 8G free heap memory... 

Arg, that calculation was a little off...
 (a long isn't exactly 8K...)

But you get my concern...

~mck

-- 
When you say: I wrote a program that crashed Windows, people just
stare at you blankly and say: Hey, I got those with the system -- for
free. Linus Torvalds 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: Task's map reading more record than CFIF's inputSplitSize

[Mick Semb Wever]

  3 map tasks (from 4013) is still running after read 25 million rows.
  Can this be a bug in StorageService.getSplits(..) ? 

 getSplits looks pretty foolproof to me but I guess we'd need to add
 more debug logging to rule out a bug there for sure.
 
 I guess the main alternative would be a bug in the recordreader paging.

Entered https://issues.apache.org/jira/browse/CASSANDRA-3150

~mck

-- 
“People only see what they're prepared to see.” - Ralph Waldo Emerson 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: RF=1 w/ hadoop jobs

[Mick Semb Wever]

On Fri, 2011-09-02 at 09:28 +0200, Patrik Modesto wrote:
 We use Cassandra as a storage for web-pages, we store the HTML, all
 URLs that has the same HTML data and some computed data. We run Hadoop
 MR jobs to compute lexical and thematical data for each page and for
 exporting the data to a binary files for later use. URL gets to a
 Cassandra on user request (a pageview) so if we delete an URL, it gets
 back quickly if the page is active. Because of that and because there
 is lots of data, we have the keyspace set to RF=1. We can drop the
 whole keyspace and it will regenerate quickly and would contain only
 fresh data, so we don't care about lossing a node. 

I've entered a jira issue covering this request.
https://issues.apache.org/jira/browse/CASSANDRA-3136

Would you mind attaching your patch to the issue.
(No review of it will happen anywhere else.)

~mck

-- 
“Innovators and creative geniuses cannot be reared in schools. They are
precisely the men who defy what the school has taught them.” - Ludwig
von Mises 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |



signature.asc
Description: This is a digitally signed message part

Re: KeyRange in the CoumnFamilyInputFormat

[Mick Semb Wever]

On Mon, 2011-09-05 at 18:18 +0300, Vitaly Vengrov wrote:
 See these rows in the ColumnFamilyInputFormat.getSplits method : 
 
 assert jobKeyRange.start_key == null : only start_token supported;  

 assert jobKeyRange.end_key == null : only end_token supported; 
 
 So, the question is why start_key and end_key aren't supported ? 
 
 What I actually need is the ability to specify exact rowKey (UUID).
 Not a key range.  I believe I can do this with same start and end keys
 but not with tokes. 

The background to this is CASSANDRA-1125 and specifically this comment
https://issues.apache.org/jira/browse/CASSANDRA-1125?focusedCommentId=13058858page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13058858

Tokens are used here to be consistent with the thrift API.

What you want is:


ConfigHelper.setInputRange(
jobConf,

partitioner.getTokenFactory().toString(partitioner.getToken(myKey)),

partitioner.getTokenFactory().toString(partitioner.getToken(myKey)));


In fact this would not be possible if you were using range.start_key and
range.end_key since that would exclude the one row you are trying to
include.

Out of curiosity why are you using hadoop to process one row?
Won't this be solely processed by one split and therefore only one task?

~mck

-- 
The only thing I know, is that I know nothing. Socrates 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: KeyRange in the CoumnFamilyInputFormat

[Mick Semb Wever]

On Mon, 2011-09-05 at 19:02 +0200, Mick Semb Wever wrote:
 
 ConfigHelper.setInputRange(
 jobConf,
 
 partitioner.getTokenFactory().toString(partitioner.getToken(myKey)),
 
 partitioner.getTokenFactory().toString(partitioner.getToken(myKey)));
 
 
 In fact this would not be possible if you were using range.start_key and
 range.end_key since that would exclude the one row you are trying to
 include. 

Sorry i take that back. It's ofc keys that are start-inclusive.

~mck

-- 
Those people who think they know everything are a great annoyance to
those of us who do. Isaac Asimov 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |



signature.asc
Description: This is a digitally signed message part

Re: RF=1 w/ hadoop jobs

[Mick Semb Wever]

On Mon, 2011-09-05 at 21:52 +0200, Patrik Modesto wrote:
 I'm not sure about 0.8.x and 0.7.9 (to be released today with your
 patch) but 0.7.8 will fail even with RF1 when there is Hadoop
 TaskTracer without local Cassandra. So increasing RF is not a
 solution. 

This isn't true (or not the intention).

If you increase RF then yes the task will fail but it will get re-run on
the next replica. So the job takes longer but should still work.

~mck

-- 
This is my simple religion. There is no need for temples; no need for
complicated philosophy. Our own brain, our own heart is our temple; the
philosophy is kindness. The Dalai Lama 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |


signature.asc
Description: This is a digitally signed message part

Re: RF=1 w/ hadoop jobs

[Mick Semb Wever]

On Fri, 2011-09-02 at 08:20 +0200, Patrik Modesto wrote:
 As Jonathan
 already explained himself: ignoring unavailable ranges is a
 misfeature, imo 

Generally it's not what one would want i think.
But I can see the case when data is to be treated volatile and ignoring
unavailable ranges may be acceptable. 

For example if you searching for something or some-pattern and one hit
is enough. If you get the hit it's a positive result regardless if
ranges were ignored, if you don't and you *know* there was a range
ignored along the way you can re-run the job later. The worse case
scenario here is no worse than the job always failing on you. Although
some indication of ranges ignored is required.

Another example is when your just trying to extract a small random
sample (like a pig SAMPLE) of data out of cassandra.

Patrik: is it possible to describe the use-case you have here?

~mck

-- 
“The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore, all
progress depends on the unreasonable man.” - George Bernard Shaw 

| http://semb.wever.org | http://sesat.no |
| http://tech.finn.no   | Java XSS Filter |



signature.asc
Description: This is a digitally signed message part

Re: [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns

[Mick Semb Wever]

On Sun, 2011-06-12 at 18:53 +, Mick Semb Wever wrote:
  This issue could stand to be summarized (I still wish we used a
  mailing list for monsters like this).
 
 
 This i actually really appreciate about the cassandra community. 

To formulate this: As a newbie here it has allowed me to understand
individual issues, their history and development discussion, without
having to go all in and subscribe to the development list. The latter
can be quite a daunting task in some communities to begin and keep up
with if it is where all development discussion is happening.
that's 2cents anyway from someone still finding their way into the code.

~mck

-- 
We are born naked, wet and hungry. Then things get worse. 
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no   | Java XSS Filter



signature.asc
Description: This is a digitally signed message part

Re: [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns

[Mick Semb Wever]

On Sun, 2011-06-12 at 13:50 +, Eric Evans (JIRA) wrote:
 Eric Evans commented on CASSANDRA-2474:
 ---
 
 This issue could stand to be summarized (I still wish we used a
 mailing list for monsters like this).


This i actually really appreciate about the cassandra community.
Although it would certainly be better if comments in jira issues
supported threads... https://jira.atlassian.com/browse/JRA-3406

Why not send all Jira changes to a mailing already (like other
communities do). Along with threading (if it is ever implemented) you
would get the best of both worlds right?

~mck


-- 
Although the Buddhists will tell you that desire is the root of
suffering, my personal experience leads me to point the finger at system
administration. Philip Greenspun 
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Re: [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns

[Mick Semb Wever]

On Sun, 2011-06-12 at 12:10 -0500, Eric Evans wrote:
  Why not send all Jira changes to a mailing already (like other
  communities do).
 
 We do. 

I had a quick search and could not find it.

But now i see it's part of the commits list.

~mck

-- 
Everything you can imagine is real. Pablo Picasso 
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

CL.ONE gives UnavailableException on ok node

[Mick Semb Wever]

Just experienced something i don't understand yet.

Running a 3 node cluster successfully for a few days now, then one of
the nodes went down (server required reboot).
After this the other two nodes kept throwing UnavailableExceptions like

UnavailableException()
at 
org.apache.cassandra.service.WriteResponseHandler.assureSufficientLiveNodes(WriteResponseHandler.java:127)
at 
org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:118)
at 
no.finntech.countstats.listener.CassandraMessageListener$1.run(CassandraMessageListener.java:356)

(this code being loosely based off the second example in
http://wiki.apache.org/cassandra/ScribeToCassandra ).

This seems a bit weird to me when the StorageProxy.mutate(..) is being
called with ConsistencyLevel.ONE.

I'm running 0.7.4 so i doubt it to be CASSANDRA-2069

~mck

-- 
Everything you can imagine is real. Pablo Picasso 
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no   | Java XSS Filter



signature.asc
Description: This is a digitally signed message part

Re: CL.ONE gives UnavailableException on ok node

[Mick Semb Wever]

On Fri, 2011-04-15 at 15:43 -0500, Jonathan Ellis wrote:
 Sure sounds like you have RF=1 to me.

Yes that's right.

I see... so the answer here is that i should be using CL.ANY ?
(so the write goes through and hinted handoff can get it to the correct
node latter on).

~mck

-- 
The fox condemns the trap, not himself. William Blake 
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Re: map reduce job over indexed range of keys

[Mick Semb Wever]

On Thu, 2011-02-24 at 19:45 -0500, Matt Kennedy wrote:
 Right, so I'm interpreting silence as a confirmation on all points. I
 opened:
 https://issues.apache.org/jira/browse/CASSANDRA-2245
 https://issues.apache.org/jira/browse/CASSANDRA-2246

I think https://issues.apache.org/jira/browse/CASSANDRA-1125 is what you
were looking for. Sorry for the late reply.

~mck

-- 
When there is no enemy within, the enemies outside can't hurt you.
African proverb 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter



signature.asc
Description: This is a digitally signed message part

Re: [mapreduce] ColumnFamilyRecordWriter hidden reuse

[Mick Semb Wever]

On Tue, 2011-01-25 at 09:37 +0100, Patrik Modesto wrote:
 While developing really simple MR task, I've found that a
 combiantion of Hadoop optimalization and Cassandra
 ColumnFamilyRecordWriter queue creates wrong keys to send to
 batch_mutate(). 

I've seen similar behaviour (junk rows being written), although my keys
are always a result from
  LongSerializer.get().toByteBuffer(key)


i'm interested in looking into it - but can you provide a code example? 

  From what i can see TextOutputFormat.LineRecordWriter.write(..)
doesn't clone anything, but it does write it out immediately.
  While ColumnFamilyRecordWriter does batch the mutations up as you say,
it takes a ByteBuffer as a key, why/how are you re-using this
client-side (arn't you creating a new ByteBuffer each call to
write(..))?

~mck

-- 
Never let your sense of morals get in the way of doing what's right.
Isaac Asimov 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter



signature.asc
Description: This is a digitally signed message part

Re: [mapreduce] ColumnFamilyRecordWriter hidden reuse

[Mick Semb Wever]

On Tue, 2011-01-25 at 14:16 +0100, Patrik Modesto wrote:
 The atttached file contains the working version with cloned key in
 reduce() method. My other aproache was:
 
  context.write(ByteBuffer.wrap(key.getBytes(), 0, key.getLength()),
  Collections.singletonList(getMutation(key)));
 
 Which produce junk keys. 

In fact i have another problem (trying to write an empty byte[], or
something, as a key, which put one whole row out of whack, ((one row in
25 million...))).

But i'm debugging along the same code.

I don't quite understand how the byte[] in 
ByteBuffer.wrap(key.getBytes(),...)
gets clobbered.
Well your key is a mutable Text object, so i can see some possibility
depending on how hadoop uses these objects.
Is there something to ByteBuffer.allocate(..) i'm missing...

btw.
 is d.timestamp = System.currentTimeMillis(); ok?
 shouldn't this be microseconds so that each mutation has a different
timestamp? http://wiki.apache.org/cassandra/DataModel


~mck


-- 
As you go the way of life, you will see a great chasm. Jump. It is not
as wide as you think. Native American Initiation Rite 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter

-- 
Everything should be made as simple as possible, but not simpler.
Albert Einstein (William of Ockham) 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Re: Cassandra on iSCSI?

[Mick Semb Wever]

 So if one is forced to use a SAN, how should you set up Cassandra is
 the interesting question - to me! Here are some thoughts:- 
 1. Ensure that each node gets dedicated - not shared - LUNs 
 2. Ensure that these LUNs do share spindles, or nodes will seize to be
 isolatable (this will be tough to get, given how SAN administrators
 think about this) 
 3. Most SANs deliver performance by striping (RAID 0) - sacrifice
 striping for isolation if push comes to shove 
 4. Do not share data directories from multiple nodes onto a single
 location via NFS or CFS for example. They are cool in shared resource
 environments, but breaks the premise behind Cassandra. All data
 storage should be private to the cassandra node, even when on shared
 storage 
 5. Do not change any assumption around Replication Factor (RF) or
 Consistency Level (CL) due to the shared storage - in fact if
 anything, increase your replication factor because you now have
 potential SPOF storage.  

That was gold, and lead to a direct conversation between provider and
developer. Various tests showed IOPS will often be at 5k per node.
Therefore the iSCSI solution would need to be tailored to handle it.

Just like mentioned above our provider simply couldn't provide us so much
disk per server. But after a good discussion it became obvious (doh!)
that the application can actually save a lot of disk by using different
keyspaces with different RF. We have raw data that needs to be
collected, but can be temporarily unavailable for reading, hence RF=1
makes sense. This raw data is the vast bulk of the data so this saves
lots of disk space. The aggregated data, which is relatively small in
comparison, is critical for the application to read so we can keep in a
separate keyspace with higher RF...

~mck

-- 
“Anyone who lives within their means suffers from a lack of
imagination.” - Oscar Wilde 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter



signature.asc
Description: This is a digitally signed message part

Re: Cassandra on iSCSI?

[Mick Semb Wever]

 Of course with a SAN you'd want RF=1 since it's replicating
 internally. 

Isn't this the same case for raid-5 as well?

And we want RF=2 if we need to keep reading while doing rolling
restarts?

~mck

-- 
“Anyone who lives within their means suffers from a lack of
imagination.” - Oscar Wilde 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Re: Cassandra on iSCSI?

[Mick Semb Wever]

 [OT] They're quoting roughly the same price for both (claiming
 that the
 extra cost goes into having for each node a separate disk
 cabinet to run
 local raid-5).
 
 You might not need raid-5 for local attached storage. 

Yes we did ask. But raid-5 is the minimum being offered from our hosting
provider... We could go to raid 10, but raid 0 is out of the question...

~mck

-- 
To be young, really young, takes a very long time. Picasso 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Cassandra on iSCSI?

[Mick Semb Wever]

Does anyone have any experiences with Cassandra on iSCSI?

I'm currently testing a (soon-to-be) production server using both local
raid-5 and iSCSI disks. Our hosting provider is pushing us hard towards
the iSCSI disks because it is easier for them to run (and to meet our
needs for increasing disk capacity overtime).

I'm worried that iSCSI is a non-scalable solution for an otherwise
scalable application (all cassandra nodes will have separate partitions
to the one iSCSI).

To go with raid-5 disks our hosting provider requires proof that iSCSI
won't work. I tried various things (eg `nodetool cleanup` on 12Gb load
giving 5k IOPS) but iSCSI seems to keep up to the performance of the
local raid-5 disks...

Should i be worried about using iSCSI?
Are there better tests i should be running? 

~mck

-- 
The turtle only makes progress when it's neck is stuck out Rollo May 
| http://semb.wever.org | http://sesat.no
| http://finn.no   | Java XSS Filter


signature.asc
Description: This is a digitally signed message part

Re: Cassandra on iSCSI?

[Mick Semb Wever]

 It should work fine; the main reason to go with local storage is the
 huge cost advantage.

[OT] They're quoting roughly the same price for both (claiming that the
extra cost goes into having for each node a separate disk cabinet to run
local raid-5).

 *I just committed a README for contrib/stress to the 0.7 svn branch 

thanks! i'll check it out.

~mck

-- 
“An invasion of armies can be resisted, but not an idea whose time has
come.” - Victor Hugo 
| www.semb.wever.org | www.sesat.no 
| www.finn.no | http://xss-http-filter.sf.net


signature.asc
Description: This is a digitally signed message part