Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Airmail 20240628 #5178

Closed
wants to merge 5 commits into from
Closed

Airmail 20240628 #5178

wants to merge 5 commits into from

Conversation

fulmicoton
Copy link
Contributor

No description provided.

- to deal with the \0 sstable ordering bug
- to include @PSeitz version of the columnar multivalue sparse index fix.
The piece that estimates whether the next request is likely to fail is extremely simplistic for the moment.
It simply counter the number of errors (not taking in account successes) that happened in a given time window.

The reason is that for the moment, we want to use it for persist requests when the WAL is full.
On airmail, the aggressive retry logic of the client was causing a massive grpc storm on the faulty indexer node,
taking all of its CPU and preventing it from getting out of that state.

In this case, the error estimation logic is very simple, a full WAL guarantees that no further persist request will be successful for a little while.
Copy link

On SSD:

Average search latency is 0.991x that of the reference (lower is better).
Ref run id: 2374, ref commit: f4e5710
Link

On GCS:

Average search latency is 1.03x that of the reference (lower is better).
Ref run id: 2375, ref commit: f4e5710
Link

@fulmicoton fulmicoton closed this Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant