Skip to content

fix:SETEX replication does not work#3133

Merged
Mixficsol merged 1 commit intoOpenAtomFoundation:unstablefrom
YuCai18:hotfixuns/fix_setex
Jul 22, 2025
Merged

fix:SETEX replication does not work#3133
Mixficsol merged 1 commit intoOpenAtomFoundation:unstablefrom
YuCai18:hotfixuns/fix_setex

Conversation

@YuCai18
Copy link
Copy Markdown
Collaborator

@YuCai18 YuCai18 commented Jul 22, 2025

修复了pika4.0中setex在主从上不同步的bug #3117

修改的代码部分

1.过期时间计算错误:

此次修改将 SETEX/PSETEX 写入 binlog 时统一转换为接受绝对秒级时间戳的 pksetexat 指令,先在主库把 “当前时间 + TTL” 换算成过期时间点后落库,保证从库收到后与主库在同一时刻过期;同时把 PKSetexAtCmd::Do() 中时间戳乘 1000 的结果改用 int64_t 传递,避免 32 位溢溢出导致过期时间为负数,键立即失效,从而彻底解决主从过期不一致的问题。

修改后的运行截图

image-20250709201539889-1752063341461-4

image-20250709201845060-1752063526769-6

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling of expiration times for key-setting commands to prevent potential overflow and ensure accurate timestamp calculations.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jul 22, 2025

Walkthrough

The changes update how expiration timestamps are calculated and stored in key-value commands, shifting to explicit 64-bit integer arithmetic to prevent overflow and improve precision. These modifications affect the internal handling of TTL and expiration times within methods for setting keys with expiration.

Changes

File(s) Change Summary
src/pika_kv.cc Refactored timestamp and expiration calculations in SetexCmd, PsetexCmd, and PKSetexAtCmd methods to use 64-bit integers, ensuring correct arithmetic and overflow prevention. No changes to public interfaces.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Command (Setex/Psetex/SetexAt)
    participant TimeUtil
    participant Storage

    Client->>Command: Set key with TTL
    Command->>TimeUtil: Get current time (sec/ms)
    TimeUtil-->>Command: Return 64-bit timestamp
    Command->>Command: Calculate expire_at using 64-bit arithmetic
    Command->>Storage: Store key with expire_at
    Storage-->>Command: Acknowledge
    Command-->>Client: Respond
Loading

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

Suggested labels

☢️ Bug

Suggested reviewers

  • wangshao1
  • chejinge
  • AlexStocks

Poem

A hop and a skip through time's gentle flow,
Now 64 bits help our timestamps to grow.
No more overflows as the seconds tick by,
With precision and care, our keys never die.
🕰️🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8b077fc and 97c2754.

📒 Files selected for processing (1)
  • src/pika_kv.cc (3 hunks)
🧠 Learnings (1)
src/pika_kv.cc (2)

Learnt from: hahahashen
PR: #338
File: src/client.h:33-48
Timestamp: 2024-10-09T12:55:29.966Z
Learning: The PClient class in src/client.h uses std::chrono for handling timestamps for better type safety and clarity.

Learnt from: hahahashen
PR: #338
File: src/client.h:33-48
Timestamp: 2024-06-14T14:09:58.236Z
Learning: The PClient class in src/client.h uses std::chrono for handling timestamps for better type safety and clarity.

🧰 Additional context used
🧠 Learnings (1)
src/pika_kv.cc (2)

Learnt from: hahahashen
PR: #338
File: src/client.h:33-48
Timestamp: 2024-10-09T12:55:29.966Z
Learning: The PClient class in src/client.h uses std::chrono for handling timestamps for better type safety and clarity.

Learnt from: hahahashen
PR: #338
File: src/client.h:33-48
Timestamp: 2024-06-14T14:09:58.236Z
Learning: The PClient class in src/client.h uses std::chrono for handling timestamps for better type safety and clarity.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: build_on_macos
  • GitHub Check: build_on_centos
  • GitHub Check: build_on_ubuntu
  • GitHub Check: Analyze (go)
  • GitHub Check: build_on_ubuntu
  • GitHub Check: build_on_macos
  • GitHub Check: build_on_centos
🔇 Additional comments (3)
src/pika_kv.cc (3)

890-890: Good fix to prevent timestamp overflow.

The explicit use of int64_t and casting from time_t prevents potential overflow issues, especially important for the year 2038 problem on 32-bit systems. This ensures consistent timestamp handling in replication.


948-949: Improved timestamp calculation with better precision.

The refactoring to use an intermediate expire_at_ms variable and explicit int64_t types improves code clarity and prevents potential precision issues. This structured approach to millisecond-to-second conversion is more maintainable.


1774-1776: Critical fix to prevent timestamp overflow in millisecond conversion.

The change from int32_t casting to int64_t arithmetic prevents overflow when converting seconds to milliseconds. This is essential for correct expiration handling, especially for timestamps beyond 2038. The added comment clearly documents the intent.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions Bot added the ☢️ Bug Something isn't working label Jul 22, 2025
Comment thread src/pika_kv.cc
void PKSetexAtCmd::Do() {
s_ = db_->storage()->PKSetexAt(key_, value_, static_cast<int32_t>(time_stamp_sec_ * 1000));
// Use int64_t to avoid overflow
int64_t time_stamp_ms = static_cast<int64_t>(time_stamp_sec_) * 1000;
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

这里的 time_stamp_sec 已经是 int64_t 了,为啥还需要转一下

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

是的已经是int64_t了,保留static_cast<int64_t>是为了和源代码对齐

@Mixficsol Mixficsol merged commit 5d1de83 into OpenAtomFoundation:unstable Jul 22, 2025
27 checks passed
byseea11 pushed a commit to byseea11/pikiwidb that referenced this pull request Sep 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☢️ Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants