Any idea what would be the exact cause for this error? Thanks.
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Hi @nikhillimaje, this is probably duplicated with #702
\nplease try the latest version.
","upvoteCount":1,"url":"https://github.com/redis/rueidis/discussions/768#discussioncomment-12217275"}}}Invalid memory address or nil pointer dereference #768
-
|
Hello, we recently saw the below error when the pods were spinning up causing them to enter crash loop. The underlying data store was Redis and was degraded, because of the large number of connections from our service. Any idea what would be the exact cause for this error? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Hi @nikhillimaje, this is probably duplicated with #702 please try the latest version. |
Beta Was this translation helpful? Give feedback.
-
|
Connections won’t be closed for no reason. Someone needs to close them. |
Beta Was this translation helpful? Give feedback.
-
|
Let's consider the above scenario where our application crashed because of the nil pointer. In this case as well, the connections won't be closed? Note that we're not explicitly calling |
Beta Was this translation helpful? Give feedback.
-
|
In that case, those connections will be forced closed by your operating system. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. Thanks for explaining. Is there a way to enforce timeouts on the read requests? We have |
Beta Was this translation helpful? Give feedback.
-
|
Use context deadline or context timeout: |
Beta Was this translation helpful? Give feedback.
Hi @nikhillimaje, this is probably duplicated with #702
please try the latest version.