Trial Cloud connection timeout

Cloud
1

I’m trying to connect to the trial cloud database using the Go code on my localhost machine.

cp := aero.NewClientPolicy()
cp.User = "apiKey"
cp.Password = "secret"
cp.Timeout = 3 * time.Second
cp.TlsConfig = &tls.Config{}

client, err := aero.NewClientWithPolicyAndHost(cp, aero.NewHost("<myhost>.asdb.io", 3000))

Constantly getting the Timeout error. Here is the log:

2024/08/15 13:28:42 No nodes available; seeding...
2024/08/15 13:28:42 Seeding the cluster. Seeds count: 3
2024/08/15 13:28:42 Node Validator has 1 nodes and they are: [3.213.27.154:3000]
2024/08/15 13:28:42 Node Validator has 1 nodes and they are: [3.222.97.32:3000]
2024/08/15 13:28:42 Node Validator has 1 nodes and they are: [34.197.170.120:3000]
2024/08/15 13:28:44 Connection to address `34.197.170.120:3000` failed to establish with error: dial tcp 34.197.170.120:3000: i/o timeout
2024/08/15 13:28:44 Connection to address `3.213.27.154:3000` failed to establish with error: dial tcp 3.213.27.154:3000: i/o timeout
2024/08/15 13:28:44 Alias 34.197.170.120:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 34.197.170.120:3000: i/o timeout
2024/08/15 13:28:44 Seed 34.197.170.120:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 34.197.170.120:3000: i/o timeout
2024/08/15 13:28:44 Connection to address `3.222.97.32:3000` failed to establish with error: dial tcp 3.222.97.32:3000: i/o timeout
2024/08/15 13:28:44 Alias 3.222.97.32:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 3.222.97.32:3000: i/o timeout
2024/08/15 13:28:44 Seed 3.222.97.32:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 3.222.97.32:3000: i/o timeout
2024/08/15 13:28:44 Alias 3.213.27.154:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 3.213.27.154:3000: i/o timeout
2024/08/15 13:28:44 Seed 3.213.27.154:3000 failed: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 3.213.27.154:3000: i/o timeout
2024/08/15 13:28:44 ResultCode: INVALID_NODE_ERROR, Iteration: 0, InDoubt: false, Node: <nil>: Failed to connect to hosts: [3.222.97.32:3000 34.197.170.120:3000 3.213.27.154:3000]
  ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: Timeout
  dial tcp 34.197.170.120:3000: i/o timeout
2024/08/15 13:28:44 No nodes available; seeding...
2024/08/15 13:28:44 Seeding the cluster. Seeds count: 3
2024/08/15 13:28:44 Node Validator has 1 nodes and they are: [3.213.27.154:3000]
2024/08/15 13:28:44 Node Validator has 1 nodes and they are: [3.222.97.32:3000]
2024/08/15 13:28:44 Node Validator has 1 nodes and they are: [34.197.170.120:3000]
2024/08/15 13:28:45 Failed to connect to host(s): [d8d839ab-5811-4950-b3ae-7dbf5170fdd5.asdb.io:3000]; error: ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: command execution timed out on client: See `Policy.Timeout`
2024/08/15 13:28:45 Exception connecting aero spike cluster ResultCode: TIMEOUT, Iteration: 0, InDoubt: false, Node: <nil>: command execution timed out on client: See `Policy.Timeout`
2

Hi Ivan_Chobotar,

Thank for these details. We’re looking into this and will get back to you soon.

Can you confirm which version of the Go proxy client you are using?

Best, Eric

3

I’m using v7 aerospike client on go1.22.4

5

Thanks for sharing the client version details. We double checked the database and didnt any connectivity issues.

We did notice that you are attempting to connect over port 3000 and you need to use port 4000 to connect.

Can you try changing the port and let us know if that resolved the issue?

You can also look at our quick start guide for reference as well: Aerospike Quick Start | Developer

6

Now I’m getting the Requested new buffer size is invalid. Requested: 91695177164146, allowed: 0…67108864

I’ve found similar question here on forum. The answer was to check if the database is running - mine is running

7

Sorry for the delay.

Can you switch to using the v6 client as described in the Quick Start? We have tested that version of the client with your cluster and confirmed that everything works.

There are some changes needed for the v7 client that are not fully documented yet. Let me know if you would like to continue with the v7 client and I can let you know when those changes are documented.

I’m also going to extend your trial by another week. Let me know if you think you will need more time.

Best, Eric

8

v6 worked for me thank you for help

1 Like