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

Bug(bulkload):rocksDB parameter allow_ingest_behind lose after replica migration #1650

Closed
ninsmiracle opened this issue Oct 19, 2023 · 0 comments
Labels
type/bug This issue reports a bug.

Comments

@ninsmiracle
Copy link
Contributor

Bug Report

  1. What did you do?
  • create a new app with parameter rocksdb.allow_ingest_behind = true
  • put some data in this new app
  • stop one node
  • change meta.lb.assign_delay_ms and let other nodes learn missing replicas of this app
  • those replicas that has been migrated start with rocksdb.allow_ingest_behind = false(which is default)
  1. What did you expect to see?
    In my opinion,this parameter should be consistent after replica migration.If I doing a data migration by using bulkload function,it may change data ingestion method.

  2. What version of Pegasus are you using?
    pegasus2.4

@ninsmiracle ninsmiracle added the type/bug This issue reports a bug. label Oct 19, 2023
empiredan pushed a commit that referenced this issue Nov 29, 2023
…replica migration (#1651)

#1650

While reopening a replica with empty envs(currently envs would be empty ONLY when reopening), put the last allow_ingest_behind value to the current option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug This issue reports a bug.
Projects
None yet
Development

No branches or pull requests

2 participants