Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion relay-server/src/services/buffer/envelope_stack/sqlite.rs
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ impl SqliteEnvelopeStack {
/// In case an envelope fails deserialization due to malformed data in the database, the affected
/// envelope will not be unspooled and unspooling will continue with the remaining envelopes.
async fn unspool_from_disk(&mut self) -> Result<(), SqliteEnvelopeStackError> {
let envelopes = relay_statsd::metric!(timer(RelayTimers::BufferUnspool), {
let mut envelopes = relay_statsd::metric!(timer(RelayTimers::BufferUnspool), {
self.envelope_store
.delete_many(
self.own_key,
Expand All @@ -139,6 +139,11 @@ impl SqliteEnvelopeStack {
return Ok(());
}

// Since the store returns the envelopes sorted in descending order, we want to put them
// in reverse into the vector in the buffer, because we want to pop the last element always,
// which has to be the newest (aka with the biggest timestamp).
envelopes.reverse();

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why do we reverse twice, once here and once in delete_many?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It's explained in the comment above, I wanted to return descending values from the store but when concatenating in the buffer, we pop from the bottom (which we assume has the newest timestamp).


// We push in the back of the buffer, since we still want to give priority to
// incoming envelopes that have a more recent timestamp.
self.batches_buffer_size += envelopes.len();
Expand Down
38 changes: 28 additions & 10 deletions relay-server/src/services/buffer/envelope_store/sqlite.rs
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
use std::cmp::Reverse;
use std::error::Error;
use std::path::Path;
use std::pin::pin;
Expand All @@ -13,6 +14,7 @@ use crate::Envelope;
use futures::stream::StreamExt;
use hashbrown::HashSet;
use relay_base_schema::project::{ParseProjectKeyError, ProjectKey};
use relay_common::time::UnixTimestamp;
use relay_config::Config;
use sqlx::migrate::MigrateError;
use sqlx::query::Query;
Expand Down Expand Up @@ -370,9 +372,12 @@ impl SqliteEnvelopeStore {
}

// We sort envelopes by `received_at`.
//
// Unfortunately we have to do this because SQLite `DELETE` with `RETURNING` doesn't
// return deleted rows in a specific order.
extracted_envelopes.sort_by_key(|a| a.received_at());
extracted_envelopes.sort_by_key(|a| {
Reverse(UnixTimestamp::from_datetime(a.received_at()).unwrap_or(UnixTimestamp::now()))

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I forgot to return the dates in reverse sorted order to honor the API. This is now fixed, the envelopes are returning in descending timestamp order.

});

Ok(extracted_envelopes)
}
Expand Down Expand Up @@ -518,12 +523,10 @@ pub fn build_count_all<'a>() -> Query<'a, Sqlite, SqliteArguments<'a>> {

#[cfg(test)]
mod tests {
use hashbrown::HashSet;
use std::time::Duration;
use tokio::time::sleep;

use relay_base_schema::project::ProjectKey;
use relay_event_schema::protocol::EventId;

use super::*;
use crate::services::buffer::testutils::utils::{mock_envelopes, setup_db};
Expand All @@ -538,21 +541,36 @@ mod tests {

// We insert 10 envelopes.
let envelopes = mock_envelopes(10);
let envelope_ids: HashSet<EventId> =
envelopes.iter().filter_map(|e| e.event_id()).collect();
assert!(envelope_store
.insert_many(envelopes.iter().map(|e| e.as_ref().try_into().unwrap()))
.await
.is_ok());

// We check that if we load more than the limit, we still get back at most 10.
// We check that if we load 5, we get the newest 5.
let extracted_envelopes = envelope_store

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed and improved this test.

.delete_many(own_key, sampling_key, 5)
.await
.unwrap();
assert_eq!(extracted_envelopes.len(), 5);
for i in 0..5 {
assert_eq!(
extracted_envelopes[i].event_id(),
envelopes[5..][4 - i].event_id()
);
}

// We check that if we load more than the envelopes stored on disk, we still get back at
// most 5.
let extracted_envelopes = envelope_store
.delete_many(own_key, sampling_key, 15)
.delete_many(own_key, sampling_key, 10)
.await
.unwrap();
assert_eq!(envelopes.len(), 10);
for envelope in extracted_envelopes {
assert!(envelope_ids.contains(&envelope.event_id().unwrap()));
assert_eq!(extracted_envelopes.len(), 5);
for i in 0..5 {
assert_eq!(
extracted_envelopes[i].event_id(),
envelopes[0..5][4 - i].event_id()
);
}
}

Expand Down