Skip to content
Madelyn Olson edited this page Aug 11, 2026 · 160 revisions

Weekly online meeting

The Valkey community hosts a weekly meeting to discuss any topic that requires an online discussion. The meeting is every Monday at 8:00 Pacific time. (16:00 or 15:00 UTC). You can find the link and the exact details of the upcoming meetings here: https://zoom-lfx.platform.linuxfoundation.org/meetings/valkey?view=week.

Anyone is welcome to come and participate in the meeting. If you have a topic you would like to discuss, please add it under the Next Agenda section in the following format. The discussion must include a link to the relevant pull request or issue to be discussed, we will not review topics that have not been previously discussed in the community.

Format and introduction

Notes will take the form of:

  1. Top level topic
    1. Discussion point 1
    2. Discussion point 2
  2. Top level topic ...

Meeting notes are sometimes posted as bullets under each discussion point, but they're often posted only as comments on the linked issues and pull requests.

Next agendas

If you are an active contributor you can add items here to be discussed in the next invite. If you are a new contributor, please make sure you have opened an issue or pull request. A member of the community will talk you through the expectations for the meeting.

Core Team Sync 2027-02-XX (15:00 UTC)

  1. https://github.com/valkey-io/valkey/issues/4276 - RFC to create Valkey-Samples project

Core Team Sync 2026-08-17 (15:00 UTC)

  1. Discuss WBL durability PR details and get final sign-off (for 9.2? or no): https://github.com/valkey-io/valkey/pull/3381

Core Team Sync 2026-08-10 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/pull/3708/changes - Let's a final review of this. We talked about it last week.
  2. https://github.com/valkey-io/valkey/issues/4261 - minor change to add EXEC to commandlog. Do we want this?
  3. https://github.com/valkey-io/valkey/issues/4276 - RFC to create Valkey-Samples project
  4. https://github.com/valkey-io/valkey/issues/4203 - Inconsistent behaviour for encodings
  5. https://github.com/valkey-io/valkey/issues/4373 - [NEW] Feature Request: Repo Taxonomy
  6. https://github.com/valkey-io/valkey/issues/4374 - [NEW] Feature Request: Probabilistic Modules

Core Team Sync 2026-08-03 (15:00 UTC)

  1. Discuss WBL durability PR details and get final sign-off (for 9.2? or no): https://github.com/valkey-io/valkey/pull/3381
  2. We will not hold the release for it, but if it get's reviewed and is safe in unstable as experimental we can merge it.
  3. https://github.com/valkey-io/valkey/pull/3212 - efficiency improvements for HFE of small hashes - discuss rdb version bump
  4. Still trending for 9.2. Prefer to avoid bumping the RDB version, but needs help reviewing.
  5. https://github.com/valkey-io/valkey/pull/4197 - A new metric primary_last_full_sync_duration_ms to track the most recent full sync duration
  6. Satheesha will follow up on providing more concrete use cases.
  7. https://github.com/valkey-io/valkey/pull/3721 - Should we backport on this.
  8. Yes, we should.

Core Team Sync 2026-07-27 (15:00 UTC)

  1. Discuss data tiering - https://github.com/dubey02/valkey-data-tiering/blob/unstable/design-docs/data-tiering/valkey-data-tiering-tsc-alignment.md
  2. https://github.com/valkey-io/valkey/issues/2392 - Discuss Atomic Slot Migration AUTH
  3. https://github.com/valkey-io/valkey/issues/3062 - Major decision on new repo for Lua 5.5 module
  4. https://github.com/valkey-io/valkey/pull/3940 - Nested prefetching for hash and zset inner hashtables and https://github.com/valkey-io/valkey/pull/3389 - Optimize multi key commands prefetching

Past meetings

Core Team Sync 2026-07-20 (15:00 UTC)

  1. Go over the plan for 9.2/10.0 https://github.com/valkey-io/valkey/issues/4218

Core Team Sync 2026-07-13 (15:00 UTC)

  1. https://github.com/valkey-io/valkey-doc/pull/454 - Forkless: created a centralized documentation page for forkless operations, covering all aspects delivered and in progress. Wanted to confirm this is the format and place we want for documenting the project.
  2. https://github.com/valkey-io/valkey/issues/3983 - Disabling default user results in silent data loss with AOF
  3. https://github.com/valkey-io/valkey/pull/3565 - AOF data integrity check followup

Core Team Sync 2026-07-05 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/pull/3986 - Do not count key misses for EXISTS command
  2. https://github.com/valkey-io/valkey/pull/3708 - lets close on top-keys analysis. the author addressed the PR comments and provided updated benchmark results
  3. https://github.com/valkey-io/valkey/pull/3911 - Can we get major decision on making lightweight VM_CallArgv API public?

Core Team Sync 2026-06-29 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/issues/4062 - Will propose a strategy for "Doing less with Less" and saying no more. Also will propose assigning a TSC for major decision shepherd.

Core Team Sync 2026-06-22 (15:00 UTC)

  1. @stockholmux proposal for a strategy of ownership areas to help encourage new folks.
  2. https://github.com/valkey-io/valkey/pull/3880 - per slot memory stats by @eifrah-aws

Core Team Sync 2026-06-15 (15:00 UTC)

  1. QoS based on Trusted Sources - https://github.com/valkey-io/valkey/issues/3927
  2. Steady-state replication throttle - https://github.com/valkey-io/valkey/issues/3963

Core Team Sync 2026-06-08 (15:00 UTC)

  1. Hot key observability HLD review - Lets agree on the interface, commands highlevel algorithem and limitaitons. - https://github.com/valkey-io/valkey/pull/3708
  2. CLUSTER SHARDS compatibility issue - https://github.com/valkey-io/valkey/issues/3909
  3. DB-level ACL breaking ACL LIST compatibility - https://github.com/valkey-io/valkey/issues/3915
  4. A/A design discussion - https://github.com/valkey-io/valkey/issues/512

Core Team Sync 2026-06-01 (15:00 UTC)

  1. Inline compression - https://github.com/valkey-io/valkey/issues/3423
  2. ACL Group. https://github.com/valkey-io/valkey/issues/3726
  3. Fix cluster AUX-field control-character and delimiter injection #3848 - backport or not?

Core Team Sync 2026-05-25 (15:00 UTC)

  1. Allow to restrict user authentication to external authentication module https://github.com/valkey-io/valkey/issues/2203
  2. https://github.com/valkey-io/valkey/issues/2203#issuecomment-4535460112

Core Team Sync 2026-05-18 (15:00 UTC)

  1. Valkey 9.1 go/no-go: https://github.com/orgs/valkey-io/projects/41/views/1

Core Team Sync 2026-05-11 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/issues/3403 - Support dual certificates (PQC and RSA)
  2. https://github.com/valkey-io/valkey/pull/3646 - major decision, change default config value for commandlog to gain performance back.
  3. https://github.com/valkey-io/valkey/issues/3429. [BUG] Stream commands missing signalModifiedKey calls

Core Team Sync 2026-05-04 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/pull/3565 - major decision pending

Core Team Sync 2026-04-27 (15:00 UTC)

  1. https://github.com/valkey-io/valkey/issues/2991 - Can we major-decision approve the opt-in solution to MOVE keyless readonly commands?
  2. https://github.com/valkey-io/valkey/pull/3522 - major decision pending

Core Team Sync 2026-04-20 (15:00 UTC)

  1. Configuration to retain encodings during RDB reload - https://github.com/valkey-io/valkey/issues/3479
    1. We'll add the config.
  2. Modernizing Valkey AOF - https://github.com/valkey-io/valkey/issues/3515
    1. High level alignment, next step will be followup items.
  3. Patch fixes for well long existing syntax bugs - https://github.com/valkey-io/valkey/issues/3483, should we break it or define it?
    1. Unclear what the specific steps are here, we didn't really get much broad alignment on the issue.

Core team sync 2026-04-13 (15:00 UTC)

  1. Persist cluster config in BIO - https://github.com/valkey-io/valkey/pull/2555
    1. Madelyn and Jacob are supposed to review this, and then follow up.
  2. Add support for CONFIG INFO to display config type and valid values - https://github.com/valkey-io/valkey/pull/3050
    1. Major decision deferred because of lack of quorum, but will be auto approved.
  3. New revision of module command result callback API: https://github.com/valkey-io/valkey/pull/2936
    1. Made decisions to try to get this in to rc2.
  4. Automatically detect test failures from daily CI runs: https://github.com/valkey-io/valkey/pull/3358
    1. Decision was to go for it. Not technically a major decision, so we'll merge it.
  5. Optimize multi key commands using sliding window prefetching https://github.com/valkey-io/valkey/pull/3389
    1. Generally looks good, just need to refine and merge.

Core team sync 2026-04-06 (15:00 UTC)

  1. New revision of module command result callback API: https://github.com/valkey-io/valkey/pull/2936
    1. The API still seems reasonable at a high level, but still questions about the specifics.

Core team sync 2026-03-30 (15:00 UTC)

  1. 9.1/unstable status (TL;DR many failed tests - https://github.com/valkey-io/valkey/actions/runs/23722657826)
    1. Reviewed the status. Key PRs to merge are the queue improvements.
  2. Discuss Valkey-Skills repo: https://github.com/avifenesh/valkey-skills/
    1. Follow up with Avi about: 1) What is the governance structure. 2) What are the specific end users that we are targeting 3) What specific initial recommendations should we be doing.

Core team sync 2026-03-23 (15:00 UTC)

  1. Discuss analysis of perf regression introduced by #2516 (removes pointer overhead, saves 20–30% memory for embstr): https://github.com/Nikhil-Manglore/valkey/blob/analysis/PR2516_Analysis.md Questions: Do we keep the tradeoff? Do we want to raise embstr threshold, take tradeoff for larger size range?
    1. We will accept the perf degradation for the embedded strings memory improvement.
    2. @Nikhil-Manglore will do performance testing to make sure increasing the embedded string limit 128 bytes.
  2. Discuss LuaJIT module (up to 80% faster than default Lua module, 0 patches to LuaJIT):
    1. https://github.com/valkey-io/valkey/issues/1229#issuecomment-4067466902
    2. https://github.com/secwall/valkey-luajit
  3. Discuss static linking of default LUA module (https://github.com/valkey-io/valkey/pull/3392)
  4. Any issues with https://github.com/valkey-io/valkey/pull/2823 for benchmark?

Core team sync 2026-03-16 (15:00 UTC)

  1. (Highest priority) Valkey 9.1 RC floating items
    1. Do we wait on https://github.com/valkey-io/valkey/pull/3324 or just do it? (Madelyn thinks we should do iot)
  2. Discuss proposals for Data Tiering
    1. https://github.com/valkey-io/valkey/pull/3296 (RFC #26)
    2. https://github.com/valkey-io/valkey/issues/3326
  3. https://github.com/valkey-io/valkey/pull/1032#discussion_r2660129652
  4. Participants; how do we accept more companies who support Valkey?

Core team sync 2026-03-09 (15:00 UTC)

  1. Closing Valkey 9.1 discussions
    1. Valkey 9.1-rc1 should go out this week! Kyle will write an RC blog.
  2. https://github.com/valkey-io/valkey/pull/866
    1. Let's try to get this merged in for 9.1 as well. Will close on it offline.
  3. Replace fast_float with ffc.h (plain C, PR by Daniel Lemire): https://github.com/valkey-io/valkey/pull/3329
    1. Yes, let's bring it in for 9.1 if we can merge it in the next few days.

Core team sync 2026-03-02 (16:00 UTC)

  1. Remind people that the meeting will shift by an hour if you aren't in the US/Canada.
  2. Discuss ZSET refactor (skiplist replacement): https://github.com/valkey-io/valkey/issues/3166
  3. Discuss valkey-sink module: https://github.com/valkey-io/valkey/issues/3290

Core team sync 2026-02-23 (16:00 UTC)

  1. Discuss this PR which seems to be dangling: https://github.com/valkey-io/valkey/pull/2846
    1. We will merge it for 9.0
  2. Discuss Replication compression: https://github.com/valkey-io/valkey/issues/3195
    1. We are good to move forward. Sarthak will open a PR.

Core team sync 2026-02-16 (16:00 UTC)

  1. Fast approval cycle on: https://github.com/valkey-io/valkey/pull/3217
    1. We were in fact not fast. But have consensus.
  2. Re-evaluate the migration C++ unit tests.
  3. Discuss refactor of RFC process https://github.com/valkey-io/valkey/issues/3172

Core team sync 2026-02-09 (16:00 UTC)

  1. Adds new ValkeyModule_CallArgv API function https://github.com/valkey-io/valkey/pull/3122
    • The new API seems good. We will continue to watch the performance numbers and make a later decision.
  2. https://github.com/valkey-io/valkey/pull/3091 - We suggest to add an info field to count hashes removed during load when all their fields expired.
    • Only a log is sufficient. No info field.
  3. Discuss major decision around cluster scan - https://github.com/valkey-io/valkey/pull/2934
    • Approval given but with some refactoring suggested in the versioning scheme.
  4. https://github.com/valkey-io/valkey-rfc/pull/34 - kickstart on top key analysis high level specifications
    • Monitor performance results in Valkey admin (If needed)

Core team sync 2026-02-02 (16:00 UTC)

  1. Patch releases. What's the plan?
    1. Ran will open an issue for automatically doing performance.
    2. Viktor will do the the patch release 9.0 tomorrow. Anything else will go with the security release happening later.
  2. New MSETEX command allows to set an expiration time with MSET https://github.com/valkey-io/valkey/pull/3121
    1. Approved, we will continue to support APIs as they are requested.
  3. Adds new ValkeyModule_CallArgv API function https://github.com/valkey-io/valkey/pull/3122
    1. Pushing discussion to next week, as we are missing Ricardo.
  4. Add remaining_repl_size field in CLUSTER MIGRATESLOTS output: https://github.com/valkey-io/valkey/pull/3135
    1. Approved.
    2. Also approved related PR: https://github.com/valkey-io/valkey/pull/2924
  5. Redesign IO threading communication PR: https://github.com/valkey-io/valkey/pull/2909
    1. Came up with some guidance on the major decision parts. Will ping the core team as well since they weren't @'d
  6. Add server side TLS certificate expiry tracking and INFO telemetry #2913
    1. Moved to approve since we have more of a quorum now.

Core team sync 2026-01-26 (16:00 UTC)

  1. Module API: command result callback (AKA monitor API): https://github.com/valkey-io/valkey/pull/2936
  2. Track request payload distribution in INFO stats: https://github.com/valkey-io/valkey/pull/3106
  3. Add support for CONFIG HELP to display config type and valid values https://github.com/valkey-io/valkey/pull/3050

Core team sync 2026-01-19 (16:00 UTC)

  1. Discuss RESPB https://github.com/valkey-io/valkey/issues/2992
  2. Decision about TLS module and Lua and Module. We should decide to deprecate TLS. Static building all of the modules. Also the performance degradation from https://github.com/valkey-io/valkey/issues/3031#issuecomment-3730677903.
  3. Add used_memory_overhead_human and used_memory_dataset_human info fields https://github.com/valkey-io/valkey/pull/2971
  4. Backport HFE bug fixes: https://github.com/valkey-io/valkey/pull/3060 https://github.com/valkey-io/valkey/pull/3001

Core team sync 2026-01-12 (16:00 UTC)

  1. Review https://github.com/valkey-io/valkey/pull/2943 explicit includes of fmacros.h
    • JimB123: Can open a PR with a different approach.
  2. There's at least 3 PRs for TLS cert reload, which one to support or none at all?
    1. Issue https://github.com/valkey-io/valkey/issues/2649
    2. https://github.com/valkey-io/valkey/pull/1870
    3. https://github.com/valkey-io/valkey/pull/2650
    4. https://github.com/valkey-io/valkey/pull/3020 👈 (This one looks close)
    • Major decision approved, need to finalize the PR and merge it.
  3. Try again to make a decision about CPU utilization metric when I/O threads are used and threads to busy-looping:
    • Major decision approved with some requests.
  4. Copy-avoidance bugs and performance issue
  5. Makes CLUSTER KEYSLOT available in standalone mode
    • Done!

Core team sync 2026-01-05 (16:00 UTC)

  1. Lets re-discuss strategy regarding empty sets
    1. https://github.com/valkey-io/valkey/issues/68
    2. https://github.com/valkey-io/valkey/pull/2972
    3. https://github.com/valkey-io/valkey/issues/2977
  2. @JimB123 wants to discuss using gtest again https://github.com/valkey-io/valkey/pull/2956
    • Major decision approved
  3. Discussing READONLY keyless commands on non-readonly replicas
    1. https://github.com/valkey-io/valkey/issues/2991
    2. https://github.com/valkey-io/valkey/issues/2991#issuecomment-3711431045
    • Decision was that Yana was going to come up with a more concrete proposal.

Clone this wiki locally