Skip to content

Weekly meeting

Jump to bottom Edit New page
Wen Hui edited this page Nov 17, 2025 · 233 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 agenda

If you are an active contributor and on the invite, you can add items here to be discussed in the next invite.

Core team sync 2025-11-24 (16:00 UTC)

  1. Implement bigkey real time scan feature - https://github.com/valkey-io/valkey/pull/2819
    1. Built-in function in Valkey core OR
    2. Implement it as a seperated module? Extend: same design as calculation memory per key? https://github.com/valkey-io/valkey/issues/2850
  2. Adds HGETDEL Support to Valkey https://github.com/valkey-io/valkey/pull/2851
  3. Save cluster file in bio to avoid the stuck io latency https://github.com/valkey-io/valkey/pull/2555 -- any concern for this?
  4. To demo the initial GLIDE documentation site, discuss its structure, and gather feedback before the public preview.

Past meetings

Core team sync 2025-11-17 (16:00 UTC)

  1. Database level access control https://github.com/valkey-io/valkey/pull/2309

Core team sync 2025-11-10 (16:00 UTC)

  1. Topics?

Core team sync 2025-11-03 (16:00 UTC)

  1. Discuss the various open-replication improvements - https://github.com/valkey-io/valkey/issues/2767, https://github.com/valkey-io/valkey/pull/2470 (Was an intern, maybe we takeover the PR), TBD Forkless improvement.
  2. Related to https://github.com/valkey-io/valkey/pull/2470 - probably need information about base.rdb load improvements, BGREWRITEAOF, server start/stop with AOF.
  3. Valkey UI official support - https://github.com/valkey-io/valkey-rfc/pull/31
    • Looks OK. We will cleanup and merge the RFC and then once the code is in "mini-GA" state we will merge it.
  4. Valkey 9.0.1
    • Release in next weeks.

Core team sync 2025-10-27 (14:00 UTC)

  1. Adding support for shared memory - https://github.com/valkey-io/valkey/pull/2472
    1. (Major decision) Review the API - Approved
    2. Concerns about code intrusiveness - Have @JimB123 given a second review of the code.
  2. Make commandlog-request-larger-than and commandlog-reply-larger-than become memory config https://github.com/valkey-io/valkey/pull/2648
    1. (Major decision) Allow Memory configs to support negative values, this was previously not used. - Approved
  3. Add ValkeyModule_ACLCheckCommandPermissionsForCurrentUser API https://github.com/valkey-io/valkey/pull/2690
    1. (Major decision) Add new APIs - Decision was to switch to a draft, as this was not needed.
  4. Review database level ACLs - https://github.com/valkey-io/valkey/pull/2309
    1. (Major decision) Decide on the new syntax db=1,2,3 vs db+=123 etc
      1. No concrete decision about the syntax, we provide some guidance for continuing investigation. @hpatro will follow up.
  5. Initial discussion about various full sync replication improvement.
    1. Initial discussion, will progress further next week.

Core team sync 2025-10-20 (14:00 UTC)

  1. Adding merge queue to unstable branch

Core team sync 2025-10-13 (14:00 UTC)

  1. House Keeping items
    • Any concern with delaying 9.0 until 10/16 or 10/21? The LF would like to do some marketing.
    • Decision is 10/21.
  2. Bug fix for 9.0 that includes breaking changes to the module API: https://github.com/valkey-io/valkey/pull/1826
  3. Bug fix for 9.0, https://github.com/valkey-io/valkey/pull/685/files
    • Let's try to get it merged for 9.0
  4. Valkey 9.1 decision making process.
  5. Forkless replication - https://github.com/valkey-io/valkey/issues/1754#issuecomment-3392487797
    • Review high level design and highlight and potential concerns
  6. Enable dual channel replication - https://github.com/valkey-io/valkey/issues/2083
    • We punting this to 10.0

Core team sync 2025-10-06 (14:00 UTC)

  1. For 9.0:
  2. Decision to use the +2 model for all major decision
    • Vote
      • Approved by majority of TSC (including votes given outside of the meeting)
    • Need to update the governance doc (who?)

Core team sync 2025-09-29 (14:00 UTC)

  1. Add slot migration client flags and module context flags #2639 (Needed for 9.0.0-rc3)
  2. Fix incorrect lag and entries-read value with tombstone #685
  3. Notice: New repo valkey-operator created. There is an RFC.
  4. Check the PRs with 'major-decision-pending'. (Should we use a label like 'major-decision-postponed' on PRs we already discussed and don't want to discuss again right now?)
  5. Change to a softer major decision model, to avoid decisions being blocked by TSC members passively not giving their votes/approvals.
    • No quorum during meeting, but async decision after the meeting to use +2

meeting extracts:

  1. Jacob will drive RC3. We target early as possible (by 2nd oct)
  2. Start back porting fixes to older versions. @ranshid - will focus on 8.1

Core team sync 2025-09-22 (14:00 UTC)

  1. Follow up on - Fixed blocking behavior (https://github.com/valkey-io/valkey/pull/2329)
  2. Discussion about SCANDEL = SCAN + delete https://github.com/valkey-io/valkey/issues/2623
  3. Discussion about the 9.0 release.
    • Decision to release RC2 ASAP
    • We will make an RC3 with the required ASM follow-ups such as hiding ongoing ASM on replicas.

Core team sync 2025-09-15 (14:00 UTC)

  1. Discussion about helm charts! https://github.com/valkey-io/valkey/issues/2371

Core team sync 2025-09-08 (14:00 UTC)

  1. RC2 release review
    1. https://github.com/orgs/valkey-io/projects/18/views/1
  2. Review the helm chart issue with bitnami. https://github.com/valkey-io/valkey/issues/2371
  3. blocking clients should return -MOVED and -REDIRECT correctly #2329

Core team sync 2025-09-01 (14:00 UTC)

Core team sync 2025-08-25 (14:00 UTC)

  1. Add cluster-announce-client-(port|tls-port) configs #2429
    • Approved
  2. Relaxed RDB check for foreign RDB formats (such as the ones from Redis 7.4 and Redis 8) #2543
    • Approved
  3. Separate RDB snapshotting from atomic slot migration #2533
    • A few new INFO fields to approve
      • Consensus to add these fields, but there are concerns about the chosen INFO sections and exact names for these fields. Suggestions to be posted as comments in the PR.
  4. Reset cluster related stats in CONFIG RESETSTATS #2458
    • Approved
  5. New module API event for tracking authentication attempts #2237
    • new module API event ValkeyModuleEvent_AuthenticationAttempt
      • Approved
  6. Un-deprecated many deprecated commands. Issue #2459, PR #2546.
    • Approved

Core team sync 2025-08-18 (14:00 UTC)

  1. Optimize pipelining by parsing and prefetching multiple commands #2092
    • Performance regression for pipelining observed in 8.0 (0.63MRPS), 8.1 (0.65MRPS) and unstable (0.75MRSP) compared to 7.2 (0.949MRPS). Benchmarked by @JoBeR007 here.
      • Benchmark result possibly not accurate, due to how CPU cores were pinned.
    • This PR roughly doubles the RPS for pipelined commands, with and without I/O threads.
    • Compensation for not accepting cross-slot MGET.
      • Blocker for this PR is just a code review. To be reviewed and merged ASAP.
  2. Stability issues (crashes) in 8.1 still not solved:
    • [CRASH] Crash during downgrade from Valkey 8.1.0 to Valkey 8.0.3 #2341
    • [CRASH] Crash during upgrade from Valkey 8.1.0-ga to Valkey 8.1.0-ga #2093
    • [CRASH] Unexpected crash after the FULL SYNC #2114
    • [BUG] Unsuccessful (extremely high number) of attempts to perform Partial resynchronization causing CPU/Memory spikes #2119 Fixed in #2490
      • Crashes observed only once or a few times and can't be reproduced are very hard to debug and fix.
      • If it's a replica crashing, it's less severed than if it's a primary crashing.
  3. Backporting of fixes to 8.0 postponed indefinitely due to flaky tests?
    • 8.0.4 was released with only some CVE fix, but without 15 PRs backported in #2210.
      • From now on, we will backport not only bug fixes but also fixes to flaky tests and and similar testing related fixes to be sure that the tests are passing for the patch releases.
      • Viktor will finish the 8.0.5 release within the following days.
      • Test failures on the 8.0 branch resolved by backporting additional commits to the 8.0 branch.
  4. Unit testing framework #2492
    • Discussion about whether mocking is good or bad. No conclusion.
  5. Command to SCAN + Delete keys #2501
    • Discussion. No conclusion.
  6. Allow Read requests on IO/Threading #2022
    • Presentation of the high level design ideas by Dan.
      • In general positive response.
      • Discussion and clarification about how the amount of write commands affects the speed of read commands.
      • Some concern about added complexity. Doesn't appear to be a blocker.
      • Request for ideas about how to expand this to standalone (non-cluster) mode.

Core team sync 2025-08-11 (14:00 UTC)

  1. Allow dynamic modification of databases num if the db is not been used 2385
  2. Full text search functionality (https://github.com/valkey-io/valkey-rfc/pull/24)

Core team sync 2025-08-04 (14:00 UTC)

  1. Valkey 9.0 Project status: (https://github.com/orgs/valkey-io/projects/18)
    1. Atomic slot migration. We're close, but there are still some open comments: https://github.com/valkey-io/valkey/pull/1949
  2. Cluster Bus Network In/Out: (https://github.com/valkey-io/valkey/issues/1929)
  3. Discuss Valkey Search RFC (https://github.com/valkey-io/valkey-rfc/pull/24)

Core team sync 2025-07-28 (14:00 UTC)

  1. Valkey 9.0 Project status: https://github.com/orgs/valkey-io/projects/18
    1. HFE and atomic slot migration making progress.
  2. Discuss the negative filtering format for client command filters, issue 1936
    1. Use NOT-* syntax. Conditionally approved from meeting
  3. Analytics on valkey.io via LF standard format
    1. Notified

Core team sync 2025-07-21 (14:00 UTC)

Nothing?

Core team sync 2025-07-21 (14:00 UTC)

  1. Discuss demos/samples repo as proposed on the issue 2272
    1. Core team meeting. Directionally aligned, @PingXie will take a look at the proposal offline.
  2. Discuss Database-level access control 2309
    1. https://github.com/valkey-io/valkey/pull/2309#issuecomment-3069915410
  3. Change configs for "Auto-failover on shutdown" (not yet released) to match other shutdown options #2292
    1. I think we discussed this last week, might have forgotten to copy it.

Core team sync 2025-07-07 (14:00 UTC)

  1. Discuss Read offloading
    1. Offloading for pipelining. There is some amount of technical debt that is getting introduced. Let's talk about it.
    2. Related to https://github.com/valkey-io/valkey/pull/2208
    3. See notes here: https://github.com/valkey-io/valkey/issues/2022#issuecomment-3045492704
  2. Introduce HASH items expiration #2089 to discuss HEXPIRE etc writable command flag "DENYOOM"
    1. @Madelyn will back channel and ask Oran if we can change the hexpire event.
    2. Only HSETEX will be marked as a write command.
  3. Discuss client support for Swift language with authors.
    1. @Madelyn will add http://github.com/adam-fowler and http://github.com/fabianfett to the org. (DONE)

Core team sync 2025-06-30 (14:00 UTC)

  1. Review Valkey 9 board decide code freeze.
    1. Code freeze at end of July? (Target July 29th)
    2. Required features for the launch
      1. Atomic slot migration (changes needed to make it source driven)
        1. Simplify to 1 shot for code freeze. (One week, will re-request review)
        2. Doesn't need help, will do other work after code freeze.
      2. Hash field expiration (We have a later discussion for this)
        1. (See below) We need another person on reviewing this. (Ricardo will take a look)
    3. Like to have features
      1. Memory sharing for VSS (Check with Yair about https://github.com/valkey-io/valkey/pull/1804)
      2. Read offloading: We should schedule a major discussion about it (Next week?)
      3. Prefetching and pipelining optimizations: Viktor is a bit busy, maybe we can free him up?
    4. Potential gaps we should be testing
      1. Testing multi-database clients.
      2. Does by-polygon have client support.
  2. HFE status:
  3. Moving more towards lazy consensus https://www.apache.org/foundation/voting.html#LazyConsensus as opposed to the full consensus we get today. https://github.com/valkey-io/valkey/blob/unstable/GOVERNANCE.md#voting
    1. Maybe make a proposal on the governance, then leave it and commit it for after 9.0.
  4. For 7.2 and 8.0, we will release them with the new CVEs as is. We'll follow up and try to figure out how to reduce the test flakiness.

Core team sync 2025-06-23 (14:00 UTC)

  1. Improve CLUSTER FLUSHSLOT routing and propagation https://github.com/valkey-io/valkey/pull/2167
    1. Didn't have quorum, need a separate vote.

Core team sync 2025-06-16 (14:00 UTC)

  1. Valkey + modules named as valkey-extensions or better descriptive name. Valkey-bundle vs valkey-extended.
    1. Valkey-bundle is preferred name
  2. Slot-level memory metrics performance test result discussion #2128
  3. Add SAFE option to SHUTDOWN to reject shutdown in unsafe situations #2195
  4. Remove the 500ms fixed delay for automatic failover for faster failover #2209

Core team sync 2025-06-09 (14:00 UTC)

What did we talk about?

Core team sync 2025-06-02 (14:00 UTC)

  1. Add CLUSTER FLUSHSLOT command revisit #1384
    1. We will merge this as is, we can amend to it later without making any breaking change.
    2. Kyle will create an issue on the docs to make it clearer about how databases are kind of a node level construct.
  2. Hash field expirations (If we are really up to it) #2089
    1. Ran will continue with his work.
  3. Add support for automatic client authentication via TLS certificate fields #1920
    1. We will go with an enum.

Core team sync 2025-05-26 (14:00 UTC)

  1. Automated performance benchmarking #2073
  2. Adding KEYINFO command to find out keys that have large number of elements#1151
  3. Slot-level memory metrics POC #2128
  4. Prevent multiple LUA debug sessions #2112

Core team sync 2025-05-19 (14:00 UTC)

  1. ValkeyLDAP module https://github.com/rjd15372/valkey-ldap - discuss the repository move under valkey-io org.
    1. Should probably use a thread pool instead of creating a new thread per request.
    2. Should maintain persistent connections for the LDAP work.
    3. Module distribution story?
    4. Ricardo will move the repository. Decision is that we will leave the module as valkey-ldap.
  2. Save to Disk in Bio Thread #1784 PR: https://github.com/valkey-io/valkey/pull/1784
    1. Looks good. Don't implement a config.
  3. Consider change default of dual-channel-replication-enabled to "yes"#2083
    1. We will review this again right before the 9.0 merge. Added the 9.0 project tag.
  4. [NEW] Introducing an independent admin thread #1893
    1. Reviewed the high level architecture. Next step is to implement the interrupt code.

Core team sync 2025-05-12 (14:00 UTC)

  1. Replication Flow Control – Prioritizing replication traffic in the replica #1838
    1. Decision was not to use a config
  2. RDB Compression through LZ4, Batching and Dictionary #1962
    1. Decision was to move forward with implementation. Some thoughts left on the issue.
  3. Think again: CLUSTER FLUSHSLOT (#1133, #1384) name is too similar to existing command CLUSTER FLUSHSLOTS
    1. Leave the name as is.

Core team sync 2025-05-05 (14:00 UTC)

  1. Adding KEYINFO command to find out keys that have large number of elements #1151
  2. DELIFEQ https://github.com/valkey-io/valkey/pull/1975
    • Postponed from last week
      • Command accepted
  3. INCR arguments EX, PX, NX, XX https://github.com/valkey-io/valkey/issues/1818
    • Postponed from last week
      • Meeting in favor but meeting didn't have quorum at this point.
  4. Auth client using TLS client certificate's common name

Core team sync 2025-04-28 (14:00 UTC)

  1. Add framework for cross-slot commands, enable for MGET
  2. Mark primary node as alive immediately if reachable and failover is not possible
  3. Info Keysizes section
  4. Add GETPXT, MGETPXT (Get with millisecond expiration) commands Candidate
    • No decision.
  5. DELIFEQ https://github.com/valkey-io/valkey/pull/1975
    • No time to discuss. Postponed.
  6. INCR arguments EX, PX, NX, XX https://github.com/valkey-io/valkey/issues/1818
    • No time to discuss. Postponed.

Core team sync 2025-04-21 (14:00 UTC)

  1. Support BYPOLYGON option for GEOSEARCH #1755

    1. Any concerns with this feature or can it move forward to implementation?
      1. The API looks correct, seems better than the approach of having an index.
    2. Are there any concerns related to polygon validation such as overlap?
      1. Add tests for overlapping polygons, validating a polygon around the equator, spanning hemispheres, make sure it's not looping anywhere.
    3. Should we support points on the edge?
      1. Check the implementation of by box and by radius.

  2. Valkey Test Framework

    1. See notes here: https://github.com/valkey-io/valkey-rfc/pull/17#issuecomment-2818791136.
    2. Moving forward with modules fo rnow.

Core team sync 2025-04-14 (14:00 UTC)

  1. Introducing an independent admin thread (https://github.com/valkey-io/valkey/issues/1893)
    1. Wen will followup to collect more information
  2. [Client Introspection] Client Commands Extended Filtering (https://github.com/valkey-io/valkey/pull/1466)
    1. This seems already approved, so will skip it unless there is something else we want to discuss
  3. Add sentinel_total_tilt to sentinel INFO sentinel (https://github.com/valkey-io/valkey/pull/1904)
    1. Approved
  4. Add node pfail and fail count to cluster info metrics (https://github.com/valkey-io/valkey/pull/1910)
    1. Approved
  5. Fixed CROSSSLOT ERROR in Cluster Mode for PUBSUB SHARDNUMSUB #1369
    1. Will have a vote for whether or not breaking change is worth it.
  6. Introduce MPTCP #1811
    1. Approved

Core team sync 2025-04-07 (14:00 UTC)

  1. Bugs and plan for 8.1.1
    1. https://github.com/valkey-io/valkey/pull/1819
      • Yes, it will be included
    2. Anything else? Check project 8.1 "To be backported"
      • Any patches that have already been merged or are soon ready to merge will be included.
  2. 8.0.3?
    1. Project 8.0 "To be backported"
  3. 7.2.x?
    1. Project 7.2 "To be backported"
  4. Major decisions for 9.0:
    1. #1091 Trigger manual failover on SIGTERM / shutdown to cluster primary (Viktor's suggestion)
      • Approved
    2. #1811 Introduce MPTCP (Viktor's suggestion)
      • Conceptually approved. Only minor things like config naming were raised and we should comment about it in the PR.
    3. #653 Revise config defaults for Valkey 8 (Wen's suggestion)
      • We changed some defaults in 8.0. We should close this issue and create new issues for 9.0 for the defaults that are still suggested to change.
      • For the listpack sizes, we deferred the decision to wait for the new hashtable to be introduced. Now, we can do some benchmarking and come up with new defaults.
    4. #707 Allow multi-slot MGET in Cluster Mode (Wen's suggestion)
      • Last week's decision is that Ping will open a PR with an alternative approach.
    5. #1840 Enable client eviction by default, set maxmemory-clients too 100% by default (Wen's suggestion)
      • The majority seems to prefer to keep it disabled by default. No formal decision.
  5. Other
    1. Follow up on #23 [NEW] Atomic slot migration HLD (Wen's suggestion)
      • Follow up from last week if Jacob has more information
      • We will create a feature branch under the valkey repo.
    2. Discussion around Python test framework. Should we adopt it more widely.

Core team sync 2025-03-31 (14:00 UTC All zones)

  1. Way of working
    1. Backporting changes to older version/branch - Create development guide #1558, comment
    2. How to prioritize better?
      • Concern that e.g. Atomic slot migration is delayed due to less important changes that take our time (discussions, decisions, reviews).
  2. Prioritize among the 17 PRs and 24 issues that need a decision, without discussing each one in detail.
    1. PRs: major-decision-pending
    2. Issues: major-decision-pending
  3. Make decisions about individual PRs and issues:
    1. Enhance valkey-benchmark with Multi-Language Support and Advanced Testing Capabilities (not a major decision?)

Core team sync 2025-03-24 (14:00 UTC All zones)

  1. 8.1 GA build to be released on 3/31. [@ranshid]
    • Tag the documentation repository at the same time.
    • Author the release blog post.
  2. Feature blogs:
    • New hashtable. [@zuiderkwast]
  3. Pre-release of a bundled container image with the official modules in early April. [@hpatro]
  4. Fully automated container image release process for all modules by June. [@hpatro]
  5. Man pages for all modules to be completed by June. [module maintainers]
  6. Fix for the engine crash on module client blocking during keyspace events to be released as part of 8.1.1.

Core team sync 2025-03-17 (14:00 UTC All zones)

  1. Cluster with multiple databases - issue #1671, PR #1319
    1. Decided to use a new config cluster-databases for the number of databases in cluster mode. Default 1. The existing databases config is not used in cluster mode.
    2. We stop rewriting databases to 1 on CONFIG REWRITE when cluster is enabled.
  2. Lazy memory initialization for databases https://github.com/valkey-io/valkey/pull/1609
  3. Cluster topology HASH https://github.com/valkey-io/valkey/issues/1814
    1. We should come up with a more comprehensive plan: https://github.com/valkey-io/valkey/issues/1814#issuecomment-2729968634

Core team sync 2025-03-10 (15:00 UTC All zones)

  1. Ask for Valkey 8.1 - https://github.com/valkey-io/valkey/pull/1819
    1. Not sure if this API is correct, Jacob will follow up.
  2. More refined memory management system - https://github.com/valkey-io/valkey/issues/1792
    1. Directionally aligned on extending the existing functionality.
  3. Add last_fork_start_time to INFO STATS - https://github.com/valkey-io/valkey/pull/978
    1. Punting to Valkey 9.0
  4. Introduce cluster-ignore-disk-write-errors to prevent the process from existing when saving fails https://github.com/valkey-io/valkey/pull/1032
    1. Punting to Valkey 9.0
  5. Decide on CLUSTER REPLICATE NO-ONE vs CLUSTER REPLICATE NO ONE: https://github.com/valkey-io/valkey/pull/1674
    1. Decided on CLUSTER REPLICATE NO ONE.

Core team sync 2025-03-03 (15:00 UTC All zones)

  1. Module versioning and bundling strategy - https://github.com/valkey-io/valkey/issues/408
    1. Discussed an update here: https://github.com/valkey-io/valkey/issues/408#issuecomment-2694855407
  2. Introduce a new API for shared memory for VSS - https://github.com/valkey-io/valkey/pull/1804/files
  3. Valkey 8.1 launch time frame (do we want to launch during kubecon?)
    1. CNCF is part of the Linux foundation, which hosts kubecon.

Core team sync 2025-02-24 (15:00 UTC All zones)

  • Finalize server config cluster-manual-failover-timeout min/max value https://github.com/valkey-io/valkey/pull/1690.
    • Very high failover timeout could cause write unavailability, so might be beneficial to add a cancel command. However, it's premature to build it without anyone needing it. Hence, decided against it.
  • Possibly a breaking change for some clients depending on the output so it shouldn't be included in 8.1 https://github.com/valkey-io/valkey/pull/1559
  • Discussed RC2 - Stabilization of test failures in progress. No new major features are getting built in. 3 weeks cadence of RC release can be followed.

Core team sync 2025-02-17 (15:00 UTC All zones)

Core team sync 2025-02-10 (15:00 UTC All zones)

  1. Discuss the naming issue for PR https://github.com/valkey-io/valkey/pull/831
  2. New item for RC1? https://github.com/valkey-io/valkey/pull/1698 Show capa in client list
  3. RC1 release content:

Core team sync 2025-02-03 (15:00 UTC All zones)

  1. Which features can make it to the 8.1.0-rc1.
    • Various discussion about the release.
  2. Release candidate version numbering.
    • Whether to revise the decision to use 8.1 rather than 8.2, https://github.com/valkey-io/valkey/issues/1650
      • Decision to stick to 8.1
    • Which version to use for release candidates e.g. in the INFO and HELLO fields. Options: 8.0.240, 8.1.0 (same as GA), 8.1.0-rc1.
      • Discussion of pros and cons of each option.
      • Decision(?) to use the GA version 8.1.0 identical for all release candidates and for the GA release.
      • Idea raised about introducing an INFO field to identify that the server is running a release candidate.

Core team sync 2025-01-27 (15:00 UTC All zones)

  1. Scripting engine modulization (Ricardo)
    1. Allows users to replace builtin Lua with LuaJit, Lua 5.3, etc.
    2. Convert builtin Lua to module? (how and why) (issue #1627)
      1. We decided to postpone this to after 8.1.
    3. How to disable the builtin Lua: Just unload the module? (issue #1204)
    4. Current state: Module API for defining scripting engines already merged (PR #1277), but needs some more API changes for EVAL and for being able to completely provide a Lua engine using module API.
    5. Multiple Lua can co-exist in modules if we just change the call to dlopen() in module.c to use the RTLD_DEEPBIND flag. Safe to change?
      1. We decided that we want a separate pull request for this change.
  2. Decisions we have to make before RC1. What to prioritize?
    1. Rolling downgrade, forward compatibility https://github.com/valkey-io/valkey/issues/1108 (Vote)
      1. Approved the PR "Relaxed RDB version check" https://github.com/valkey-io/valkey/pull/1604
    2. Add key-eviction-memory parameter for evicting key earlier to avoid OOM https://github.com/valkey-io/valkey/pull/831
      1. No consensus about config name and semantics. Discussion continues on the PR.
    3. Add paused_reason to INFO CLIENTS https://github.com/valkey-io/valkey/pull/1564
      1. Please approve or comment on the PR.
    4. Extend LATENCY LATEST to add min / sum / cnt stats https://github.com/valkey-io/valkey/pull/1570
      1. The usefulness of the min field is questioned. Maybe we can skip that one and keep the other fields. Comment on the PR.
    5. Add new SCRIPT STATS subcommand https://github.com/valkey-io/valkey/pull/1418
      1. The usefulness of this command is questioned, and whether stats for scripts and functions should be covered by the same commands. Ricardo will think about the usefulness of this command while working on scripting engine modularization.
    6. Reply Offload yes/no https://github.com/valkey-io/valkey/pull/1457
      1. Concerns about the complexity of the optimization and whether the performance improvement is large enough to justify the complexity.
      2. Suggestion to open separate PR with a simpler approach, which would only avoid copying large strings (e.g. more than one page size) to the reply buffer, and would not be limited to IO threads. It is likely less performant, but can be achieved with a smaller change and less complexity. Ideas to be posted on the PR.
  3. discuss generally our stance regarding minor code improvements / refactoring / syntactic sugar changes.
      1. We discussed. No consensus about general stance. Changes that are objectively to the better (correcting typos) are more often accepted than changes that are more about personal preferences. Git blame is used extensively by some of us, so there's benefit in avoiding changes.

Core team sync 2025-01-20 (15:00 UTC All zones)

Core team sync 2025-01-13 (15:00 UTC All zones)

Core team sync 2025-01-06

Add a custom footer
Add a custom sidebar

Clone this wiki locally