Open tdeverdiere opened 2 years ago
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
.
/reopen
@christophefromparis: You can't reopen an issue/PR unless you authored it or you are a collaborator.
/remove-lifecycle stale
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
.
/remove-lifecycle stale
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
.
/remove-lifecycle stale
/reopen
@tdeverdiere: Reopened this issue.
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
.
/reopen
@tdeverdiere: Reopened this issue.
Describe the bug In k8s cluster, when Redis is restarted eventing-redis use an old socket to connect and there is this error in logs:
Expected behavior Eventing-redis should reopen a socket when the error is "use of closed network connection". Or may be we should use a pool of connection to handle those error.
To Reproduce Restart Redis in the k8s cluster