-
Notifications
You must be signed in to change notification settings - Fork 40
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
getting tend error #130
Comments
Sorry for the extremely late reply. Could you share the full stack trace? What file/line does this exception originate from? |
Hi, the company i work in has open a case with your support team |
I'm afraid I wouldn't be able to help much without a stack trace, since I wouldn't know where to look. Can you please paste the whole stack trace from your logs?
|
Hi, the company I work in, opened a case with your support.
"#00036770-Aerospike Ruby Client Issues- AppLovin"
On Wed, Aug 21, 2024 at 9:26 AM Khosrow Afroozeh ***@***.***>
wrote:
… I'm afraid I wouldn't be able to help much without a stack trace, since I
wouldn't know where to look. Can you please paste the whole stack trace
from your logs?On 21. Aug 2024, at 8:07 AM, erez-parashi ***@***.***>
wrote:
Hi, the company i work in has open a case with your support team
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#130 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A24VSRJEYU2YKDWJBYTKCWLZSQXKBAVCNFSM6AAAAABJTSUX3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBRGIZTCMBUG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Exception occured during tend: undefined method `name' for nil:NilClass
aerospike (3.0.0)
GKE is updating the aerospike cluster nodes.
While this is happening , pods with ruby client try to work with aerospike and some clients get this error and continue to fail until the pod is restarted
The text was updated successfully, but these errors were encountered: