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

When the stream is deleted while the redis stream source is running, the service should recreate the stream and the group #483

Open
tdeverdiere opened this issue Oct 16, 2023 · 4 comments
Labels
kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@tdeverdiere
Copy link
Contributor

Problem
When the stream is deleted, while the redis stream source is running, the service does not recreate the stream and the group so it stays in error logging :
"GROUP sync is missing and creates error : NOGROUP No such key 'my_stream' or consumer group 'a_group' in XREADGROUP with GROUP option"

To fix this, i would capture the error and send a Redis command to recreate the group. But i did not look much at the code.

Persona:
Event consumer (developer)
System Operator

Exit Criteria
No more error logs written like described above when the Redis stream is deleted

Time Estimate (optional):
1 day ?

Additional context (optional)
Restarting the service fixes the problem, so it is a workaround now.

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 15, 2024
@tdeverdiere
Copy link
Contributor Author

/reopen

@knative-prow knative-prow bot reopened this Oct 10, 2024
Copy link

knative-prow bot commented Oct 10, 2024

@tdeverdiere: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 11, 2024
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant