TLS handshake timeout when using cloud Redis with large # of consumers
Closed this issue · 10 comments
panic: TLS handshake timeout
goroutine 75 [running]:
knative.dev/eventing-redis/source/pkg/adapter.(*Adapter).newPool.func1(0x0, 0x0, 0x0, 0x0)
knative.dev/eventing-redis/source/pkg/adapter/adapter.go:256 +0x418
knative.dev/eventing-redis/source/pkg/adapter.(*Adapter).Start.func1(0xc0004ec140, 0xc000187570, 0xc000433470, 0x1f7d720, 0xc000432030, 0xc000054027, 0x8, 0xc0003bc5d0, 0x12)
knative.dev/eventing-redis/source/pkg/adapter/adapter.go:132 +0x7c
created by knative.dev/eventing-redis/source/pkg/adapter.(*Adapter).Start
knative.dev/eventing-redis/source/pkg/adapter/adapter.go:129 +0xb25
To reproduce:
config-redis set to 5000 consumers
config-tls set cert
set address in redisstreamsource to cloud instance
Install everything and logs show the panic above sometimes.
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
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
@aavarghese: 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/test-infra repository.
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.