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

Feed expired key deletion events to subscriber, then finally deliver to a watch client. #8540

Closed
Tracked by #8425
drmingdrmer opened this issue Oct 31, 2022 · 0 comments · Fixed by #8539
Closed
Tracked by #8425
Assignees
Labels
A-meta Area: databend meta serive

Comments

@drmingdrmer
Copy link
Member

No description provided.

drmingdrmer added a commit to drmingdrmer/databend that referenced this issue Oct 31, 2022
- Clean upto 32 expired keys before applying a raft-log.

- When modifying(insert/update/delete) a kv record, it emits at most two event:
  - If the existent key expired, emit a `delete` event, because a
    expired key is seen and removed.
  - Then the event of the update follows.

- Fix: databendlabs#8489
- Fix: databendlabs#8490
- Fix: databendlabs#8540
@drmingdrmer drmingdrmer self-assigned this Oct 31, 2022
@drmingdrmer drmingdrmer added A-meta Area: databend meta serive A-api Area: databend REST/Admin and JDBC driver and removed A-api Area: databend REST/Admin and JDBC driver labels Oct 31, 2022
@mergify mergify bot closed this as completed in fd0cb56 Oct 31, 2022
@mergify mergify bot closed this as completed in #8539 Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: databend meta serive
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant