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

Recovery hangs in Fetcher #21

Closed
2 tasks
patkivikram opened this issue Nov 4, 2020 · 5 comments
Closed
2 tasks

Recovery hangs in Fetcher #21

patkivikram opened this issue Nov 4, 2020 · 5 comments

Comments

@patkivikram
Copy link
Collaborator

Checklist

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

Steps to reproduce

We have noticed that on a restart the recovery hangs with the only message from the fetcher and then it just hangs indefinitely

Expected behavior

Recovery should not hang

Actual behavior

Hangs with the following log message
[^----Fetcher]: Starting...

Full traceback

Paste the full traceback (if there is any)

Versions

  • Python version 3.8
  • Faust version 1.11.0a1
  • Operating system centos
  • Kafka version 2.4
  • RocksDB version (if applicable) 6.7
@marcosschroh
Copy link
Contributor

The version for faust-streaming is 0.1.0

@austinnichols101
Copy link
Contributor

@patkivikram - I was able to work around a similar timing issue with the following code. Interested to see if it has any impact on your issue.

class FaustApp(faust.App):

    # MDYER: Add a delay to work around the "Fetch offset" hang issue
    def on_rebalance_return(self, *args, **kwargs):
        interval = 5
        logger.info(f'on_rebalance_return - {interval}')
        time.sleep(interval)
        super().on_rebalance_return(*args, **kwargs)

@marcosschroh
Copy link
Contributor

@austinnichols101 your solution does not work for me. I tried and also I have increased the interval. I think it can not be solved redefining on_rebalance_return

@austinnichols101
Copy link
Contributor

Yup - I spoke with @patkivikram and it appears to be a different issue...

@patkivikram
Copy link
Collaborator Author

This was merged to master today

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

3 participants