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

Fix faust to not resume flow on rebalance if rocksdb file is unavailable #92

Closed
patkivikram opened this issue Feb 3, 2021 · 1 comment

Comments

@patkivikram
Copy link
Collaborator

Checklist

  • [ x] I have included information about relevant versions
  • [ x] I have verified that the issue persists when using the master branch of Faust.

Steps to reproduce

On repartition if the rocksdb instance is owned by another worker the requesting worker should wait and not resume its streams

Expected behavior

It should wait until the rocksdb instance is available

Actual behavior

The worker started to process and crashed when it could not access the rocksdb instance

Full traceback

Paste the full traceback (if there is any)

Versions

  • Python version
  • Faust version
  • Operating system
  • Kafka version
  • RocksDB version (if applicable)
@patkivikram
Copy link
Collaborator Author

merged to master in v0.4.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant