Skip to content

Conversation

@tomwilkie
Copy link
Contributor

This causes tombstones to be written to Cassandra, which causes excessive heap usage.:

Signed-off-by: Tom Wilkie tom@grafana.com

What this PR does:

We write empty values (just using the row and column value) for metric name and series rows.
These empty value cause tombstones to be written to Cortex (https://thelastpickle.com/blog/2018/07/05/undetectable-tombstones-in-apache-cassandra.html). Tombstones make Cassandra slow(er).

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

This causes tombstones to be written to Cassandra, which causes excessive heap usage.:

Signed-off-by: Tom Wilkie <tom@grafana.com>
Copy link
Contributor

@jtlisi jtlisi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gouthamve gouthamve merged commit b4b3ebc into master May 5, 2020
gouthamve pushed a commit to grafana/cortex that referenced this pull request May 7, 2020
This causes tombstones to be written to Cassandra, which causes excessive heap usage.:

Signed-off-by: Tom Wilkie <tom@grafana.com>
@tomwilkie tomwilkie deleted the dont-write-null-values-to-index branch June 8, 2020 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants